Announcement

Collapse
No announcement yet.

Help diagnosing a Mirth crash

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Help diagnosing a Mirth crash

    I'm not sure if this is a Mirth problem or a Java problem.

    4 days ago one of my Mirth instances crashed with the only relevant message in the logs being this from wrapper.log:

    Code:
    ERROR  | wrapper  | 2008/04/25 18:28:12 | JVM appears hung: Timed out waiting for signal from JVM.
    ERROR  | wrapper  | 2008/04/25 18:28:12 | JVM did not exit on request, terminated
    STATUS | wrapper  | 2008/04/25 18:28:14 | JVM exited in response to signal SIGKILL (9).
    ERROR  | wrapper  | 2008/04/25 18:28:14 | Unable to start a JVM
    Any ideas as to what caused this? How can I prevent it from happening again??
    Jon Bartels

    Zen is hiring!!!!
    http://consultzen.com/careers/
    Talented healthcare IT professionals wanted. Engineers to sales to management.
    Good benefits, great working environment, genuinely interesting work.

  • #2
    Re:Help diagnosing a Mirth crash

    I googled it and found this here

    http://wrapper.tanukisoftware.org/do...eshooting.html

    Because the Wrapper is using a pinging mechanism to check on the health of the JVM, it is possible that the Wrapper will think that the JVM is hung when it isn't if another process is taking 100% of the CPU for longer than 30 seconds. This will result in an entry like the following in your log file, and the JVM being restarted:

    The property wrapper.ping.timeout=30 in conf/wrapper.log can be used to extend this timeout. But be aware that this will also lengthen the amount of time that your application will remain hung in the event of a real problem.
    Chris Ro
    Sr. Software Engineer | Mirth Corporation

    Comment


    • #3
      Re:Help diagnosing a Mirth crash

      chrisr wrote:
      I googled it and found this here

      http://wrapper.tanukisoftware.org/do...eshooting.html

      Because the Wrapper is using a pinging mechanism to check on the health of the JVM, it is possible that the Wrapper will think that the JVM is hung when it isn't if another process is taking 100% of the CPU for longer than 30 seconds. This will result in an entry like the following in your log file, and the JVM being restarted:

      The property wrapper.ping.timeout=30 in conf/wrapper.log can be used to extend this timeout. But be aware that this will also lengthen the amount of time that your application will remain hung in the event of a real problem.
      I owe you a beer for doing my googling for me! :P

      That seems like a wierd side effect. I'm aware of a crash-prone app running on that server, so until that is fixed I'll have to increase that timeout.
      Jon Bartels

      Zen is hiring!!!!
      http://consultzen.com/careers/
      Talented healthcare IT professionals wanted. Engineers to sales to management.
      Good benefits, great working environment, genuinely interesting work.

      Comment

      Working...
      X