|
From: Leif M. <le...@ta...> - 2003-11-12 16:03:55
|
Eric,
Could you set the wrapper.debug=true property and rerun your test?
Then post
back with the wrapper.log and wrapper.conf file from one of the
applications that is
failing on you.
Without the log output I am guessing. But what integration method
did you use
to integrate with the Wrapper? If you are using method #3
(WrapperListener) then
it may be that you are not handling the LOGOUT event correctly in the
controlEvent
method. I should be able to tell from the wrapper.log/wrapper.conf files.
Cheers,
Leif
PS. I'm sure it was unintentional, but it looks like you replied to a
digest mail of the
day's emails so that all got posted as well. When posting a new thread,
please always
start a new mail rather than replying to an existing email. It helps me
to keep the
various threads strait and makes sure that emails don't get lost. :-)
EXT-Smith, Eric M wrote:
>Leif, et. al,
>
>I have an interesting situation on one of my machines here and am my wits end to explain what is happening.
>
>I have three W2K machines, each of which has three separate services launched during the boot process using the wrapper. On two of the machines, everything appears to be fine. On the third machine, everything starts fine, but if someone logs into the box and then logs out, the services are all terminated.
>
>The services use RMI, Java 1.4.1_02, JDBC to MySQL, and normal socket communications.
>
>Any suggestions?
>
>Eric Smith
>InfoStructure Systems
>Boeing Chairman's Innovation Initiative
>
>
|