Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

JVM terminated. Exit code=255

907 views
Skip to first unread message

James

unread,
Apr 27, 2004, 12:30:16 AM4/27/04
to
Hello All,

I'm using WSAD 5.1.0, with P4 processor and 1GB of memory.
During development, sometimes the processor usage goes up high
looking like it's processing something "heavy". Then after
a while, WSAD shut-down with the error below in a dialog
box:

JVM terminated. Exit code=255
C:\WSAD5\.eclipse\jre\bin\javaw.exe
-Xj9
-cp C:\WSAD5\.\eclipse\startup.jar org.eclipse.core.launcher.Main
-os win32
-ws win32
-arch x86
-showsplash C:\WSAD5\.\eclipse\eclipse.exe -showsplash 600
-data C:\WSAD5\WORKSPACE

It don't happen frequently and only let's say once every forth-night.
But certainly this is quite annoying as I might lost some un-saved works.

Anyone has anything to comment on this WSAD behaviour ?


Thanks in advance.

Wolfgang Heintz

unread,
Apr 29, 2004, 2:14:42 AM4/29/04
to
Remove the entry "-Xj9" from the VMArgs-Line in your File
"wsappdev.ini" and the WSAD (Vers. 5.1) will work without Problems.

Wolfgang

Ravi Yagatili

unread,
May 10, 2004, 3:06:55 PM5/10/04
to
Wolfgang,

What does -Xj9 do & mean?

Thanks
Ravi


wolfgan...@epost.de (Wolfgang Heintz) wrote in message news:<4078b659.04042...@posting.google.com>...

Peter Manahan

unread,
May 10, 2004, 4:10:24 PM5/10/04
to
J9 is the JVM that WSAD supports/tested with. Once you remove it you are
working in an unsupported configuration. Addtionally WSAD's performance
will decrease.

Your best bet would be to open a problem report with support in order to
get it resolved. They may already have a fix for the problem or a
workaround.

Peter

Jan Nicklisch

unread,
Jan 27, 2005, 9:41:53 AM1/27/05
to
WIN2000, SP4

Removing the argument "-Xj9" didn't help us, but

deinstalling (!) the virus scanner BitDefender did help

(stopping alone didn't).


JN


0 new messages