RE: [Wrapper-user] Environment problems?

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

Leif,

Firstly thanks for the response.

The application is third party (Tibco Integration Manager), so I can =
only give you a rough idea of what is taking place.

The program is designed to be fault tolerant - the first "engine" is =
started with a flag which tells it to establish a fault tolerant bus =
transport, subsequent "engines" search for existing engines with the =
same group name and form a fault tolerant cluster. The exception is =
occurring when the first instance attempts to establish the fault =
tolerant bus transport (hence the error message "Initialization failed =
for bus transport FtDefault"). I believe that this transport is UDP.

Because I can successfully start the program from the command line, I =
thought at first to ask about how the wrapper passed environment =
settings. From your response it would appear that the environment is not =
the issue.

Do you think that there could be some system resource conflict between =
the wrapper, and the application trying to establish the transport?

Another thought was permissions - but again, if I can run the program =
successfully from the same shell as I try to run the wrapper, then I =
cannot see that this could be an issue.

I hope that some genius out there might be able to hint at what the =
problem might be and a possible fix, as I currently have many of these =
programs to support in a production environment, and the wrapper seemed =
the perfect solution for automatic restarting.

Regards

Eric

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