Menu ▾ ▴

#67 Wrapper stop - no errors

open
None
5
2004-11-12
2004-10-19
Anonymous
No

The Wrapper goes down for no reason. We have
configured our services to be restarted 15 minutes after
failure. So they get restarted. But am not sure why the
wrapper should go down.
The last line that is printed on the log file is
SERVICE_CONTROL_INTERROGATE
Attached abstract of the wrapper log file
Note : At 3:32 - wrapper stopped ( I guess ). Don't
know why??
At 3:47 - Service was restarted again.

Discussion

  • Nobody/Anonymous

    Wrapper log file

     
  • Nobody/Anonymous

    Logged In: NO

    Log file is attached.. Please ignore the previous post

     
  • Leif Mortenson

    Leif Mortenson - 2004-11-12
    • assigned_to: nobody --> mortenson
     
  • Leif Mortenson

    Leif Mortenson - 2004-11-12

    Logged In: YES
    user_id=228081

    What version of the Wrapper are you using? The log that
    you send shows a baly corrupted line of debug output just
    before the Wrapper exits:
    INFO | jvm 2 | 2004/10/19 03:32:46 | Received a packet
    PING : ping
    INFO | jvm 2 | 2004/10/19 03:32:46 | Send a packet PING
    ok
    DEBUGDX BUwra | rwr p er04/11000014/ 0/:32:3462|46 c| d a
    pGcekettrolHandlkr
    4)
    DEBUG | wrapper | 2004/10/19 03:32:46 |
    SERVICE_CONTROL_INTERROGATE
    STATUS | wrapper | 2004/10/19 03:47:47 | --> Wrapper
    Started as Service
    DEBUG | wrapperp | 2004/10/19 03:47:47 | server listening
    on port 17006.

    Most likely this is a synchronization problem that was fixed
    in version 3.1.1. I suggest 3.1.2 as there was a timing
    bug fixed there.

    Were you seeing this problem without debug output enabled?
    It was only a problem if the message from the signal handler
    thread attempted to print a message at the exact same
    instant as the main thread did the same?

    Cheers,
    Leif

     

Log in to post a comment.