Tuesday, 17 July 2007

XA Transaction Errors On Websphere Talking To 10g Database Through JDBC Driver 10g

When attempting to run XA JDBC program on Websphere the following runtime error can occur:

13545 The XA Error is : -7
13546 The XA Error message is : Resource manager is unavailable.
13547 The Oracle Error code is : 17002
13548 The Oracle Error message is: Internal XA Error
13549 The cause is : null.
13550 [5/18/07 10:29:24:538 MST] 00000084 WSRdbXaResour E DSRA0302E: XAException occurred.
Error code is: XAER_RMFAIL (-7). Exception is:
13551 [5/18/07 10:29:24:538 MST] 00000084 WSRdbXaResour 3 XAER_RMFAIL connection error occurred
13552 [5/18/07 10:29:24:538 MST] 00000084 WSRdbXaResour 3 process connection error occurred
event for XAResource com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl@43e4a31d
13553 [5/18/07 10:29:24:538 MST] 00000084 WSJdbcConnect > close Entry
13554 com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@5f13637b
13555 [5/18/07 10:29:24:538 MST] 00000084 WSJdbcConnect 1 state --> CLOSED

It turns out that from the stack trace/error a 17002 error means that the connection pool is handing out stale connections which have been closed. This is documented on IBM web site with various different ways of trouble shooting stale connection errors from WebSphere. See the link below.

http://www-1.ibm.com/support/docview.wss?uid=swg21247168#SCETroubleshooting
Troubleshooting stale connection problems

No comments: