JBossDeveloper

I have got the same problem.

[JmsConnectionPool] The connection pool was exhausted. Waiting 1 second before trying again..

I tried to use jms-jca-provider as suggested:

<providers>
 <jms-jca-provider name="JBossMQ"
 connection-factory="ConnectionFactory"
 jndi-URL="jnp://127.0.0.1:1199"
 jndi-context-factory="org.jnp.interfaces.NamingContextFactory"
 jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces">
...

But I still get the error. I am using 4.2.1GA.

 

"domkun" wrote:
But I still get the error. I am using 4.2.1GA.

The <jms-jca-provider> handles the incoming messages but the pool still applies to the outgoing ones. The connections should be obtained from the pool and then released.

Does the error message continue once you get it or does it begin and then stop?

Can you please describe your ESB application, it may shed some light on the issue.

The error message apears once and then every second until a jms connection is released. (I think this is the right behaviour, and good for all situations.) But I think my problem is that I need more connections in the pool.

So here is my scenario:
The problem occured during stress testing my application using JMeter. I simulated 20 concurrent users, which are calling 2 webservices, exposed using the SOAPProcessor.
Each of the webservices call a esb service via the ServiceInvoker.

I just fixed the problem with changing the jbossesb-properties.xml in jbossesb-server-4.2.1GA\server\default\deploy\jbossesb.sar to

...
<properties name="transports" depends="core">
 <property name="org.jboss.soa.esb.mail.smtp.host" value="localhost"/>
 <property name="org.jboss.soa.esb.mail.smtp.user" value="jbossesb"/>
 <property name="org.jboss.soa.esb.mail.smtp.password" value=""/>
 <property name="org.jboss.soa.esb.mail.smtp.port" value="25"/>
 <property name="org.jboss.soa.esb.mail.smtp.auth" value="true"/>
 <property name="org.jboss.soa.esb.ftp.localdir" value="/tmp"/>
 <property name="org.jboss.soa.esb.ftp.remotedir" value="/tmp"/>
 <property name="org.jboss.soa.esb.jms.connectionPool" value="200"/>
 <property name="org.jboss.soa.esb.jms.sessionSleep" value="30"/>
 </properties>
...

But I don't know whether this is a good or bad idea :)

I also tried to set the "org.jboss.soa.esb.jms.connectionPool" in the jbossesb-properties.xml of my esb-artifact, but it seemed that it had no effect.

Greetings,
Dominik

Hiya Dominik.

"domkun" wrote:
I just fixed the problem with changing the jbossesb-properties.xml in jbossesb-server-4.2.1GA\server\default\deploy\jbossesb.sar to

...
<properties name="transports" depends="core">
 <property name="org.jboss.soa.esb.mail.smtp.host" value="localhost"/>
 <property name="org.jboss.soa.esb.mail.smtp.user" value="jbossesb"/>
 <property name="org.jboss.soa.esb.mail.smtp.password" value=""/>
 <property name="org.jboss.soa.esb.mail.smtp.port" value="25"/>
 <property name="org.jboss.soa.esb.mail.smtp.auth" value="true"/>
 <property name="org.jboss.soa.esb.ftp.localdir" value="/tmp"/>
 <property name="org.jboss.soa.esb.ftp.remotedir" value="/tmp"/>
 <property name="org.jboss.soa.esb.jms.connectionPool" value="200"/>
 <property name="org.jboss.soa.esb.jms.sessionSleep" value="30"/>
 </properties>
...

But I don't know whether this is a good or bad idea :)

I need to take back my previous statement, looks like we did address the hard coded limit and it was some time ago. Mark fixed this back in July for the 4.2MR3 release. My bad.

http://jira.jboss.com/jira/browse/JBESB-579

"domkun" wrote:
I also tried to set the "org.jboss.soa.esb.jms.connectionPool" in the jbossesb-properties.xml of my esb-artifact, but it seemed that it had no effect.

There is no way to do this through your ESB artifact at present, although it is a good suggestion.

Thanks,

Kev