3 Replies Latest reply on Aug 19, 2008 6:39 AM by Kamil Demecki

    Jboss JMS error - help needed

    Ravikiran Chittari Newbie

      I am getting the following error in my server logs.

      Does this mean (a) My defaultDS connection that points to hsqldb is max-ed out on connection pool? Hsqldb is used for jms messages.

      OR it is jms-ds.xml that manages jmsXA ds?

      ERROR [org.jboss.resource.adapter.jms.JmsSessionFactoryImpl] could not create session
      javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] )
      at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:301)
      at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
      at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
      at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
      at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
      at org.

      Thanks for your help..

        • 1. Re: Jboss JMS error - help needed
          Anil Reddy Newbie

          can you post some configurations - i mean what is the hsql-db.xml looking like ?

          • 2. Re: Jboss JMS error - help needed
            Ravikiran Chittari Newbie

            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 -->

            <!-- The maximum connections in a pool/sub-pool -->

            For jms-ds.xml, again standard stuff
            <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>

            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
              Kamil Demecki Novice



              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.