It's all about the answers!

Ask a question

RTC keep crashing after Red Hat's update for 6.5


Gustavo Martim (2813) | asked Apr 23 '14, 2:25 p.m.
edited Apr 23 '14, 2:36 p.m.
Hi all,

My RTC keep crashing very often after I have updated my Red Hat to 6.5. I'm not sure if it makes sense but frequently RTC crashes.

There is no common behavior between crashes. I already faced an issue on RTC running on Red Hat before but in this case it occurs in an specific case and was fixed easily with this forum's help.

Unfortunately now it is not the case, as I said, in some cases RTC runs for almost a day with no crash and others within an hour it crashes more than 4 times.

Here is what is printed on the window opened after crashing:

JVM terminated. Exit code=160
/opt/ibm/TeamConcert//jdk/jre/bin/javaw
-Xms100m
-Xmx1024m
-Xmnx64m
-Xgcpolicy:gencon
-Xscmx96m
-Xshareclasses:name=IBMSDP_%u
-Xcompressedrefs
-Dsdp.driver=RADO90-I20130531_1619
-Xquickstart
-XX:MaxPermSize=512M
-Dcom.ibm.ws.management.event.max_polling_interval=1000
-jar /opt/ibm/TeamConcert//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
-os linux
-ws gtk
-arch x86_64
-showsplash
-launcher /opt/ibm/TeamConcert/eclipse
-name Eclipse
--launcher.library /opt/ibm/TeamConcert//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120913-144807/eclipse_1502.so
-startup /opt/ibm/TeamConcert//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.overrideVmargs
-exitdata 238031
-install /opt/ibm/TeamConcert
-product com.ibm.team.concert.product
-vm /opt/ibm/TeamConcert//jdk/jre/bin/javaw
-vmargs
-Xms100m
-Xmx1024m
-Xmnx64m
-Xgcpolicy:gencon
-Xscmx96m
-Xshareclasses:name=IBMSDP_%u
-Xcompressedrefs
-Dsdp.driver=RADO90-I20130531_1619
-Xquickstart
-XX:MaxPermSize=512M
-Dcom.ibm.ws.management.event.max_polling_interval=1000
-jar /opt/ibm/TeamConcert//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar

Everything else that I have is the information from Crash Reporter, I can provide it if needed.

Not sure if it is relevant, here are some parts from there:

