It's all about the answers!

Ask a question

RTC Client unexpectedly exits on Fedora 10 x86_64


Colin Coates (9121) | asked Apr 06 '09, 5:36 p.m.
I used "RTC-Eclipse-Client-1.0.1.1GA-Linux-Local.zip" to install a stand-alone installation of the RTC Client onto Fedora 10 x86_64.

I use the GNOME menu option "Applications->IBM Rational Team Concert->IBM Rational Team Concert" to invoke the Client; the RTC Client begins to load, but then unexpectedly exits. The following message is displayed in a dialog window:

JVM terminated. Exit code=160
/opt/ibm/TeamConcert/jdk/jre/bin/javaw
-Xjit:exclude={com/ibm/team/coverage/internal/common/report/SourceElementInfo.write*}
-Xms100m
-Xmx512m
-Dosgi.requiredJavaVersion=1.5
-jar /opt/ibm/TeamConcert/startup.jar
-os linux
-ws gtk
-arch x86
-showsplash
-launcher /opt/ibm/TeamConcert/eclipse
-name Eclipse
--launcher.library /opt/ibm/TeamConcert/eclipse_1023.so
-startup /opt/ibm/TeamConcert/startup.jar
-exitdata 1b001a
-product com.ibm.team.concert.product
-vm /opt/ibm/TeamConcert/jdk/jre/bin/javaw
-vmargs
-Xjit:exclude={com/ibm/team/coverage/internal/common/report/SourceElementInfo.write*}
-Xms100m
-Xmx512m
-Dosgi.requiredJavaVersion=1.5
-jar /opt/ibm/TeamConcert/startup.jar


Does anyone have an idea about how I can fix this problem?

9 answers



permanent link
Wai Chan (611) | answered Jun 10 '10, 10:24 a.m.
I am using ubuntu 10.04. When I open the history tab of any work item, the RTC will crash.
!ENTRY org.eclipse.ui.console 4 120 2010-06-10 22:16:34.037
!MESSAGE An exception occurred during console notification
!STACK 0
org.eclipse.swt.SWTException: Device is disposed
at org.eclipse.swt.SWT.error(SWT.java:3777)
at org.eclipse.swt.SWT.error(SWT.java:3695)
at org.eclipse.swt.SWT.error(SWT.java:3666)
at org.eclipse.swt.widgets.Display.error(Display.java:1142)
at org.eclipse.swt.widgets.Display.asyncExec(Display.java:664)
at org.eclipse.ui.internal.console.ConsoleDropDownAction.consolesRemoved(ConsoleDropDownAction.java:150)
at org.eclipse.ui.internal.console.ConsoleManager$ConsoleNotifier.run(ConsoleManager.java:154)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.ui.internal.console.ConsoleManager$ConsoleNotifier.notify(ConsoleManager.java:174)
at org.eclipse.ui.internal.console.ConsoleManager.fireUpdate(ConsoleManager.java:262)
at org.eclipse.ui.internal.console.ConsoleManager.removeConsoles(ConsoleManager.java:244)
at org.eclipse.ui.console.ConsolePlugin.stop(ConsolePlugin.java:175)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$3.run(BundleContextImpl.java:1050)
at java.security.AccessController.doPrivileged(AccessController.java:251)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:1046)
at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:457)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:531)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1104)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:655)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:312)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:257)
at org.eclipse.osgi.framework.internal.core.SystemBundle.suspend(SystemBundle.java:236)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:678)
at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:576)
at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.java:41)
at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:424)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:200)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

Anyone knows how to fix the problem?

permanent link
vadenasy bharma (6) | answered Dec 09 '09, 6:31 a.m.
Can you use the same code and commands that you use to set up Red Hat Fedora server to set up Ubuntu server? I have Ubuntu 7.04 server running on an older comp. i have and im trying to teach myself how to get a web server running. I've got a lot of info off of the web, but i also came across the Red Hat Fedora and Enterprise Linux Bible 4 . I wanted to know if i could use that to work on my Ubuntu 7.04 server?
_________________________
keyword research ~ keyword tool ~ keyword tracking ~ affiliate elite

permanent link
Colin Coates (9121) | answered May 08 '09, 6:14 a.m.
Great suggestion, and thanks very much Mathias,

I slightly finessed your suggested solution for my specific case. Please note the installation of a Fedora 10 rpm to provide the missing xulrunner 1.8:

1. In GNOME, navigate the menus "System->Administration->Add/Remove Programs".

2. Search for xulrunner.

3. Select "Xulrunner for IBM Lotus Notes 8", which is the "xulrunner-lwp-1.8.1.13-1 (i386)" RPM, and then install. Obviously, this could be done from the command line using yum.

4. Use the command line to:

echo -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-1.8.1.13-lwp >> /opt/IBM/TeamConcert_1/eclipse.ini


... or similar! ;)

Thanks again!
Colin

permanent link
Mathias Hermansson (43166) | answered May 02 '09, 6:21 p.m.
Hi,

A better work around is to download Xulrunner 1.8 (RHEL5 and Fedora 10 with Firefox are packaged with Xulrunner 1.9) from Mozilla, and then edit the eclipse.ini file in the TeamConcert directory to point out the correct Xulrunner.

