We are running Jboss4.0.2. We use it for queuing as well as maintaing 
connection pool to the database. 


Occasionally we see (lots of when it happens) below error in the logs.

anonymous wrote : 
  | 19:34:32,947 WARN  [TransactionImpl] Transaction 
TransactionImpl:XidImpl[FormatId=257, GlobalId=cmp2app01/47048438, BranchQual=, 
localId=47048438] timed out.
  | status=STATUS_ACTIVE
  | 19:34:32,951 WARN  [TransactionImpl] Transaction 
TransactionImpl:XidImpl[FormatId=257, GlobalId=cmp2app01/47048446, BranchQual=, 
localId=47048446] timed out.
  | status=STATUS_ACTIVE
  | 19:34:32,951 WARN  [TransactionImpl] Transaction 
TransactionImpl:XidImpl[FormatId=257, GlobalId=cmp2app01/47048449, BranchQual=, 
localId=47048449] timed out.
  | status=STATUS_
  | 
  | 


What does above mean and what can be the impact ?


That is usually followed by the below error.

anonymous wrote : 
  | 
  | 19:35:28,023 INFO  [TxConnectionManager] Could not enlist in transaction on 
entering meta-aware object!
  | javax.transaction.SystemException: Could not get XAResource from 
ManagedConnection!javax.transaction.RollbackException: Already marked for 
rollback Transactio
  | nImpl:XidImpl[FormatId=257, GlobalId=cmp2app01/47048500, BranchQual=, 
localId=47048500]
  |         at 
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.enlist(TxConnectionManager.java:441)
  |         at 
org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnectionManager.java:322)
  |         at 
org.jboss.resource.connectionmanager.BaseConnectionManager2.reconnectManagedConnection(BaseConnectionManager2.java:583)
  |         at 
org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:450)
  |         at 
org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:874)
  |         at 
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:103)
  |         at 
com.mobilgw.sam.common.cp.celcom.WFCelcomComponentFactory.(WFCelcomComponentFactory.java:120)
  |         at 
com.mobilgw.sam.plugin.celcom.CheckAllowBlacklist.checkSubscriberForAllowBlackList(CheckAllowBlacklist.java:159)
  |         at 
com.mobilgw.sam.plugin.celcom.CheckAllowBlacklist.execute(CheckAllowBlacklist.java:80)
  |         at 
com.mobilgw.sam.executionengine.adapter.JavaAdapterHandler.execute(JavaAdapterHandler.java:84)
  |         at 
com.mobilgw.sam.executionengine.ExecutionEngine.execute(ExecutionEngine.java:575)
  |         at 
com.mobilgw.sam.executionengine.ExecutionEngine.execute(ExecutionEngine.java:460)
  |         at 
com.mobilgw.sam.executionengine.ExecutionEngine.execute(ExecutionEngine.java:586)
  |         at 
com.mobilgw.sam.executionengine.ExecutionEngine.execute(ExecutionEngine.java:460)
  |         at 
com.mobilgw.sam.executionengine.ExecutionEngine.execute(ExecutionEngine.java:455)
  |         at 
com.mobilgw.sam.executionengine.ExecutionEngine.execute(ExecutionEngine.java:361)
  |         at 
com.mobilgw.sam.executionengine.queue.SmsService.run(SmsService.java:575)
  |         at java.lang.Thread.run(Thread.java:534)
  | 19:35:28,026 WARN  [TxConnectionManager] Unchecked throwable in 
managedConnectionDisconnected()
  | org.jboss.resource.JBossResourceException: Error in delist!; - nested 
throwable: (java.lang.IllegalArgumentException: xaRes not enlisted 
org.jboss.resource.co
  | [EMAIL PROTECTED])
  |         at 
org.jboss.resource.connectionmanager.BaseConnectionManager2.rethrowAsResourceException(BaseConnectionManager2.java:101)
  |         at 
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.delist(TxConnectionManager.java:488)
  |         at 
org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionDisconnected(TxConnectionManager.java:337)
  |         at 
org.jboss.resource.connectionmanager.BaseConnectionManager2.disconnectManagedConnection(BaseConnectionManager2.java:601)
  |         at 
org.jboss.resource.connectionmanager.BaseConnectionManager2.reconnectManagedConnection(BaseConnectionManager2.java:587)
  |         at 
org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:450)
  |         at 
org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:874)
  |         at 
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:103)
  |         at 
com.mobilgw.sam.common.cp.celcom.WFCelcomComponentFactory.(WFCelcomComponentFactory.java:120)
  |         at 
com.mobilgw.sam.plugin.celcom.CheckAllowBlacklist.checkSubscriberForAllowBlackList(CheckAllowBlacklist.java:159)
  |         at 
com.mobilgw.sam.plugin.celcom.CheckAllowBlacklist.execute(CheckAllowBlacklist.java:80)
  |         at 
com.mobilgw.sam.executionengine.adapter.JavaAdapterHandler.execute(JavaAdapterHandler.java:84)
  |         at 
com.mobilgw.sam.executionengine.ExecutionEngine.execute(ExecutionEngine.java:575)
  |         at 
com.mobilgw.sam.executionengine.ExecutionEngine.execute(ExecutionEngine.java:460)
  |         at 
com.mobilgw.sam.executionengine.ExecutionEngine.execute(ExecutionEngine.java:586)
  |         at 
com.mobilgw.sam.executionengine.ExecutionEngine.execute(ExecutionEngine.java:460)
  |         at 
com.mobilgw.sam.executionengine.ExecutionEngine.execute(ExecutionEngine.java:455)
  |         at 
com.mobilgw.sam.executionengine.ExecutionEngine.execute(ExecutionEngine.java:361)
  |         at 
com.mobilgw.sam.executionengine.queue.SmsService.run(SmsService.java:575)
  |         at java.lang.Thread.run(Thread.java:534)
  | Caused by: java.lang.IllegalArgumentException: xaRes not enlisted [EMAIL 
PROTECTED]
  |         at 
org.jboss.tm.TransactionImpl.delistResource(TransactionImpl.java:428)
  |         at 
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.delist(TxConnectionManager.java:476)
  |         ... 18 more
  | 
  | 


After this we usually find that there are no more connections left with the 
database. What could be the cause and where should I be searching for solutions?


Also is there any relation between connection pool for hypersonic DB and oracle 
DB? I have seen that usually DB connection problem occurs whenever we hit a 
problem with hypersonic DB in production. When the problem strikes we usually 
see that the sum of available and used connections doesn?t even sums up to the 
max configured in oracle-ds.xml

Any idea/suggestion would be really helpful.

Thanking in advance.
Suds
        

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066533#4066533

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066533
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to