...
NULL           ------------------------------------------------------------------------
0SECTION       THREADS subcomponent dump routine
NULL           =================================
NULL
1XMPOOLINFO    JVM Thread pool info:
2XMPOOLTOTAL       Current total number of pooled threads: 80
2XMPOOLLIVE        Current total number of live threads: 38
2XMPOOLDAEMON      Current total number of live daemon threads: 24
NULL           
1XMCURTHDINFO  Current thread
NULL           ----------------------
3XMTHREADINFO      "main" J9VMThread:0x0000000041345100, j9thread_t:0x00007FA75802DAC0, java/lang/Thread:0x0000000001456EB0, state:R, prio=6
3XMJAVALTHREAD            (java/lang/Thread getId:0x1, isDaemon:false)
3XMTHREADINFO1            (native thread ID:0x1B80, native priority:0x6, native policy:UNKNOWN)
3XMTHREADINFO2            (native stack address range from:0x00007FA75D2BE000, to:0x00007FA75DCBF000, size:0xA01000)
3XMHEAPALLOC             Heap bytes allocated since last GC cycle=20767304 (0x13CE248)
3XMTHREADINFO3           Java callstack:
4XESTACKTRACE                at org/eclipse/swt/internal/webkit/WebKitGTK._JSEvaluateScript(Native Method)
4XESTACKTRACE                at org/eclipse/swt/internal/webkit/WebKitGTK.JSEvaluateScript(WebKitGTK.java:119)
4XESTACKTRACE                at org/eclipse/swt/browser/WebKit.execute(WebKit.java:802)
4XESTACKTRACE                at org/eclipse/swt/browser/WebKit.addEventHandlers(WebKit.java:722)
4XESTACKTRACE                at org/eclipse/swt/browser/WebKit.webkit_window_object_cleared(WebKit.java:1975)
4XESTACKTRACE                at org/eclipse/swt/browser/WebKit.webViewProc(WebKit.java:473)
4XESTACKTRACE                at org/eclipse/swt/browser/WebKit.Proc(WebKit.java:387)
4XESTACKTRACE                at org/eclipse/swt/internal/webkit/WebKitGTK._webkit_web_frame_get_global_context(Native Method)
4XESTACKTRACE                at org/eclipse/swt/internal/webkit/WebKitGTK.webkit_web_frame_get_global_context(WebKitGTK.java:959)
4XESTACKTRACE                at org/eclipse/swt/browser/WebKit.execute(WebKit.java:785)
4XESTACKTRACE                at org/eclipse/swt/browser/WebBrowser.createFunction(WebBrowser.java:375)
4XESTACKTRACE                at org/eclipse/swt/browser/BrowserFunction.<init>(BrowserFunction.java:147)
4XESTACKTRACE                at org/eclipse/swt/browser/BrowserFunction.<init>(BrowserFunction.java:84)
4XESTACKTRACE                at org/eclipse/swt/browser/WebKit$6.<init>(WebKit.java:632)
4XESTACKTRACE                at org/eclipse/swt/browser/WebKit.create(WebKit.java:632)
4XESTACKTRACE                at org/eclipse/swt/browser/Browser.<init>(Browser.java:99)
4XESTACKTRACE                at com/ibm/team/process/internal/ide/ui/advice/TeamAdvisorView.createDetailBrowser(TeamAdvisorView.java:298)
4XESTACKTRACE                at com/ibm/team/process/internal/ide/ui/advice/TeamAdvisorView.createPartControl(TeamAdvisorView.java:279)
4XESTACKTRACE                at org/eclipse/ui/internal/e4/compatibility/CompatibilityPart.createPartControl(CompatibilityPart.java:138)
4XESTACKTRACE                at org/eclipse/ui/internal/e4/compatibility/CompatibilityView.createPartControl(CompatibilityView.java:155)
4XESTACKTRACE                at org/eclipse/ui/internal/e4/compatibility/CompatibilityPart.create(CompatibilityPart.java:313)
4XESTACKTRACE                at sun/reflect/NativeMethodAccessorImpl.invoke0(Native Method)
4XESTACKTRACE                at sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88(Compiled Code))
4XESTACKTRACE                at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55(Compiled Code))
4XESTACKTRACE                at java/lang/reflect/Method.invoke(Method.java:613(Compiled Code))
4XESTACKTRACE                at org/eclipse/e4/core/internal/di/MethodRequestor.execute(MethodRequestor.java:56(Compiled Code))
4XESTACKTRACE                at org/eclipse/e4/core/internal/di/InjectorImpl.processAnnotated(InjectorImpl.java:861(Compiled Code))
4XESTACKTRACE                at org/eclipse/e4/core/internal/di/InjectorImpl.processAnnotated(InjectorImpl.java:841(Compiled Code))
4XESTACKTRACE                at org/eclipse/e4/core/internal/di/InjectorImpl.inject(InjectorImpl.java:113(Compiled Code))
4XESTACKTRACE                at org/eclipse/e4/core/internal/di/InjectorImpl.internalMake(InjectorImpl.java:321(Compiled Code))
4XESTACKTRACE                at org/eclipse/e4/core/internal/di/InjectorImpl.make(InjectorImpl.java:242)
4XESTACKTRACE                at org/eclipse/e4/core/contexts/ContextInjectionFactory.make(ContextInjectionFactory.java:161)
...
1XMTHDINFO     Thread Details
NULL           ------------------
NULL          
3XMTHREADINFO      "MemoryPoolMXBean notification dispatcher" J9VMThread:0x0000000042DABC00, j9thread_t:0x00007FA70C0087F0, java/lang/Thread:0x0000000004082000, state:CW, prio=6
3XMJAVALTHREAD            (java/lang/Thread getId:0x41, isDaemon:true)
3XMTHREADINFO1            (native thread ID:0x1C04, native priority:0x6, native policy:UNKNOWN)
3XMTHREADINFO2            (native stack address range from:0x00007FA718003000, to:0x00007FA718044000, size:0x41000)
3XMHEAPALLOC             Heap bytes allocated since last GC cycle=0 (0x0)
3XMTHREADINFO3           Java callstack:
4XESTACKTRACE                at com/ibm/lang/management/MemoryNotificationThread.processNotificationLoop(Native Method)
4XESTACKTRACE                at com/ibm/lang/management/MemoryNotificationThread.run(MemoryNotificationThread.java:54)
...
3XMTHREADINFO      "WebSphere status monitor" J9VMThread:0x000000004427A600, j9thread_t:0x00007FA70C073900, java/lang/Thread:0x00000000082210D0, state:CW, prio=2
3XMJAVALTHREAD            (java/lang/Thread getId:0xBF, isDaemon:true)
3XMTHREADINFO1            (native thread ID:0x1F6E, native priority:0x2, native policy:UNKNOWN)
3XMTHREADINFO2            (native stack address range from:0x00007FA6CABB9000, to:0x00007FA6CABFA000, size:0x41000)
3XMHEAPALLOC             Heap bytes allocated since last GC cycle=170096 (0x29870)
3XMTHREADINFO3           Java callstack:
4XESTACKTRACE                at java/lang/Thread.sleep(Native Method)
4XESTACKTRACE                at java/lang/Thread.sleep(Thread.java:904(Compiled Code))
4XESTACKTRACE                at com/ibm/ws/st/core/internal/WebSphereServerBehaviour$1.run(WebSphereServerBehaviour.java:284)
...

