-
1. Re: OracleXARecovery transaction recovery module can not detect when JDBC connection is broken
mmusgrov Jun 3, 2010 7:59 AM (in response to dengyong)Does the connection owner (the on in the XA datasource config file) have permission to up access the ORACLE tables (dba_pending_transactions exct). You can find the relevent permissions you will need in the transactions administration guide.
-
2. Re: OracleXARecovery transaction recovery module can not detect when JDBC connection is broken
dengyong Jun 4, 2010 12:28 AM (in response to mmusgrov)Hi Michael:
Thanks for your answers. But you did not get my questions.
That error is popping up only after the network cable is unplugged.
I am expecting the oracle recovery module can detect the cached connection is bad and auto recovery to use an new one.
BTW, my user has all the needed permission here:
GRANT SELECT ON SYS.dba_pending_transactions TO <user>; GRANT SELECT ON SYS.pending_trans$ TO <user>; GRANT SELECT ON SYS.dba_2pc_pending TO <user>; GRANT EXECUTE ON SYS.dbms_system TO <user>;
-
3. Re: OracleXARecovery transaction recovery module can not detect when JDBC connection is broken
jhalliday Jun 4, 2010 4:31 AM (in response to dengyong)> I am expecting the oracle recovery module can detect the cached connection is bad and auto recovery to use an new one.
It relies on the connection being reported as bad - that's what the ConnectionEventListener is for. Looks like the Oracle driver doesn't do that though. Just subclass the existing implementation and add explicit connection validation if you want that feature.
-
4. Re: OracleXARecovery transaction recovery module can not detect when JDBC connection is broken
dengyong Jun 4, 2010 1:10 PM (in response to jhalliday)Jonathan:
Did you intend to fix this in next release?
Thanks for your reply in advance.