Announcement

Collapse
No announcement yet.

Mirth through OutofMemorey after 2000 msg

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

  • Mirth through OutofMemorey after 2000 msg

    Hi,
    After processing 2000 messages the admin tool is not working and it giving the following message. Did any one observed this behaviour.

    Thank you
    Ram

    java.lang.OutOfMemoryError: unable to create new native thread
    at java.lang.Thread.start0(Native Method)
    at java.lang.Thread.start(Unknown Source)
    at org.mortbay.util.ThreadPool$PoolThread.enterPool(T hreadPool.java:448)
    at org.mortbay.util.Pool.newPondLife(Pool.java:375)
    at org.mortbay.util.Pool.get(Pool.java:305)
    at org.mortbay.util.ThreadPool.run(ThreadPool.java:36 8)
    at org.mortbay.util.ThreadedServer$Acceptor.run(Threa dedServer.java:640)
    WARN 2008-11-13 14:56:39,188 [Acceptor ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080]] org.mortbay.util.ThreadedServer: EXCEPTION
    java.lang.OutOfMemoryError: unable to create new native thread
    at java.lang.Thread.start0(Native Method)
    at java.lang.Thread.start(Unknown Source)
    at org.mortbay.util.ThreadPool$PoolThread.enterPool(T hreadPool.java:448)
    at org.mortbay.util.Pool.newPondLife(Pool.java:375)
    at org.mortbay.util.Pool.get(Pool.java:305)
    at org.mortbay.util.ThreadPool.run(ThreadPool.java:36 8)
    at org.mortbay.util.ThreadedServer$Acceptor.run(Threa dedServer.java:640)

  • #2
    Re:Mirth through OutofMemorey after 2000 msg

    The problem seems related to the creation of too-much threads. Mirth launch a thread for each new message is received. IT seems that process of the message takes too much time in being processed.

    You can read the next link to check how create more threads:

    http://answers.google.com/answers/threadview?id=344545

    Comment


    • #3
      Mirth through OutofMemorey after 2000 msgs

      Thank you for the help.

      I have changed the threads count by putting the following in wrapper.conf

      wrapper.java.additional.1=-Xss100k

      but I have noticed after starting the mirth the thread count is going up as time goes by. Before start of the Mirth we have 493 threads and once I started the mirth we got count 560. After 40 minutes, it went up to 850. It means the threads are not being closed and it will through OutMemoreyOf exception after some time.

      NOTE: We have not processed any messages. It was running and has file reader channels polling every 30 seconds.

      Any idea why the thread count is going up even without processing any messages.

      Thanks you
      Ram

      Post edited by: rampratapa, at: 11/17/2008 08:42

      Comment

      Working...
      X