5 Replies Latest reply on Oct 7, 2008 2:56 PM by Raghavan TV

    Error processing courier, backing off for 32000 milliseconds

    Raghavan TV Newbie

      I've deployed a ESB Service that contains around 60 esb services + 110 JMS Queue (JBM Queue) + 1 SQL-Provider Queue

      The moment I deploy the service, I receive a
      --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
      [MessageAwareListener] Error processing courier, backing off for 32000 milliseconds Error
      --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

      As result of this, my SQL-Provider also does not read any data from the source table. I saw a JIRA logged for a similar error for 4.3GA and the thread was closed citing that it was fixed in 4.4.

      Hence I deployed the smae service in 4.4 and continue to see the same error. Is there a limitation on number of esb services that can be used in a single deploy?

      --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
      server.log
      --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 DEBUG [org.jboss.soa.esb.listeners.message.MessageAwareListener] Courier Exception
      org.jboss.soa.esb.couriers.CourierException: Unable to create Message Consumer
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:406)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:386)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248)
      at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: org.jboss.soa.esb.couriers.CourierServiceBindException: Failed to get JMS Session from pool.
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:164)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:478)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:398)
      ... 7 more
      Caused by: org.jboss.internal.soa.esb.rosetta.pooling.ConnectionException: Could not obtain a JMS connection from the pool after 30s.
      at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:258)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:158)
      ... 9 more
      2008-10-06 10:55:45,078 DEBUG [org.jboss.soa.esb.listeners.message.MessageAwareListener] Courier Exception
      org.jboss.soa.esb.couriers.CourierException: Unable to create Message Consumer
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:406)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:386)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248)
      at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: org.jboss.soa.esb.couriers.CourierServiceBindException: Failed to get JMS Session from pool.
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:164)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:478)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:398)
      ... 7 more
      Caused by: org.jboss.internal.soa.esb.rosetta.pooling.ConnectionException: Could not obtain a JMS connection from the pool after 30s.
      at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:258)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:158)
      ... 9 more
      2008-10-06 10:55:45,078 DEBUG [org.jboss.soa.esb.listeners.message.MessageAwareListener] Courier Exception
      org.jboss.soa.esb.couriers.CourierException: Unable to create Message Consumer
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:406)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:386)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248)
      at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: org.jboss.soa.esb.couriers.CourierServiceBindException: Failed to get JMS Session from pool.
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:164)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:478)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:398)
      ... 7 more
      Caused by: org.jboss.internal.soa.esb.rosetta.pooling.ConnectionException: Could not obtain a JMS connection from the pool after 30s.
      at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:258)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:158)
      ... 9 more
      2008-10-06 10:55:45,078 DEBUG [org.jboss.soa.esb.listeners.message.MessageAwareListener] Courier Exception
      org.jboss.soa.esb.couriers.CourierException: Unable to create Message Consumer
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:406)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:386)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248)
      at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: org.jboss.soa.esb.couriers.CourierServiceBindException: Failed to get JMS Session from pool.
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:164)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:478)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:398)
      ... 7 more
      Caused by: org.jboss.internal.soa.esb.rosetta.pooling.ConnectionException: Could not obtain a JMS connection from the pool after 30s.
      at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:258)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:158)
      ... 9 more
      2008-10-06 10:55:45,078 DEBUG [org.jboss.soa.esb.listeners.message.MessageAwareListener] Courier Exception
      org.jboss.soa.esb.couriers.CourierException: Unable to create Message Consumer
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:406)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:386)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248)
      at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: org.jboss.soa.esb.couriers.CourierServiceBindException: Failed to get JMS Session from pool.
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:164)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:478)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:398)
      ... 7 more
      Caused by: org.jboss.internal.soa.esb.rosetta.pooling.ConnectionException: Could not obtain a JMS connection from the pool after 30s.
      at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:258)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:158)
      ... 9 more
      2008-10-06 10:55:45,078 DEBUG [org.jboss.soa.esb.listeners.message.MessageAwareListener] Courier Exception
      org.jboss.soa.esb.couriers.CourierException: Unable to create Message Consumer
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:406)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:386)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248)
      at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: org.jboss.soa.esb.couriers.CourierServiceBindException: Failed to get JMS Session from pool.
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:164)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:478)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:398)
      ... 7 more
      Caused by: org.jboss.internal.soa.esb.rosetta.pooling.ConnectionException: Could not obtain a JMS connection from the pool after 30s.
      at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:258)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:158)
      ... 9 more
      2008-10-06 10:55:45,078 DEBUG [org.jboss.soa.esb.listeners.message.MessageAwareListener] Courier Exception
      org.jboss.soa.esb.couriers.CourierException: Unable to create Message Consumer
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:406)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:386)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248)
      at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: org.jboss.soa.esb.couriers.CourierServiceBindException: Failed to get JMS Session from pool.
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:164)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:478)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:398)
      ... 7 more
      Caused by: org.jboss.internal.soa.esb.rosetta.pooling.ConnectionException: Could not obtain a JMS connection from the pool after 30s.
      at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:258)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:158)
      ... 9 more
      2008-10-06 10:55:45,078 DEBUG [org.jboss.soa.esb.listeners.message.MessageAwareListener] Courier Exception
      org.jboss.soa.esb.couriers.CourierException: Unable to create Message Consumer
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:406)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:386)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248)
      at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: org.jboss.soa.esb.couriers.CourierServiceBindException: Failed to get JMS Session from pool.
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:164)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:478)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:398)
      ... 7 more
      Caused by: org.jboss.internal.soa.esb.rosetta.pooling.ConnectionException: Could not obtain a JMS connection from the pool after 30s.
      at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:258)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:158)
      ... 9 more
      2008-10-06 10:55:45,078 DEBUG [org.jboss.soa.esb.listeners.message.MessageAwareListener] Courier Exception
      org.jboss.soa.esb.couriers.CourierException: Unable to create Message Consumer
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:406)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:386)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248)
      at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: org.jboss.soa.esb.couriers.CourierServiceBindException: Failed to get JMS Session from pool.
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:164)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:478)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:398)
      ... 7 more
      Caused by: org.jboss.internal.soa.esb.rosetta.pooling.ConnectionException: Could not obtain a JMS connection from the pool after 30s.
      at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:258)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:158)
      ... 9 more
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,078 WARN [org.jboss.soa.esb.listeners.message.MessageAwareListener] Error processing courier, backing off for 32000 milliseconds
      2008-10-06 10:55:45,828 DEBUG [org.jbpm.job.executor.JobExecutorThread] acquiring jobs for execution...
      2008-10-06 10:55:45,828 DEBUG [org.jbpm.configuration.JbpmContextInfo] creating jbpm context with service factories '[tx, message, scheduler, logging, persistence, authentication]'
      2008-10-06 10:55:45,828 DEBUG [org.jbpm.JbpmContext] creating org.jbpm.JbpmContext@10ca790
      2008-10-06 10:55:45,828 DEBUG [org.jbpm.JbpmContext] start user JTA transaction
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.JDBCContext] successfully registered Synchronization
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.impl.SessionImpl] opened session at timestamp: 5010516974972928
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.persistence.db.DbPersistenceService] using current hibernate session SessionImpl(PersistenceContext[entityKeys=[],collectionKeys=[]];ActionQueue[insertions=[] updates=[] deletions=[] collectionCreations=[] collectionRemovals=[] collectionUpdates=[]])
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.job.executor.JobExecutorThread] querying for acquirable job...
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.ConnectionManager] opening JDBC connection
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.SQL] select top ? job0_.ID_ as ID1_26_, job0_.VERSION_ as VERSION3_26_, job0_.DUEDATE_ as DUEDATE4_26_, job0_.PROCESSINSTANCE_ as PROCESSI5_26_, job0_.TOKEN_ as TOKEN6_26_, job0_.TASKINSTANCE_ as TASKINST7_26_, job0_.ISSUSPENDED_ as ISSUSPEN8_26_, job0_.ISEXCLUSIVE_ as ISEXCLUS9_26_, job0_.LOCKOWNER_ as LOCKOWNER10_26_, job0_.LOCKTIME_ as LOCKTIME11_26_, job0_.EXCEPTION_ as EXCEPTION12_26_, job0_.RETRIES_ as RETRIES13_26_, job0_.NAME_ as NAME14_26_, job0_.REPEAT_ as REPEAT15_26_, job0_.TRANSITIONNAME_ as TRANSIT16_26_, job0_.ACTION_ as ACTION17_26_, job0_.GRAPHELEMENTTYPE_ as GRAPHEL18_26_, job0_.GRAPHELEMENT_ as GRAPHEL19_26_, job0_.NODE_ as NODE20_26_, job0_.CLASS_ as CLASS2_26_ from JBPM_JOB job0_ where (job0_.LOCKOWNER_ is null or job0_.LOCKOWNER_=?) and job0_.RETRIES_>0 and job0_.DUEDATE_<=? and job0_.ISSUSPENDED_<>1 order by job0_.DUEDATE_ asc
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to open ResultSet (open ResultSets: 0, globally: 0)
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close ResultSet (open ResultSets: 1, globally: 1)
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.ConnectionManager] aggressively releasing JDBC connection
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.ConnectionManager] releasing JDBC connection [ (open PreparedStatements: 0, globally: 0) (open ResultSets: 0, globally: 0)]
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.engine.StatefulPersistenceContext] initializing non-lazy collections
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.job.executor.JobExecutorThread] no acquirable jobs in job table
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.JbpmContext] closing jbpmContext org.jbpm.JbpmContext@10ca790
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.svc.Services] closing service 'persistence': org.jbpm.persistence.jta.JtaDbPersistenceService@606914
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.JbpmContext] end user JTA transaction
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.JbpmContext] end jta transation with COMMIT
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.svc.Services] closing service 'tx': org.jbpm.tx.TxService@1dd05d6
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.job.executor.JobExecutorThread] obtained locks on following jobs: []
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.configuration.JbpmContextInfo] creating jbpm context with service factories '[tx, message, scheduler, logging, persistence, authentication]'
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.JbpmContext] creating org.jbpm.JbpmContext@1aa610e
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.JbpmContext] start user JTA transaction
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.JDBCContext] successfully registered Synchronization
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.impl.SessionImpl] opened session at timestamp: 5010516974972929
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.persistence.db.DbPersistenceService] using current hibernate session SessionImpl(PersistenceContext[entityKeys=[],collectionKeys=[]];ActionQueue[insertions=[] updates=[] deletions=[] collectionCreations=[] collectionRemovals=[] collectionUpdates=[]])
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.ConnectionManager] opening JDBC connection
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.SQL] select top ? job0_.ID_ as ID1_26_, job0_.VERSION_ as VERSION3_26_, job0_.DUEDATE_ as DUEDATE4_26_, job0_.PROCESSINSTANCE_ as PROCESSI5_26_, job0_.TOKEN_ as TOKEN6_26_, job0_.TASKINSTANCE_ as TASKINST7_26_, job0_.ISSUSPENDED_ as ISSUSPEN8_26_, job0_.ISEXCLUSIVE_ as ISEXCLUS9_26_, job0_.LOCKOWNER_ as LOCKOWNER10_26_, job0_.LOCKTIME_ as LOCKTIME11_26_, job0_.EXCEPTION_ as EXCEPTION12_26_, job0_.RETRIES_ as RETRIES13_26_, job0_.NAME_ as NAME14_26_, job0_.REPEAT_ as REPEAT15_26_, job0_.TRANSITIONNAME_ as TRANSIT16_26_, job0_.ACTION_ as ACTION17_26_, job0_.GRAPHELEMENTTYPE_ as GRAPHEL18_26_, job0_.GRAPHELEMENT_ as GRAPHEL19_26_, job0_.NODE_ as NODE20_26_, job0_.CLASS_ as CLASS2_26_ from JBPM_JOB job0_ where (job0_.LOCKOWNER_ is null or job0_.LOCKOWNER_=?) and job0_.RETRIES_>0 and job0_.ISSUSPENDED_<>1 order by job0_.DUEDATE_ asc
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to open ResultSet (open ResultSets: 0, globally: 0)
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close ResultSet (open ResultSets: 1, globally: 1)
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.ConnectionManager] aggressively releasing JDBC connection
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.jdbc.ConnectionManager] releasing JDBC connection [ (open PreparedStatements: 0, globally: 0) (open ResultSets: 0, globally: 0)]
      2008-10-06 10:55:45,843 DEBUG [org.hibernate.engine.StatefulPersistenceContext] initializing non-lazy collections
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.JbpmContext] closing jbpmContext org.jbpm.JbpmContext@1aa610e
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.svc.Services] closing service 'persistence': org.jbpm.persistence.jta.JtaDbPersistenceService@f1b6e0
      2008-10-06 10:55:45,843 DEBUG [org.jbpm.JbpmContext] end user JTA transaction
      2008-10-06 10:55:45,875 DEBUG [org.jbpm.JbpmContext] end jta transation with COMMIT
      2008-10-06 10:55:45,875 DEBUG [org.jbpm.svc.Services] closing service 'tx': org.jbpm.tx.TxService@49f1cb

        • 1. Re: Error processing courier, backing off for 32000 millisec
          Kevin Conner Master

          I answered this on the JIRA that I rejected.

          "You pool is full, presumably because you have not reconfigured it and have so many services in your esb.

          You need to reconfigure the pool size and/or split up your esb. "

          Have you tried either of those two?

          • 2. Re: Error processing courier, backing off for 32000 millisec
            Raghavan TV Newbie

            Hi Kevin,

            My requirement is to have a SQL-provider that will pick the messages from a table.
            Further the requirement is to fire BPMs based on the Content of the message. Hence am using CBR for routing my messages to appropriate services (which inturn calls the BPM).

            Hence splitting the esb will require me to have multiple sql-providers to the same table.

            This forces me to ask this question:
            Is it possible to have a single esb service with just sql-provider and CBR and have my other services split across multiple esb services ?

            I tried creating a sample appl with the above mentioned approach, but the action failed citing that the target service is not available within the esb scope.
            (Not sure if I've missed something)

            I also tried increasing the pool size
            jbossesb-properties.xml
            -----------------------------
            <?xml version="1.0" encoding="ISO-8859-1"?>
            <esb
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xsi:noNamespaceSchemaLocation="jbossesb-1_0.xsd">





            -------------------------------

            Is this correct?


            Once again thank you for the valuable suggestion and help.

            Thanks,
            -Raghav

            • 3. Re: Error processing courier, backing off for 32000 millisec
              Raghavan TV Newbie

              Oops...the jbossesb-properties was incomplete in my previous post

              <?xml version="1.0" encoding="ISO-8859-1"?>
              <esb
               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
               xsi:noNamespaceSchemaLocation="jbossesb-1_0.xsd">
               <properties name="transports" depends="core">
               <property name="org.jboss.soa.esb.jms.connectionPool" value="1000"/>
               </properties>
              
              </esb>


              Is this the right way to reconfigure the connection pool ?
              Thanks,
              -Raghav

              • 4. Re: Error processing courier, backing off for 32000 millisec
                Kevin Conner Master

                 

                "tvraghavan" wrote:
                Is it possible to have a single esb service with just sql-provider and CBR and have my other services split across multiple esb services ?


                Yes

                "tvraghavan" wrote:
                I tried creating a sample appl with the above mentioned approach, but the action failed citing that the target service is not available within the esb scope.


                I don't remember an error such as that in the codebase, could you post more details so that I can find out what is happening?

                "tvraghavan" wrote:
                Is this correct?


                You need to add that line to the file in jbossesb.sar, it is a global setting.


                • 5. Re: Error processing courier, backing off for 32000 millisec
                  Raghavan TV Newbie

                  Hi Kev,

                  I increased the connectionPool settings under jbossesb.sar [jbossesb-properties.xml] and I no longer see the Courier exception. Am running some test cases and shall keep you updated.

                  Thanks,
                  -Raghav