Bugs item #593625, was opened at 2002-08-11 10:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=593625&group_id=22866
Category: JBossTX Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Frank Langelage (lafr) Assigned to: David Jencks (d_jencks) Summary: informix-XA: Transaction-Handling Initial Comment: My application works well with LocalTxDS but not with XATxDS. When using the informix-xa-service.xml file, the tables get created but the DB-Session stays in transaction. BTW, I thougt DDL-Statements should not run in transaction ? Creation of Entities is nearly impossible. When using informix-service.xml all works fine. An extract from server.log is attached. (JBoss-3.0.2RC1, JDK 1.3.1, Reliant-Unix 5.45) ---------------------------------------------------------------------- >Comment By: David Jencks (d_jencks) Date: 2002-08-26 23:14 Message: Logged In: YES user_id=60525 It's a typo. Igor, I don't have any XADataSources to try this out on, and you should have cvs write access now, correct? Can you fix the xsl and at least one *-xa-ds.xml file in cvs, I will transfer whatever needs changing to the other *-xa-ds.xml files. And after it deploys, there's still the question of whether any of it works;-) Thanks david ---------------------------------------------------------------------- Comment By: Igor Fedorenko (igorfie) Date: 2002-08-26 22:59 Message: Logged In: YES user_id=232950 fehler.txt is easy -- there is another name mismatch, this time between xslt script and java code, in java attribute is called XaDataSourceClass and in xslt XADataSourceClass. David, is it a typo or I am missing something? In mean time change connector\src\main\org\jboss\resource\adapter\jdbc\xa\XAMan agedConnectionFactory.java, rename get/setXaDataSourceClass to get/setXADataSourceClass and rebuild. trace.txt is a mistery for me -- where did jboss take xa connection if it could not set driver classname to start with? ---------------------------------------------------------------------- Comment By: Frank Langelage (lafr) Date: 2002-08-26 22:39 Message: Logged In: YES user_id=300021 Ok, the last hint was useful. But now I get a WARN and a ERROR. See attached extract from server.log. XADataSourceClass is not set from informix-xa-ds.xml. ---------------------------------------------------------------------- Comment By: Igor Fedorenko (igorfie) Date: 2002-08-26 22:16 Message: Logged In: YES user_id=232950 There is a mismatch between example *-xa-ds.xml and xslt template used to process them. In "informix-xa-ds.xml" try to replace "xa-tx-datasource" with "xa-datasource". ---------------------------------------------------------------------- Comment By: Frank Langelage (lafr) Date: 2002-08-26 21:45 Message: Logged In: YES user_id=300021 I'm sorry, but I did not succeed in setting up informixXA in JBoss-4.0.0alpha. I can take informix-ds.xml, modify the properties (host, port, ...) an put in the deploy dir. This works fine. If I do the same with informix-xa-ds.xml, it does not deploy completely. I don't see message "...bound to java:/InformixXaDS", so I also cannot use it. What am I missing here ? ---------------------------------------------------------------------- Comment By: David Jencks (d_jencks) Date: 2002-08-24 01:15 Message: Logged In: YES user_id=60525 Can you guys see whether there is the same problem with the xa wrapper in jboss 4 (cvs head)? It (AFAIK) correctly implements jca semantics of autocommitting work done outside a jta (managed) transaction. If this does not fix the problems please provide details of what does happen. Note the wrapper is untested since I don't have an xa driver to play with. I would like to make sure the wrapper works and back port it to 3.2. ---------------------------------------------------------------------- Comment By: Larry Sanderson (lsanders) Date: 2002-08-12 17:05 Message: Logged In: YES user_id=379453 We encountered XAER_OUTSIDE exceptions when we tried to intermingle Local and Global transactions. The problem turned out to be an Informix bug: Local transactions are not explicitly committed or rolledback when the connection is closed. This leaves a pooled XA connection still in the scope of a local transaction. The next use of that XA connection that attempts to enlist it within a global transaction causes this error. We wrote several wrappers around the Informix drivers that fix this and several other Informix XA bugs. (We have also filed each of these bugs with Informix/IBM). The fix for this particular bug involved intercepting calls to close() and making sure that any local transactions have committed successfully. I have attached the wrapped datasource if you are interested. Just compile it and change the "XADataSourceClass" config property in your Informix service.xml. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=593625&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