Detailed instructions:

1. Download Xulrunner 1.8 to /tmp.
2. Unpack the tar.gz to /usr/local/lib:
# cd /usr/local/lib

# tar -xvzf /tmp/xulrunner-1.8.0.4.en-US.linux-i686.tar.gz

3. Append the org.eclipse.swt.browser.XULRunnerPath Java property to point out the newly installed Xulrunner 1.8 in eclipse.ini:
# echo -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/local/lib/xulrunner >>/opt/IBM/TeamConcert/eclipse.ini


Regards,
Mathias

permanent link
Colin Coates (9121) | answered Apr 08 '09, 8:35 a.m.
Thanks for the suggestion, Vishnu.

I will give your suggestion a try!

Kind Regards,
Colin

permanent link
vishnu kumar (66157) | answered Apr 08 '09, 7:57 a.m.
I have encountered same problem while starting RTC client.however i am able to start it forcefully using following command.

/opt/IBM/TeamConcert/jdk/jre/bin/java -jar /opt/IBM/TeamConcert/startup.jar

Please try it...hopefully it will work..I am not sure whether it restrict some features or not.

Thanks
Vishnu

permanent link
Colin Coates (9121) | answered Apr 08 '09, 6:37 a.m.
Hi Jared (and thanks for replying),

I have the following installed:
xulrunner-1.9.0.8-1.fc10 (i386);
xulrunner-1.9.0.8-1.fc10 (x86_64);
xulrunner-devel-1.9.0.8-1.fc10 (x86_64).

Side-issue:
Without wishing to start a flame war here (I was previously involved with developing something using XUL), is there any reason the installer does not just use the facilities provided by GTK+/GNOME?

Kind Regards,
Colin

permanent link
Jared Burns (4.5k29) | answered Apr 07 '09, 3:39 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
On Tue, 07 Apr 2009 07:28:04 +0000, colinc wrote:
Any suggestions about how I can fix the problem will be gratefully
received?

Sorry, I haven't seen anything like this before.

Random stab in the dark - do you have an up-to-date version of xulrunner
installed? The first thing the workbench tries to do is show a welcome
page that I believe is rendered as a webpage.

--
Jared Burns
Jazz Process Team

permanent link
Colin Coates (9121) | answered Apr 07 '09, 3:27 a.m.
I used "RTC-Eclipse-Client-1.0.1.1GA-Linux-Local.zip" to install a stand-alone installation of the RTC Client onto Fedora 10 x86_64.

I use the GNOME menu option "Applications->IBM Rational Team Concert->IBM Rational Team Concert" to invoke the Client; the RTC Client begins to load, but then unexpectedly exits. The following message is displayed in a dialog window:

JVM terminated. Exit code=160
/opt/ibm/TeamConcert/jdk/jre/bin/javaw
-Xjit:exclude={com/ibm/team/coverage/internal/common/report/SourceElementInfo.write*}
-Xms100m
-Xmx512m
-Dosgi.requiredJavaVersion=1.5
-jar /opt/ibm/TeamConcert/startup.jar
-os linux
-ws gtk
-arch x86
-showsplash
-launcher /opt/ibm/TeamConcert/eclipse
-name Eclipse
--launcher.library /opt/ibm/TeamConcert/eclipse_1023.so
-startup /opt/ibm/TeamConcert/startup.jar
-exitdata 1b001a
-product com.ibm.team.concert.product
-vm /opt/ibm/TeamConcert/jdk/jre/bin/javaw
-vmargs
-Xjit:exclude={com/ibm/team/coverage/internal/common/report/SourceElementInfo.write*}
-Xms100m
-Xmx512m
-Dosgi.requiredJavaVersion=1.5
-jar /opt/ibm/TeamConcert/startup.jar


Does anyone have an idea about how I can fix this problem?

I also tried re-installing using "RTC-Client-2.0Beta1-Linux-Local.zip".

This gave my a similar error message during startup:

JVM terminated. Exit code=160

/opt/ibm2/TeamConcert/jdk/jre/bin/javaw
-Xjit:exclude={com/ibm/team/coverage/internal/common/report/SourceElementInfo.write*}
-Xms100m
-Xmx512m
-Dosgi.requiredJavaVersion=1.5
-jar /opt/ibm2/TeamConcert/startup.jar
-os linux
-ws gtk
-arch x86
-showsplash
-launcher /opt/ibm2/TeamConcert/eclipse
-name Eclipse
--launcher.library /opt/ibm2/TeamConcert/eclipse_1023.so
-startup /opt/ibm2/TeamConcert/startup.jar
-exitdata 238025
-vm /opt/ibm2/TeamConcert/jdk/jre/bin/javaw
-vmargs
-Xjit:exclude={com/ibm/team/coverage/internal/common/report/SourceElementInfo.write*}
-Xms100m
-Xmx512m
-Dosgi.requiredJavaVersion=1.5
-jar /opt/ibm2/TeamConcert/startup.jar


Any suggestions about how I can fix the problem will be gratefully received?

Your answer


Register or to post your answer.


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.