1 Reply Latest reply on Aug 18, 2016 11:10 AM by jimmy001

    Unable to get managed connection for java:jboss/datasources/TASKORMDS

    mariaprabudass
    mariaprabudass Aug 17, 2016 2:39 PM

      Hi,

      We encounter an issue in production when we upgraded JBPM from 5.2.0.Final version to 5.4.0.Final version. Provided below the details and seeking your help to sort out this issue.

       

      In-order to use the local human task feature, we have upgrade the JBPM version from 5.2 to 5.4. In development, we didn't observe any issue whereas in production the exception has been raised for the customer whose load is heavy but the same didn't occur for the customer who has light or average load.

       

      Posted below the exception message & jBoss configuration for references.

      jBoss Server Log:-

      Caused by: java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/TASKORMDS

        at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:137)

        at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:92) [hibernate-core-3.6.9.Final.jar:]

        at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446) [hibernate-core-3.6.9.Final.jar:]

        ... 86 more

      Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/TASKORMDS

        at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:394)

        at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:367)

        at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:467)

        at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:129)

        ... 88 more

      Caused by: javax.resource.ResourceException: IJ000655: No managed connections available within configured blocking timeout (5000 [ms])

        at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:355)

        at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:392)

        at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:357)

        at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:351)

       

      jBoss Datasource Configuration:-

          <datasource jndi-name="java:jboss/datasources/TASKORMDS" pool-name="MySqlDS" enabled="true" jta="true" use-java-context="true" use-ccm="true">

                          <connection-url>

                              jdbc:mysql://livedb.co.in:3306/task_details

                          </connection-url>

                          <driver>

                              com.mysql

                          </driver>

                          <transaction-isolation>

                              TRANSACTION_READ_COMMITTED

                          </transaction-isolation>

                          <pool>

                              <min-pool-size>

                                  10

                              </min-pool-size>

                              <max-pool-size>

                                  100

                              </max-pool-size>

                              <prefill>

                                  false

                              </prefill>

                              <use-strict-min>

                                  false

                              </use-strict-min>

                              <flush-strategy>

                                  FailingConnectionOnly

                              </flush-strategy>

                          </pool>

                          <security>

                              <user-name>

                                  xxxxx

                            </user-name>

                              <password>

                                  xxxxx

                              </password>

                          </security>

                          <validation>

                              <check-valid-connection-sql>

                                  select 1

                              </check-valid-connection-sql>

                              <validate-on-match>

                                  true

                              </validate-on-match>

                              <background-validation>

                                  false

                              </background-validation>

                              <use-fast-fail>

                                  false

                              </use-fast-fail>

                          </validation>

                          <timeout>

                              <blocking-timeout-millis>

                                  5000

                              </blocking-timeout-millis>

                              <idle-timeout-minutes>

                                  60000

                              </idle-timeout-minutes>5.4.0.Final

                              <set-tx-query-timeout/>

                          </timeout>

                          <statement>

                              <prepared-statement-cache-size>

                                  0

                              </prepared-statement-cache-size>

                          </statement>

                      </datasource>

       

      Note:

      Customers who has heavy loads were working fine before the migration ie 5.2 version in production.

       

      Regards,

      Maria