Thanks!

Comments
Alexander Gavrin commented May 08 '14, 2:52 a.m. | edited Jun 25 '14, 3:02 a.m.

I tried all suggestions and it does not work. I tried to reinstall RTC from scratch, did multiple xulrunner installations but it still is crashing. Any other suggestion?

Accepted answer


permanent link
Rene Meyer (42913234) | answered Apr 23 '14, 2:45 p.m.
JAZZ DEVELOPER
Hello,
it could be a problem with xulrunner.
There are many different reasons or solutions to that problem with Eclipse based IDEs under Linux and incompatible versions of xulrunner.
http://www-01.ibm.com/support/docview.wss?uid=swg21598554
https://jazz.net/forum/questions/104317/jvm-terminated-exit-code160-when-submitting-build-in-rtc-eclipse-elient
If the links do not help please contact IBM technical support and supply the JVM crash report dump as well.
Best Regards,
René
Gustavo Martim selected this answer as the correct answer

Comments
Gustavo Martim commented Apr 23 '14, 4:26 p.m. | edited Apr 24 '14, 2:47 a.m.

 Thanks a lot for your helping, seems that it worked. I will keep testing and will let you know if I get anything.

Sorry, I have already seen it but not understood very well.


Again, thanks!


Gustavo Martim commented Apr 24 '14, 9:31 a.m. | edited Jun 25 '14, 3:03 a.m.

 So far, no issue anymore. Still testing.


Just to let you know what I did based on posts here. I installed this version for xulrunner:

[gumar@gumar ~]$ xulrunner19 -version
Mozilla XULRunner 1.9.2.26 - 20130213163137

and added it to eclipse.ini:

-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/bin/xulrunner19

Thanks!


Gustavo Martim commented May 08 '14, 8:19 a.m. | edited Jun 25 '14, 3:03 a.m.

 Still getting the same behavior. It worked fine for few days, but after that it started crashing again. Thanks!


