Start timeout in wrapper_enhydra.conf

[James Carnegie <james@xxxxxxxxxxxxxx>]

Dear All,

We are experiencing a small problem with the start/stop wrapper in
enhydra 5.1. Our application takes about 2 mins to start.

Although we have set up
'/usr/local/enhydra5.1/util/services/wrapper_enhydra.conf' as follows:

----------------------------------------------
# Number of seconds to allow for the JVM to be launched and contact the
#  wrapper before the wrapper should assume that the JVM is hung and
#  terminate the JVM process.  0 means never time out.  Defaults to
#  30 seconds.
wrapper.startup.timeout=0

# Number of seconds to allow between the wrapper pinging the JVM and the
#  response.  0 means never time out.  Defaults to 30 seconds.
wrapper.ping.timeout=0
----------------------------------------------


the wrapper seems to try to kill the VM, which fails, then tries to
restart the application in another VM:

----------------------------------------------
wrapper  | Startup failed: Timed out waiting for signal from JVM.
wrapper  | JVM did not exit on request, terminated
wrapper  | Launching a JVM...
----------------------------------------------

Two other little things:

1)      Is it possible to run two instances of enhydra 5.1 on the same
        machine (of course we can do it with our own wrappers, but does       
  the
standard install support this?)

2)      When the start/stop wrapper is initiated from the command line  such:
`/etc/init.d/multiserverStart start`, standard out is   redirected to the
console. This means that the ssh session we     used to call the script is
held open etc. This isn't a show        stopper, but seems a bit weird. Why is
the output sent to the  console?

Regards,
James.