Evan Hughes, James Stuckey Last Updated: January 28, 2014 Build Basis: Rational Team Concert 4.0

Tue, 12 Jun 2012

4 min read

Workaround: Running the Rational Team Concert Eclipse client on 64-bit Linux

Evan Hughes, James Stuckey
Last Updated: January 28, 2014
Build Basis: Rational Team Concert 4.0

Summary

This workaround describes how to avoid the following issues from occurring when running the Rational Team Concert Eclipse client on 64-bit Linux platforms:

No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]
error
XPCOM error -1041039104
message and crash

More Information

Problem

Some parts of the Rational Team Concert Eclipse client stop working, and the error message,

No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]

, displays instead of the expected content. The Eclipse client might also display the error,

An error occurred during creation of embedded help browser XPCOM error -1041039104

, before crashing.

Environment

This issue occurs when running the 32-bit Rational Team Concert Eclipse client on 64-bit Linux distributions that do not have a 32-bit version of XULRunner installed. It can also occur when running a 32-bit or 64-bit Rational Team Concert Eclipse client (available in Rational Team Concert 4.0 and later) on 64-bit Linux distributions with a version of XULRunner that is incompatible with the underlying version of Eclipse.

Diagnosing the problem

After delivering a change set or saving a work item, the Team Advisor view displays the error,

No more handles

XPCOM error -1041039104

. The issue can also be seen when starting the local help system or when displaying the welcome page, as done on the initial launch of the client.

Reason

You are using a 32-bit Rational Team Concert Eclipse client, and the operating system does not ship a 32-bit XULRunner. Or you are using the 32-bit or 64-bit Eclipse client, and the operating system includes an incompatible version of XULRunner.

Workaround

For 32-bit Rational Team Concert on 64-bit Linux:
1. Install a 32-bit version of XULRunner:
  - yum install xulrunner.i686
2. Restart the Rational Team Concert Eclipse client.

For Rational Team Concert 3.x (which only supports 32-bit client install) or Rational Team Concert 4.x on 32-bit Linux:
1. Install a compatible 32-bit XULRunner on the system.
2. Update your eclipse.ini to point to the library (to ensure that it is being used) by adding a line similar to the following example to the vmargs:
  - Add -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-compat
For Rational Team Concert 4.x on 64-bit Linux:
1. Install a webkitgtk+ 1.2.x package on the system.
2. Update your eclipse.ini, so that Eclipse uses webkitgtk, by adding a line similar to the following to the vmargs:
  - Add -Dorg.eclipse.swt.browser.UseWebKitGTK=true to the vmargs in the eclipse.ini, or install with eclipse 3.7.2+
3. Alternately, you can install the Rational Team Concert Eclipse client with eclipse 3.7.2+, which supports additional versions of XULRunner. For details on supported XULRunner versions, see the link to the SWT FAQ in the related information section of this article.

For Rational Team Concert 4.x on 64-bit Linux:
- If you are using 64-bit Red Hat Enterprise Linux 6.x, you must use XULRunner 1.9.2.24 to avoid crashes of the embedded web browser.

Related Information

The following links point to related information:

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Feedback

Discussion

Kevin DeKorte October 23, 2012 02:49:03

