Question for the ResourceException: Interrupted while requesting permit! Waited 0 ms

[niefeng]

Hi all,

I am observing the error "ResourceException: Interrupted while requesting permit! Waited 0 ms" in the peer node in the cluster when main node (the first node started in the cluster) is crashed unexpectedly.

The detail stack trace as follow

org.jboss.util.NestedSQLException: Interrupted while requesting permit! Waited 0 ms; - nested throwable: (javax.resource.ResourceException: Interrupted while requesting permit! Waited 0 ms)
    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95)

Caused by: javax.resource.ResourceException: Interrupted while requesting permit! Waited 0 ms
    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:312)
    at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:613)
    at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:347)
    at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:330)
    at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:402)
    at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:849)
    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
    ... 154 more

I am using JBOSS 4.2.3 GA, and the cluster is consisting of 2 nodes. The DB i am using is postgres 8.4.4 and i am using a Fedora 8 box.

I have read the thread (http://community.jboss.org/message/150841) and it mentioned the error is related to the transaction time out, and it suggested that to include the option <blocking-timeout-millis> in the ds.xml. I still observing such error even after such option is enable in my db ds file.

<!--DS -->
  <local-tx-datasource>
    <jndi-name>dbdatasource</jndi-name>
    <connection-url>jdbc:postgresql://localhost:35432/myPgsql</connection-url>
    <driver-class>org.postgresql.Driver</driver-class>
    <user-name>postgres</user-name>
    <password>XXXXX</password>
    <min-pool-size>10</min-pool-size>
    <max-pool-size>40</max-pool-size>
    <idle-timeout-minutes>15</idle-timeout-minutes>
    <blocking-timeout-millis>400000</blocking-timeout-millis>
        <!-- sql to call when connection is created.  Can be anything, select 1 is valid for PostgreSQL
        <new-connection-sql>select 1</new-connection-sql>
        -->

        <!-- sql to call on an existing pooled connection when it is obtained from pool.  Can be anything, select 1 is valid for PostgreSQL
        <check-valid-connection-sql>select 1</check-valid-connection-sql>
        -->

      <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
      <metadata>
         <type-mapping>PostgreSQL 7.2</type-mapping>
      </metadata>
  </local-tx-datasource>

Could it be my configuration is wrong? or what are the additional configuration i need to specify?

Regards

Niefeng

[vickyk]

I am observing the error "ResourceException: Interrupted while requesting permit! Waited 0 ms" in the peer node in the cluster when main node (the first node started in the cluster) is crashed unexpectedly.

It is a crash related scenario and there could be possiblity that the invoking thread is trying to call the connection is being stopped, why are you worried about it since this is happening while there is a crash. You must me worried about the crash itself.

I am using JBOSS 4.2.3 GA, and the cluster is consisting of 2 nodes. The DB i am using is postgres 8.4.4 and i am using a Fedora 8 box.

I have read the thread (http://community.jboss.org/message/150841) and it mentioned the error is related to the transaction time out, and it suggested that to include the option <blocking-timeout-millis> in the ds.xml. I still observing such error even after such option is enable in my db ds file.

You are using Jboss4.2* series which does not contain the older in memory TM, the trasaction timeout would result in thread interruption in that case. So the transaction timeout should not be the cause for this case.