Eric,
Do you know what part of your program is kicking this error out? It
appears as if the Wrapper launches the WrapperSimpleApp helper
normally and calls your configured main method.
The main method then displays some info about the current JVM,
Displays an error and then it looks like it calls System.exit() I say that
because during the same second, the shutdown hook is triggered.
>INFO | jvm 1 | 2003/05/19 13:32:58 | WrapperSimpleApp: start(args)
>INFO | jvm 1 | 2003/05/19 13:32:58 | WrapperSimpleApp: invoking main method
>INFO | jvm 1 | 2003/05/19 13:32:58 | Using Java HotSpot(TM) Client VM, 1.3.1-b24, mixed mode
>INFO | jvm 1 | 2003/05/19 13:32:59 | exception: Initialization failed for bus transport FtDefault
>INFO | jvm 1 | 2003/05/19 13:32:59 | Wrapper Manager: ShutdownHook started
>
>
Without knowing what you program is doing here is is difficult to
help. I tried doing a search but came up with nothing. If you could explain
what your code is doing there, it might help one of us to come up with
some ideas.
As fo the environment, that is entirely possible. The Wrapper launches
the JVM using the same user as was used to launch the Wrapper process.
The entire environment available to the Wrapper should also be available
to the JVM. Most environment related problems tend to be with the
environment in which the Wrapper itself is launched. I have not heard of
any problems, nor should there be any, where the JVM does not have
access to some part of the Wrapper's environment. The JVM process
is just forked, so the two should be identical.
Cheers,
Leif
|