I installed xulrunner.i686 as directed on my RHEL 6.3 system and this change now makes the RTC client segfault on startup /opt/IBM/SDP/eclipse -product com.ibm.rational.rsa4ws.product.v80.ide Unhandled exception Type=Segmentation error vmState=0x00040000 J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000001 Handler1=0036DA1A Handler2=0013AA67 InaccessibleAddress=016CB000 EDI=016CB000 ESI=016CB002 EAX=016CB002 EBX=0726DFF4 ECX=AD7F0688 EDX=AD7F068C EIP=0726B8C1 ES=002B DS=002B ESP=F7744AF4 EFlags=00210212 CS=0023 SS=002B EBP=F7744B84 Module=/usr/lib/gconv/UTF-16.so Module_base_address=0726B000 Symbol=gconv Symbol_address=0726B500 Target=2_60_20120322_106209 (Linux 2.6.32-279.9.1.el6.x86_64) CPU=x86 (4 logical CPUs) (0x3dd900000 RAM) ----------- Stack Backtrace ----------- (0x0012C2E0 [libj9prt26.so+0xf2e0]) (0x0013BA12 [libj9prt26.so+0x1ea12]) (0x0012BFD1 [libj9prt26.so+0xefd1]) (0x0012C0C5 [libj9prt26.so+0xf0c5]) (0x0012BBD4 [libj9prt26.so+0xebd4]) (0x0013BA12 [libj9prt26.so+0x1ea12]) (0x0012BB43 [libj9prt26.so+0xeb43]) (0x0036CE45 [libj9vm26.so+0x14e45]) (0x0013BA12 [libj9prt26.so+0x1ea12]) (0x0036D14E [libj9vm26.so+0x1514e]) (0x0036DA68 [libj9vm26.so+0x15a68]) (0x0013AC35 [libj9prt26.so+0x1dc35]) __kernel_rt_sigreturn+0x0 (0x00DA6410) (0x00A846BF [libc.so.6+0x186bf]) iconv+0x66 (0x00A83CD6 [libc.so.6+0x17cd6]) (0xACA7B37F [libxul.so+0xda737f]) --------------------------------------- JVMDUMP039I Processing dump event "gpf", detail "" at 2012/10/23 12:45:44 - please wait. JVMDUMP032I JVM requested System dump using '/home/kdekorte/core.20121023.124544.25181.0001.dmp' in response to an event JVMDUMP010I System dump written to /home/kdekorte/core.20121023.124544.25181.0001.dmp JVMDUMP032I JVM requested Java dump using '/home/kdekorte/javacore.20121023.124544.25181.0002.txt' in response to an event JVMDUMP012E Error in Java dump: /home/kdekorte/javacore.20121023.124544.25181.0002.txt JVMDUMP032I JVM requested Snap dump using '/home/kdekorte/Snap.20121023.124544.25181.0003.trc' in response to an event JVMDUMP010I Snap dump written to /home/kdekorte/Snap.20121023.124544.25181.0003.trc JVMDUMP013I Processed dump event "gpf", detail "".

Nhi P Ta November 1, 2012 09:57:29

My environment has MOZILLA_FIVE_HOME=/usr/lib/xulrunner-compat The workaround found is that we need to add an option in Eclipse.ini file for each of the client impacted. -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-compat/

Rene Meyer January 17, 2013 04:16:27

Hello I use the following approach for 32 bit RTC 4.0.1 Client on 64bit Linux. I installed a seperate xulrunner 32 bit version 1.9.2.19 in /opt/xulrunner. After that I modified eclipse.ini of RTC -Dorg.eclipse.swt.browser.XULRunnerPath=/opt/xulrunner.

Jim jarodon February 26, 2013 07:19:38

Following the instructions above which says: ------------------------------------------ For Rational Team Concert 4.x on 64-bit Linux: Install a webkitgtk+ 1.2.x package on the system. Update your eclipse.ini to tell Eclipse to use use webkitgtk by adding a line similar to the following to the vmargs: Add -Dorg.eclipse.swt.browser.UseWebKitGTK=true to the vmargs in the eclipse.ini, or install with eclipse 3.7.2+ ----------------------------------------------------- These instructions aren't working for me, using RTC 4.0.1 on fedora 17 64 bit. When I try to run RTC I get a crash dump. tried using new workspaces, reinstalling client etc.. no luck I have the Installed Packages xulrunner.i686 19.0-1.fc17 xulrunner.x86_64 19.0-1.fc17 for webkitgtk webkitgtk.x86_64 1.8.3-1.fc17 webkitgtk.i686 1.8.3-1.fc17 any ideas? are there updated instructions somewhere?

Jim jarodon February 26, 2013 07:20:05

btw, I also tried 4.0.2 RC2, same problem.

Rogério Ramos da Silva May 7, 2013 02:24:11

This work like a charm for me RSA 8.0.4 64bits+RTC4.0.1

Christopher Maguire May 8, 2013 06:10:12

I just encountered this problem (running RTC 4.0.1 on RHEL 6.4) today when my OS was updated. The update apparently changed my xulrunner version such that the RTC client hit this problem on startup. My copy of the RTC client was via the plain zip https://jazz.net/downloads/rational-team-concert/releases/4.0.1/RTC-Client-Linux-4.0.1.zip, which it turns out is a 32-bit client. You can install the 64 bit client only via IM. I was about to do that, when I got the advice to try adding -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-compat to my eclipse.ini (and removing the UseWebKitGTK=true entry suggested above). That fixed it.

Fredrik Larsson October 30, 2013 11:59:45

Same problem using plain zip for RTC4.0.4. Same solution as above (-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-compat in eclipse.ini) resolved it.

Alex Fitzpatrick May 7, 2014 03:33:59

An internal user encountered this when using a 64 bit client on 64 bit RHEL 6.5 after upgrading from 6.3. I was able to reproduce the issue and determined that the copy of xulrunner 1.9 installed in /usr/lib/xulrunner-compat is 32 bit. Solution: 1. Install 64 bit xulrunner19.x86_64 with yum: yum install xulrunner19.x86_64 2. Set MOZILLA_FIVE_HOME to use new version of xulrunner add to .bashrc export MOZILLA_FIVE_HOME=/usr/lib64/xulrunner-1.9.2 3. Specify XULRunnerPath in eclipse.ini add to eclipse.ini -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib64/xulrunner-1.9.2

