It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787
×7,383
×5,997
×383

question asked: Jan 08 '14, 2:22 p.m.
question was seen: 38,946 times
last updated: Feb 03 '15, 11:28 a.m.

Related questions

FAQ - How this Forum works

[SOLVED] Java was started but returned exit code=8096 on RTC Client

0
Joao Bosco Jares A. Chaves (32●4●8●13) | asked Jan 08 '14, 2:22 p.m.
edited Feb 23 '14, 6:32 p.m.
 Hi all,

I detected a issue on rtc client, at the moment that I make a load at any project. So eclipse closes, and a jvm window opens saying that: "Java was started but  returned exit code=8096". Below my configurations:

OS: Windows 7 Enterprise SP1- 64bits;
Processor:  Intel Core i7-2600
Memory: 8,00GB

Client: TeamConcert 4.0.5
Local client installation: C:\Program Files\TeamConcert405

Server: RTC 4.0.5
Local server installation: https://hub.jazz.net/

eclipse.ini:
-vm
C:\Program Files\TeamConcert405\jdk\jre\bin\javaw.exe
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20120913-144807
-install
C:/Program Files (x86)/IBM/TeamConcert405
-vmargs
-Xms206m
-Xmx1024m
-Xmnx64m
-Xgcpolicy:gencon
-Xscmx96m
-Xshareclasses:name=IBMSDP_%u


javacore.20140108.155427.6396.0002: http://tny.cz/0972847e
Exit code=8096 img attached.

Comments
Alwin Brands commented Jan 27 '14, 7:53 a.m. | edited Jan 27 '14, 8:13 a.m.

 Hi Joao, I had exactly the same problem, received identical Eclipse error log. I applied both solutions. For the first one I deleted that particular line. Don´t know how to flag a line as Comment (as REM worked in old DOS days).

Alas Eclipse still aborted. I received this error when loading the Repository Workspace into my Local Workspace.

Accepted answer

2
permanent link
Krzysztof Kaźmierczyk (7.4k●3●74●103) | answered Jan 09 '14, 3:17 a.m.
Hi Joao,
There is common issue and there are couple of tech notes regarding that:
http://www-01.ibm.com/support/docview.wss?uid=swg21656989
or http://www-01.ibm.com/support/docview.wss?uid=swg21303648 (the second one is for RAD but might be also applicable).
Please let us know if any of these technotes helped you.
Joao Bosco Jares A. Chaves selected this answer as the correct answer
Comments
Joao Bosco Jares A. Chaves commented Jan 09 '14, 8:50 a.m.

Hi Krzysztof Kazmierczyk, 


Thanks a lot, by fast response. So the problem was solved with the first link approach.
Best Regards!
:D

One other answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Joao Bosco Jares A. Chaves (32●4●8●13) | answered Jan 27 '14, 8:04 a.m.
 Hi Alwin brands, I removed all things as my eclipse.ini below:

-startup
plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.2.R36x_v20101222
-vm
jdk/jre/bin
--launcher.XXMaxPermSize
256m
-vmargs
-Xms100m
-Xmx512m
-Dosgi.requiredJavaVersion=1.6
-Dosgi.bundlefile.limit=100

Comments
Alwin Brands commented Jan 28 '14, 7:13 a.m.

Did you install RTC 4.0.5 as  64bit application? My eclipse.ini file has many more lines. Higher demand on memory I would say.


-vm
C:\Program Files\IBM\SDP\jdk\jre\bin\javaw.exe
-startup
plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
-install
C:\Program Files\IBM\SDP
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.2.R36x_v20101222
--launcher.XXMaxPermSize
256m
-vmargs
-Xquickstart
-Xms100m
-Xmx1024m
-Xmnx64m
-Xgcpolicy:gencon
-Xscmx96m
-Xnolinenumbers
-XX:MaxPermSize=128M
-Xcompressedrefs
-Dcom.ibm.ws.management.event.max_polling_interval=1000
-Djava.util.Arrays.useLegacyMergeSort=true
-Dosgi.requiredJavaVersion=1.5
-Dosgi.bundlefile.limit=100

2
Anthony Kesterton commented Feb 23 '14, 9:35 a.m.
JAZZ DEVELOPER

Removing the -Xshareclasses:name=IBMSDP_%u worked for me.  Thanks Krzysztof

Joao Bosco Jares A. Chaves commented Feb 23 '14, 6:28 p.m.

Thanks  Anthony :)

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.