|
From: Leif M. <le...@ta...> - 2004-01-22 00:30:43
|
Willy,
Whenever you encounter problems like this, the first thing you
should try is to
set the wrapper.debug=true property in the configuration file. When
you relaunch
the wrapper you will get a host of useful information, including the
full command
line used to launch the JVM. Take a close look at the library path
that the
Wrapper is generating and make sure that it is what you are expecting.
UNIX platforms show the command as an array. For debugging it is
possible
to copy the command into an empty shell script and launch the JVM manually.
(If you try this, the wrapper.key system property must be removed from the
generated command line.) This has proved useful mainly as a confidence
builder
to prove that the Wrapper is or is not the cause of a given problem.
Cheers,
Leif
Marc Wilson wrote:
>I noticed you have /opt/mqm//lib as the second path (note the //).
>
>Could that // instead of / be causing the prob?
>
>-M
>
>
>
>>-----Original Message-----
>>From: wra...@li... [mailto:wrapper-user-
>>ad...@li...] On Behalf Of Brandsdorfer, William
>>Sent: Thursday, 22 January 2004 4:54 AM
>>To: wra...@li...
>>Subject: [Wrapper-user] multiple wrapper.java.liibrary.path statements
>>
>>Greetings,
>>
>>I'm having trouble wrapping a Java program that uses multiple native
>>libraries. The application is a JMS (IBM) MQSeries program that
>>
>>
>normally
>
>
>>requires
>>LD_LIBRARY_PATH = /opt/mqm/lib:/opt/mqm/java/lib (I'm running on
>>
>>
>Solaris -
>
>
>>wrapper 3.0.5)
>>
>>My config has the following
>>
>>
>>
>>
>wrapper.java.library.path.1=/etrade/home/wbrandsd/tools/wrapper_solaris_
>3.
>
>
>>0.5/lib
>>wrapper.java.library.path.2=/opt/mqm//lib
>>wrapper.java.library.path.3=/opt/mqm/java/lib
>>
>>But when I run it I get:
>>
>>Exception in thread "main" java.lang.UnsatisfiedLinkError: no mqjbnd04
>>
>>
>in
>
>
>>java.library.path
>>
>>I know that the path exists because the program runs fine when I set
>>LD_LIBRARY_PATH and run it without the wrapper.
>>I've also used the wrapper successfully on another (non-MQSeries)
>>
>>
>program
>
>
>>Is there a known problem with multiple wrapper.java.library.paths?
>>
>>Thanks,
>>Willy
>>
>>
|