Patrick LoPresti May 20, 2014 01:55:02

We use Scientific Linux 6.x, and "yum install xulrunner19.x86_64" did not work for me. I am not sure which repository it is supposed to be in. Here is what I did. Download http://ftp.scientificlinux.org/linux/scientific/6.2/x86_64/updates/security/xulrunner-1.9.2.26-2.el6_2.x86_64.rpm This is the last update to XULRunner 1.9.2.x that I could find. mkdir /tmp/extract cd /tmp/extract rpm2cpio /path/to/xulrunner-1.9.2.26-2.el6_2.x86_64.rpm | pax -v -r This will create ./etc and ./usr directories and extract a bunch of stuff under them. The stuff under ./etc is unimportant. Just move ./usr/lib64/xulrunner-1.9.2 to some accessible place; call that /path/to/xulrunner-1.9.2. Finally, add to eclipse.ini (under the -vmargs section): -Dorg.eclipse.swt.browser.DefaultType=mozilla -Dorg.eclipse.swt.browser.XULRunnerPath=/path/to/xulrunner-1.9.2 That's it. I did not need to set MOZILLA_FIVE_HOME. Note that, with Eclipse "Luna" (4.4), you can use /usr/lib64/firefox for your XULRunnerPath, since Luna supports XULRunner 24.x (bundled with Firefox). But Luna is only a Release Candidate at the moment...

Alex Fitzpatrick June 4, 2014 03:20:19

My earlier steps appear to be incomplete, at least one customer I've seen needed to set the SWT default browser type as well, that makes my steps: 1. Install 64 bit xulrunner19.x86_64 with yum: yum install xulrunner19.x86_64 2. Set MOZILLA_FIVE_HOME to use new version of xulrunner add to .bashrc export MOZILLA_FIVE_HOME=/usr/lib64/xulrunner-1.9.2 3. Specify XULRunnerPath in eclipse.ini add to eclipse.ini -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib64/xulrunner-1.9.2 4. Force SWT to use mozilla add to eclipse.ini -Dorg.eclipse.swt.browser.DefaultType=mozilla

Patrick LoPresti June 4, 2014 04:33:06

@Alex -- I do not believe there is any "xulrunner19" package in Red Hat 6.x, nor has there ever been... Are you using some derivative (e.g. CentOS)? The "Related Links" section of the following tech note also has links for downloading usable versions of XULRunner, both 32- and 64-bit: http://www.ibm.com/support/docview.wss?uid=swg21598554 This sure seems to be a <a href="https://jazz.net/forum/questions/149248/">common problem</a>. If the WebKit in Red Hat 6.5 (plus updates) is crashy, perhaps IBM's engineers could help Red Hat figure out why and fix it?

Alex Fitzpatrick June 4, 2014 06:11:22

@Patrick I was testing with an IBM registered RHEL that uses internal update sites, I confirm that Vanilla RHEL 6.5 does not appear to have a xulrunner19 package.

Andrew Hoo June 13, 2014 01:52:38

