-
1. Re: Jboss JMS error - help needed
anilit99 Aug 10, 2008 6:18 AM (in response to ravichittari)can you post some configurations - i mean what is the hsql-db.xml looking like ?
-
2. Re: Jboss JMS error - help needed
ravichittari Aug 11, 2008 6:32 PM (in response to ravichittari)The standard stuff that comes with jboss isntall. Below are two relevant params for hsqldb-ds.xml
<!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
<min-pool-size>5</min-pool-size>
<!-- The maximum connections in a pool/sub-pool -->
<max-pool-size>20</max-pool-size>
For jms-ds.xml, again standard stuff
<tx-connection-factory>
<jndi-name>JmsXA</jndi-name>
<xa-transaction/>
<rar-name>jms-ra.rar</rar-name>
<connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
<config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
<config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
<max-pool-size>20</max-pool-size>
<security-domain-and-application>JmsXARealm</security-domain-and-application>
</tx-connection-factory>
My suspicion is that the max pool size in tx-connection-factory defined in jms-ds.xml is low for the txns I am handling. Hence getting this error.
But, want to see if anyone else has run into this issue.
Would be nice if Jboss wiki has some good pointers to this topic. -
3. Re: Jboss JMS error - help needed
skajotde Aug 19, 2008 6:39 AM (in response to ravichittari)<max-pool-size>20</max-pool-size>
It is defaults values, You should to suit its to own needs / average load.
And try check in JMX listConnectionInUse() in CachedConnectionManager or something similiar. Mayby you are not release some connections.