On 16 Oct, 16:50, ap...@[EMAIL PROTECTED]
wrote:
> > Through Orbix 3.x, Iona's products were generally crap. I swear that
> > their patch numbers read like pi.
>
> Well, I have found what it the major difference as far as I am
> concerned. With OrbixWeb I cannot get auto-launch to work. My server
> follows exactly the same pattern as the equivalent C++ server, orb
> init, impl_is_ready(server, 0), processEvents etc and it works when
> started manually, but not when AL'd. This is driving me CRAZY !!!!!
With some significant help from Ciaran McHale from IONA this problem
has now been solved. I mention the solution here in the hope it may
help someone else in the future. It is environmental, there are
several undocumented Orbix env vars that are used to pass information
in the case of auto-launch. C/C++ has no problem picking these up but
in java they have to be passed a different way otherwise AL does not
work. Here's what you have to do:
PID=
SERVER_ENV=$IT_SERVER_COMMS\:$IT_SERVER_CODE\:$IT_SERVER_****T\:
$IT_SERVER_NAME\:$PID\:$IT_M
ARKER_PATTERN\:$IT_SERVER_MARKER\:$IT_ACT_POLICY\::$IT_WELL_KNOWN_****T
\:$IT_IIOP_****T
if [ $SERVER_ENV = "::::::::::" ]; then
AUTO_LAUNCH_ARGS=''
else
if [ $SERVER_ENV = "::::::::::" ]; then
AUTO_LAUNCH_ARGS=''
else
AUTO_LAUNCH_ARGS=-Dorbixweb.env=$SERVER_ENV
fi
then you add $AUTO_LAUNCH_ARGS to the command line arguments of the
java interpreter. This causes the env vars to be picked up via the
java property orbixweb.env.
Regards,
Andrew Marlow
|