Kevin Ramer commented May 08 '14, 8:33 a.m.

One thing I tried was getting Eclipse 4.3 (J2EE package) from eclipse.org then using IBM Installation Manager to add RTC to that eclipse.  It works most of the time, but still does the exit very similar to the OP.

I have:

-Dorg.eclipse.swt.browser.XULRunnerPath=/home/ramerk/xulrunner
-Dorg.eclipse.swt.browser.UseWebKitGTK=true

in the eclipse.ini and the xulrunner is:

 xulrunner/xulrunner --version
Mozilla XULRunner 1.9.2.29pre - 20120329033228


Kevin Ramer commented Jun 03 '14, 12:56 p.m.

Ok,  I think this is much better; here's where I am with respect to all these variations:

In eclipse.ini:

-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-compat/xulrunner

Environment:
export MOZILLA_FIVE_HOME=/usr/lib64/firefox
export LD_LIBRARY_PATH=/usr/lib64/firefox:${LD_LIBRARY_PATH}

Been running all day today and yesterday...


Patrick LoPresti commented Jun 04 '14, 4:39 p.m.

You do not need MOZILLA_FIVE_HOME nor LD_LIBRARY_PATH.


At least, I did not. I did need:

-Dorg.eclipse.swt.browser.DefaultType=mozilla
            
Also, you do not want to set UseWebKitGTK to "true", because WebKit is where the crash is. The point of XULRunner is to avoid WebKit.


Patrick LoPresti commented Jun 04 '14, 4:39 p.m.

See also this tech note (and commentary).

showing 5 of 7 show 2 more comments

3 other answers



permanent link
Kevin Ramer (4.5k6167186) | answered Apr 23 '14, 4:31 p.m.
I was seeing this a bunch so I also got xulrunner from one of the links I found and put it somewhere in my $HOME.  However, that didn't help very long.   I took out the -D...UseWebKitGTK=true [ or whatever that property value was ] and haven't had it crash since.  I don't see that -D in your output above.  Just adding my info in hopes of helping our heirs and assigns down the road :-D

permanent link
Gabriel Borges (314) | answered May 05 '14, 2:48 p.m.
edited May 05 '14, 2:49 p.m.
Gustavo, it may really be the XULRunner. I've already faced issues with it, but on Ubuntu 12.10 x64 and this is how I solved it:
  1. Download xulrunner from:

    ftp://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2011/06/2011-06-30-03-36-18-mozilla-1.9.2/xulrunner-1.9.2.19pre.en-US.linux-x86_64.tar.bz2

  2. Copy the file to /opt/

  3. Extract it with the following command:

    tar -xvjf xulrunner-1.9.2.19pre.en-US.linux-x86_64.tar.bz2

  1. Now you should have a folder /opt/xulrunner. Run the following commands to install the new xulrunner (borrowed and simplified from askubuntu.com/questions/125980/how-do-i-install-xulrunner-in-12-04):

    rm -r /usr/bin/xulrunner

    rm -r /usr/bin/xpcshell

    ln -s /opt/xulrunner/xulrunner /usr/bin/xulrunner

    ln -s /opt/xulrunner/xpcshell /usr/bin/xpcshell

  2. Modify RTC's eclipse.ini file by adding the following -vmargs parameter

-Dorg.eclipse.swt.browser.XULRunnerPath=/opt/xulrunner


Give it a try and let us know if it works or not. I hope so!

Gabriel.

permanent link
William Voorhees (25) | answered Jul 31 '14, 5:25 p.m.
JAZZ DEVELOPER
In addition to having an appropriate version of xulrunner installed on your system and having the -Dorg.eclipse.swt.browser.XULRunnerPath set, for more recent versions of eclipse you additionally need to set the flag: 
-Dorg.eclipse.swt.browser.DefaultType=mozilla
As Eclipse now defaults to using the webkit browser, which on Redhat 6.5 is incompatible.

Your answer


Register or to post your answer.