Version 2

    Why do I get this error and why do my MDBs quit processing when I get this error?


    2008-09-28 00:51:21,859 WARN  [org.jboss.mq.server.BasicQueue]
    
            Caught unusual exception sending message to receiver.
    
            org.jboss.util.threadpool.ThreadPoolFullException:
    
            java.lang.InterruptedException
    
                   at
    
            org.jboss.util.threadpool.BasicThreadPool.execute(BasicThreadPool.java:417)
    
                   at
    
            org.jboss.util.threadpool.BasicThreadPool.runTaskWrapper(BasicThreadPool.java:192)
    
                   at
    
            org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:212)
    
                   at
    
            org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:206)
    
                   at
    
            org.jboss.mq.server.ClientConsumer.queueMessageForSending(ClientConsumer.java:125)
    
                   at
    
            org.jboss.mq.server.BasicQueue.queueMessageForSending(BasicQueue.java:1161)
    
                   at
    
            org.jboss.mq.server.BasicQueue.internalAddMessage(BasicQueue.java:1132)
    
                   at org.jboss.mq.server.BasicQueue.access
    
            $000(BasicQueue.java:76)
    
                   at org.jboss.mq.server.BasicQueue
    
            $AddMessagePostCommitTask.run(BasicQueue.java:1399)
    
                   at org.jboss.mq.pm.Tx.commit(Tx.java:217)
    
                   at
    
            org.jboss.mq.pm.TxManager.commitTx(TxManager.java:113)
    
                   at
    
            org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:468)
    
                   at
    
            org.jboss.mq.server.ClientMonitorInterceptor.transact(ClientMonitorInterceptor.java:168)
    
                   at
    
            org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:126)
    
                   at
    
            org.jboss.mq.security.ServerSecurityInterceptor.transact(ServerSecurityInterceptor.java:197)
    
                   at
    
            org.jboss.mq.server.TracingInterceptor.transact(TracingInterceptor.java:352)
    
                   at
    
            org.jboss.mq.server.JMSServerInvoker.transact(JMSServerInvoker.java:132)
    
                   at
    
            org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:194)
    
                   at org.jboss.mq.il.uil2.SocketManager
    
            $ReadTask.handleMsg(SocketManager.java:417)
    
                   at
    
            org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398)
    
                   at EDU.oswego.cs.dl.util.concurrent.PooledExecutor
    
            $Worker.run(PooledExecutor.java:761)
    
                   at java.lang.Thread.run()V(Unknown Source)
    

     

    You get this error becuase of a bug in the Oswego concurrent libraries.  This is an issue that we have worked around in JBoss mq.

     

    It is fixed in the community 4.2.3 and it will be fixed in EAP 4.2 CP06.

     

     

    [1] Link to the jira issue that identifies this.  https://jira.jboss.org/jira/browse/JBAS-5354