!!! WARNING !!! for all omnet/omnest users running on 64 bit linux systems.

[Rudolf Hornig]

It seems that different distros started to push out JVM 1.6.0.24 update recently. Unfortunately this build (and build 23 too) contains a serious bug and the 64-bit JVM just crashes when you try to run the IDE (32bit JVM is not affected). On windows we always use a 32-bit JVM so you can safely use any JVM version there.

Please read the description below for a possible workaround. 

Analysis: I have checked the issue and it turned out that this is a 64bit specific JVM bug (affecting both Linux and Windows versions of JDK build 23 and 24) (and both Sun/Oracle JDK and OpenJDK). It is not related to OMNET at all. Unfortunately there is no patch for it, but the next JVM builds will contain the fix:

http://bugs.sun.com/view_bug.do?bug_id=7002666

It was also reported on eclipse bug tracker:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=333227

There is a workaround though which suggests adding:

-XX:-UseCompressedOops

to the <OMNETPPROOT/>ide/omnetpp.ini file. This will disable the problematic JIT code generation path.

Please report me back if it does/doesn't work. 

Rudolf

[Tami King]

On Mar 19, 4:57 am, Rudolf Hornig <rudolf.hor...@gmail.com> wrote:

> There is a workaround though which suggests adding:
>
> -XX:-UseCompressedOops
>
> to the <OMNETPPROOT/>ide/omnetpp.ini file. This will disable the
> problematic JIT code generation path.
>
> Please report me back if it does/doesn't work.

Thanks for the information. I have tried the workaround on both Linux
machines here and it
isn't working on either one. Since Gentoo only has builds 23 and 24
in portage I'll have to do
something more drastic, like work under Windows (I have 32 bit JVMs
there too) or more likely,
set up an overlay.

Tami

[Rudolf Hornig]

Hello, I've just retested it. The provided workaround does fix the issue on my system.

Be sure to check the spelling of the option AND put it into both

ide/omnetpp.ini

ide/linux64/omnetpp.ini

This is just required because when running ./configure then ide/omnetpp.ini gets overwritten with ide/linux64/omnetpp.ini

The other solution is that you try to find somewhere on the net an older JRE (pre b23) and put the whole jre under 

<omnetpproot>/ide/jre

directory. This will force eclipse to use the private JRE instead of the installed one.

Rudolf

--
You received this message because you are subscribed to the Google Groups "omnetpp" group.
To post to this group, send email to omn...@googlegroups.com.
To unsubscribe from this group, send email to omnetpp+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/omnetpp?hl=en.

[Tami King]

On Mar 19, 10:30 am, Rudolf Hornig <rudolf.hor...@gmail.com> wrote:
> Hello, I've just retested it. The provided workaround does fix the issue on
> my system.
> Be sure to check the spelling of the option AND put it into both
>
> ide/omnetpp.ini
> ide/linux64/omnetpp.ini
>
> This is just required because when running ./configure then ide/omnetpp.ini
> gets overwritten with ide/linux64/omnetpp.ini
>
> The other solution is that you try to find somewhere on the net an older JRE
> (pre b23) and put the whole jre under
>
> <omnetpproot>/ide/jre
>
> directory. This will force eclipse to use the private JRE instead of the
> installed one.

I checked all of the files, and installed Java 1.6.0_21, but it still
crashes. Is there some
config directory someplace that I need to clean out? I removed
my .metadata directory
but that didn't help.

Tami

[Rudolf Hornig]

No, the .metadata and other issues should not affect this. Please ensure that the command line is really in effect:

Start OMNET++ (do not open any projects) (it should not crash in this case).

Help / About OMNeT++ / Installation Details / Configuration (tab).

check for the correct JAVA version there and the added extra command line parameter should appear in that text too. If you cannot find it there that you probably starting some other instance of omnet, or something other weirdness is going on :)

Rudolf

Tami

[Tami King]

On Mar 19, 12:57 pm, Rudolf Hornig <rudolf.hor...@gmail.com> wrote:

> check for the correct JAVA version there and the added extra command line
> parameter should appear in that text too. If you cannot find it there that
> you probably starting some other instance of omnet, or something other
> weirdness is going on :)

It might have to be weirdness at this point. On machine shows:

eclipse.vm=/usr/bin/java
eclipse.vmargs=-Xms128m
-Xmx512m
-XX:MaxPermSize=192m
-XX:-UseCompressedOops
-jar
/opt/omnetpp-4.1/ide/plugins/
org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar

with java:

java.version=1.6.0_23

The other machine has

java.version=1.6.0_21

omnetpp still dies on both machines.

Tami