SOLVED RE: [Wrapper-user] Environment problems?

[Roberts, E. <Eri...@on...>]

Leif,

I unintentionally ran this program from the command line without having =
run .profile and got exactly the same error - so the problem is the =
environment variables, and nothing to do with the wrapper.

Someone has screwed up the .profile script on my test system!

Thanks for your clarification about the environment variables anyway.

Regards

Eric=20

-----Original Message-----
From: Leif Mortenson [mailto:le...@ta...]
Sent: 21 May 2003 18:21
To: wra...@li...
Subject: Re: [Wrapper-user] Environment problems?


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
> =20
>
    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




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user