For those on Ubuntu 12.04 or other distros that do not provide a repository to get xulrunner, then you can try to get the xulrunner runtimes directly from mozilla. 1) Read the swt faq to determine which xulrunner you want. http://www.eclipse.org/swt/faq.php#browserlinux - Keep in mind whether or not you want 32 bit (i686) or 64 bit (x86_64) 2) Find the release from http://ftp.mozilla.org/pub/mozilla.org/xulrunner/ - I'm going to choose http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2012/05/2012-05-03-03-32-04-mozilla-1.9.2/xulrunner-1.9.2.29pre.en-US.linux-x86_64.tar.bz2 --- See my decision at the bottom of this post 3) Install the release. I've modified the script found from: http://askubuntu.com/questions/125980/how-do-i-install-xulrunner-in-12-04 XURL=http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2012/05/2012-05-03-03-32-04-mozilla-1.9.2/xulrunner-1.9.2.29pre.en-US.linux-x86_64.tar.bz2 sudo sh -c "wget -O- $XURL | tar -xjC /opt" #download and extract sudo sh -c "echo -Dorg.eclipse.swt.browser.XULRunnerPath=/opt/xulrunner >> /opt/IBM/TeamConcert/eclipse.ini" #append the path to xulrunner in the eclipse configuration -------- - I choose 1.9.2 because it is compatible with both eclipse 3.6.x and 4.2.x which are the current clients on Jazz RTC as of writing this. - I choose this nightly build over a release build because I cannot find a x86_64 release at https://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/1.9.2.19/runtimes/ ---- the closest 1.9.2.19 that I can find in x86_64 is http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2011/07/2011-07-07-03-32-36-mozilla-1.9.2/xulrunner-1.9.2.19pre.en-US.linux-x86_64.tar.bz2 - the latest mention of xulrunner in ubuntu that I can find is 1.9.2.28 (incase you want to align with what you think other people have vetted: --- http://packages.ubuntu.com/search?keywords=xulrunner-1.9.2 --- http://packages.ubuntu.com/lucid/xulrunner-1.9.2 --- http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2012/03/2012-03-06-03-32-08-mozilla-1.9.2/xulrunner-1.9.2.28pre.en-US.linux-x86_64.tar.bz2 - http://www-01.ibm.com/support/docview.wss?uid=swg21598554 lists a slightly older March 2012 build of 1.9.2.29 http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2012/03/2012-03-29-03-32-28-mozilla-1.9.2/xulrunner-1.9.2.29pre.en-US.linux-x86_64.tar.bz2 - however, working on the assumption that latest is greatest, therefore I choose May release of 1.9.2.29. - I do not choose 3.6.28 because I can only find the i686 release, and I could not find a cooresponding nightly release http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/3.6.28/runtimes/xulrunner-3.6.28.en-US.linux-i686.tar.bz2 - I do not choose 10.x because it is only compatible with eclpse 4.2.x and not 3.6.x https://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/10.0.4esr/runtimes/xulrunner-10.0.4esr.en-US.linux-x86_64.tar.bz2

Samir Patel September 27, 2014 09:18:16

solved the problem by installing libwebkitgtk on Ubuntu 12.04 and Eclipse Juno/Indigo. sudo apt-get install libwebkitgtk-1.0-0 Add the following lines at the end of your eclipse.ini: -Dorg.eclipse.swt.browser.DefaultType=webkit -Dorg.eclipse.swt.browser.UseWebKitGTK=true This enables the use webkit instead of xulrunner.

Arun K Sriramaiah October 7, 2014 11:06:05

Kubuntu14.04 is supported with RTC 4.0.7 ? if yes, could you please provide more details.

venkat 443 November 3, 2014 02:04:29

I am facing the MOZILLA_FIVE_HOME not set path in eclipse after installation of RTC Eclipse plug in. I installed RTC 5.0 on RHEL server 6.5 64 bit version. Installed the xulRunner 32 bit library on RHEL 6.5 but I am facing same problem.. Eclipse is crashing when trying to open Jazz Administration in Eclipse ..

Kevin Mayfield January 9, 2015 05:08:05

This is a VERY frustrating situation. I am using RTC406 on RHEL 6.5: $ uname -a Linux xxxxxxx.ibm.com 2.6.32-431.30.1.el6.x86_64 #1 SMP Wed Jul 30 14:44:26 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux The firefox info : $ firefox -v Mozilla Firefox 31.3.0 I found the Mozilla XULRunner 1.9.2 from https://developer.mozilla.org/en-US/docs/XULRunner_1.9.2_Release_Notes#Linux I followed the instructions on Installing XULRunner, which including registration (using root): $ xulrunner --register-global Added the eclipse.ini recommended defines: -Dorg.eclipse.swt.browser.UseWebKitGTK=true -Dorg.eclipse.swt.browser.DefaultType=mozilla -Dorg.eclipse.swt.browser.XULRunnerPath=/opt/xulrunner/1.9.2 Ran ./eclipse & Menu Help->Welcome. CRASH! The dump showed the following entry: 2CIENVVAR MOZILLA_FIVE_HOME=/usr/lib64/xulrunner Added export MOZILLA_FIVE_HOME=/opt/xulrunner/1.9.2 Ran ./eclipse & Run Help->Welcome. CRASH! I cannot move to newer than 4.0.6. I could use older. I cannot upgrade to newer version on RHEL.

Rene Meyer January 12, 2015 03:06:10

Hello, I found a good overview about Eclipse and Browser WebGtk/Xulrunner compatibility which might be helpful: http://www.eclipse.org/swt/faq.php#browserlinux

Daniel Connell November 9, 2015 10:07:15

Make sure that you check the Linux system you are running to ensure that you have the correct architecture. For example, run the command uname or uname -a to see if you are running 32 bit or 64 bit kernel. Once you get that out of the way download the appropriate one here is this technote and follow its instructions to the letter. Worked perfectly for me. Technote: http://www-01.ibm.com/support/docview.wss?uid=swg21616810

Workaround: Running the RTC Eclipse client on 64-bit RedHat Linux