5 Replies Latest reply on Oct 14, 2008 2:31 AM by hauch

    Problems with esb module with many services

    hauch

      I run into the following exception when I try to invoke a service in an esb module with >20 services.

      12:46:05,888 WARN [ServiceController] Problem starting service jboss.esb:deployment=large_service-0.33.06-SNAPSHOT.esb
      org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected connection exception from prepareMessageReceiver
       at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doInitialise(JmsGatewayListener.java:112)
       at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:133)
       at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:150)
       at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:69)
       at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:83)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
      ...
      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.soa.esb.listeners.gateway.JmsGatewayListener.prepareMessageReceiver(JmsGatewayListener.java:408)
       at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doInitialise(JmsGatewayListener.java:109)
      


      I have reproduced the error in a setup with 25 identical services on the form
       <service category="Smile" name="Service1" description="beskrivelse">
       <listeners>
       <jms-listener name="JMS-Channel" is-gateway="false" busidref="Service1Channel" maxThreads="1"/>
       <jms-listener name="JMS-Channel" is-gateway="true" busidref="Service1GW" maxThreads="1"/>
       </listeners>
       <actions>
       <action name="action_Service1" class="org.jboss.soa.esb.actions.SystemPrintln">
       <property name="printfull" value="true"/>
       <property name="message" value="****** SERVICE Service1} ***********"/>
       </action>
       </actions>
       </service>
      


      These are invoked via a file gateway.

      The error occurs when I have >20 of these, but everything work fine if I have less.
      I have reproduced the error on a jbossesb-server-4.4.GA with no modifications.

      Is this a bug or a configuration issue?