Bugs item #696663, was opened at 2003-03-03 11:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=696663&group_id=22866
Category: JBossCX Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Igor Fedorenko (igorfie) Assigned to: Nobody/Anonymous (nobody) Summary: Can't set SERIALIZABLE transaction isolation with Oracle XA Initial Comment: This is not a bug report per se, but I could not find any better place for such information. ;-) Problem as observed by JBoss users: JBoss 3.2 and 4.0 do not allow setting SERIALIZABLE transaction isolation level for Oracle XA datasources. Root cause of this is incompatible Oracle JDBC driver (surprise, surprise). There seems to be no way to set SERIALIZABLE tx isolation level with Oracle 8i JDBC drivers. To start SERIALIZABLE tx using Oracle JDBC driver v9.2.0.1 one need to: XADataSource ds = ...; XAConnection mc = ds.getXAConnection(); XAResource xares = mc.getXAResource(); xares.start(xid, XAResource.TMNOFLAGS | oracle.jdbc.xa.OracleXAResource.ORATMSERIALIZABL E); Note not-standard parameter passed to XAResource.start and that Connection.setTransactionIsolation(int) should not be called with Oracle XA drivers. I do not have any immediate plans to implement this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=696663&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
