Topic
  • 1 reply
  • Latest Post - ‏2013-12-20T09:40:51Z by AlexFleischer
JorgeAlvarez
JorgeAlvarez
1 Post

Pinned topic OPL error launching from java 1.6 (ODM v3.3)

‏2013-12-02T17:09:13Z |

Hi.

We have an ODM app run in an AIX5.3, that we execute from a custom java application using the OPL api. Before, this app worked fine when we launched from this app compiled in java 1.5, but now, compiled in java 1.6 the app fails when the OPL optimization starts. This is the error:

- ERROR -Error creating Java Runtime Environment (did you set wrong parameters in ODMS_JAVA_ARGS?): Unable to create the virtual machine. The error was -1

- ERROR -No JVM running, see previous messages

- ERROR -No JVM running, see previous messages

- ERROR -No JVM running, see previous messages

- ERROR -No JVM running, see previous messages

- WARN  -Re-generating an immutable OPL model has no effect.

- ERROR -Scripting runtime error: (in generate) Processing OPL model "workaround_163" failed..

- ERROR -Execution of "main" failed: "jar:file:/opt/IBM/ODME_331/OPTCOM/OPTCOM_server-xmlrpc_V02R00F00/bin/../oplproject_batch/deploy/myodmapplication.odmapp!/workaround_163.mod", line 62: generate: Processing OPL model "workaround_163" failed.

In the dev environment (Windows 7, and same configuration, the app works fine).

All test that we've done with jre 1.6 or jdk 1.6 has failed.

The difference that we've found has been that in the jre/jdk 1.5 installation the libraries libjava.a and libjvm.a, which are necessary like says the documentation, are in the path /java_1.5_intallation_path/jre/bin and in the jre/jdk 1.6 installation are in the path /java_1.6_installation_path/jre/lib/ppc/.

The  OPL documentation says that this libraries must to be set in  the LIBPATH environment variable. We've done this, but the result was the same. (OPL Doc: Documetation.)

Thanks.

Best Regards.

Updated on 2013-12-02T19:08:27Z at 2013-12-02T19:08:27Z by JorgeAlvarez
  • AlexFleischer
    AlexFleischer
    1247 Posts

    Re: OPL error launching from java 1.6 (ODM v3.3)

    ‏2013-12-20T09:40:51Z  

    Hi,

    I think that a PMR was logged for this and the issue is now solved.

    Regards