4 Replies Latest reply: Sep 8, 2011 1:19 PM by Brian Fox RSS

JMS provider failure detected for  ***MDB

song ke Newbie

Running JBoss 4.0.5 GA with JBoss MQ on Sun JVM 1.4, HP-UNIX, in a clustered configuration

After a variable period of activity (from 2 hours to a week), I get exception from the MDB Container:

Then the container reconnects to JMS after the 10seconds wait and fails again 120 seconds later.

WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected for xxxMDB
org.jboss.mq.SpyJMSException: Exiting on IOE; - nested throwable: (java.net.SocketTimeoutException:
Read timed out)
 at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:78)
 at org.jboss.mq.Connection.asynchFailure(Connection.java:420)
 at org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:174)
 at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:440)
 at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:372)
 at java.lang.Thread.run(Thread.java:534)
Caused by: java.net.SocketTimeoutException: Read timed out
 at java.net.SocketInputStream.socketRead0(Native Method)
 at java.net.SocketInputStream.read(SocketInputStream.java:129)
 at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
 at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:79)
 at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2133)
 at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2313)
 at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2380)
 at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2452)
 at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2601)
 at java.io.ObjectInputStream.readByte(ObjectInputStream.java:845)
 at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:317)


Then the container reconnects to JMS after the 10seconds wait and fails again 120 seconds later
12:11:34,100 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Waiting for reconnect internal 10
000ms for xxxMDB
12:11:44,147 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Trying to reconnect to JMS provid
er for xxxMDB
12:11:44,178 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnected to JMS provider for x
xxMDB
12:13:44,694 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected for
 xxxMDB


The whole is ending up in an out of memory exception a few hours later.
Any ideas ?
Thanks in advance,

  • 1. Re: JMS provider failure detected for  ***MDB
    Al Sakhapour Newbie

    Is any information available on below posting? We are using Jboss 4.2.1 GA and seeing same issue periodically. The follow is the warning messages occurring and after few hours we also get out of memory errors and nothing works after that until we restart Jboss.

     

    2010-03-05 01:15:15,208  WARN  [org.jboss.resource.adapter.jms.inflow.JmsActivation] Failure in jms  activation  org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@2bfad9(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@12343d4  destination=queue/SportsPageDataQueue isTopic=false tx=true durable=false  reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1  minSession=1 maxSession=15 keepAlive=60000 useDLQ=true  DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler  DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)

    org.jboss.mq.SpyJMSException:  Exiting on IOE; - nested throwable: (java.net.SocketTimeoutException: Read timed  out)

            at  org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:72)

            at  org.jboss.mq.Connection.asynchFailure(Connection.java:423)

            at  org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:174)

            at  org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:439)

            at  org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:371)

            at  java.lang.Thread.run(Thread.java:595)

    Caused by:  java.net.SocketTimeoutException: Read timed out

            at  java.net.SocketInputStream.socketRead0(Native  Method)

            at  java.net.SocketInputStream.read(SocketInputStream.java:129)

            at  java.io.BufferedInputStream.fill(BufferedInputStream.java:218)

            at  java.io.BufferedInputStream.read(BufferedInputStream.java:235)

            at  org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:79)

            at  java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2196)

            at  java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2376)

            at  java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2443)

            at  java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2515)

            at  java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2664)

            at  java.io.ObjectInputStream.readByte(ObjectInputStream.java:875)

            at  org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:316)

            ... 1  more

  • 2. Re: JMS provider failure detected for  ***MDB
    Adrian Brock Master
    Try the latest version, then come back to us if you still have the problem.
  • 3. Re: JMS provider failure detected for  ***MDB
    John Heijm Newbie

    Hi Adrian,

     

    Can you please give a specific answer to this question? We are experiencing this exact issue. We do not have the option to try the latest version as a real customer using our product out in the field is experiencing this. There is no option to upgrade, but we need this problem solved.

     

    Thanks.

  • 4. Re: JMS provider failure detected for  ***MDB
    Brian Fox Newbie

    Anyone found a solution for this other then upgrade to latest?  I'm running in to the same issue.  Periodically this happens, to our master in a cluster of servers.

     

    JBoss:  4.2.3GA

     


    Thanks