0 Replies Latest reply: Oct 1, 2009 9:36 AM by 807574 RSS

    Java CAPS Resource Issues (Glassfish EJB Container and JMS settings)

    807574
      Hi,

      We are currently running performance tests on our application. We are running Java CAPS 6 Update 1.

      Once we start running a big load through the application, we regularly see the following error:
      [#|2009-10-01T10:17:00.479-0400|WARNING|sun-appserver9.1|com.stc.jmsjca.core.Activation|_ThreadID=45;_ThreadName=imqConsumerReader-14-653906023769841920-26;_RequestID=e5e3cc07-86a2-4068-a80d-0055bf207e58;|JMSJCA-E014: [cc-QueueReceiver(lookup://jms/queue/COMMON_CTRLM_EDB) @ [mq://camtscpce756.mailposte.ca:37676]]: the following exception was encountered while initiating or during message delivery: [javax.jms.JMSException: JMSJCA-E001: Unexpected failure to obtain an empty work container to process JMS messages. The exception was: javax.resource.ResourceException: JMSJCA-E120: Failed to create endpoint... giving up. Last exception: javax.resource.spi.UnavailableException]; attempts will be made to (re-)start message delivery (auto reconnect mode).
      javax.jms.JMSException: JMSJCA-E001: Unexpected failure to obtain an empty work container to process JMS messages. The exception was: javax.resource.ResourceException: JMSJCA-E120: Failed to create endpoint... giving up. Last exception: javax.resource.spi.UnavailableException
      at com.stc.jmsjca.util.Exc.jmsExc(Exc.java:100)
      at com.stc.jmsjca.core.CCDelivery.getServerSession(CCDelivery.java:181)
      at com.sun.messaging.jmq.jmsclient.ConnectionConsumerImpl.onMessage(ConnectionConsumerImpl.java:176)
      at com.sun.messaging.jmq.jmsclient.ConnectionConsumerReader.deliver(ConnectionConsumerReader.java:72)
      at com.sun.messaging.jmq.jmsclient.ConsumerReader.run(ConsumerReader.java:185)
      at java.lang.Thread.run(Thread.java:619)
      Caused by: javax.resource.ResourceException: JMSJCA-E120: Failed to create endpoint... giving up. Last exception: javax.resource.spi.UnavailableException
      at com.stc.jmsjca.util.Exc.rsrcExc(Exc.java:68)
      at com.stc.jmsjca.core.Delivery.createMessageEndpoint(Delivery.java:571)
      at com.stc.jmsjca.core.CCDelivery.growPoolIfNecessary(CCDelivery.java:272)
      at com.stc.jmsjca.core.CCDelivery.getEmptyWorkContainer(CCDelivery.java:305)
      at com.stc.jmsjca.core.CCDelivery.getServerSession(CCDelivery.java:177)
      ... 4 more
      Caused by: javax.resource.spi.UnavailableException
      at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.createEndpoint(ConnectorMessageBeanClient.java:404)
      at com.stc.jmsjca.core.Delivery.createMessageEndpoint(Delivery.java:566)
      ... 7 more
      Caused by: com.sun.ejb.ResourcesExceededException: Message Bean Resources exceeded for message bean edb-application-1.0:com.cpc.caps.common.handler.COMMON_CRTLM_EDBServiceHandler
      at com.sun.ejb.containers.MessageBeanContainer.createMessageBeanListener(MessageBeanContainer.java:619)
      at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.createEndpoint(ConnectorMessageBeanClient.java:367)
      ... 8 more
      |#]


      The error states that the Message Bean Resources are exceeded. Would this be fixed by updating the EJB Container Pool size? Or is it an issue withe JMS pool settings?

      We are running stateless beans at this stage.

      Thanks!