[ http://jira.jboss.com/jira/browse/JBAS-4071?page=all ] Mauricio Seeberger updated JBAS-4071: ------------------------------------- Description: When you have more than one non-XA resource participating in a multibranch transaction, then you have a problem in your code and sooner or later it will result in inconsistent data. But JBoss (TxConnectionManager) just logs just once a general message: Prepare called on a local tx. Use of local transactions on a jta transaction with more than one branch may result in inconsistent data in some cases of failure. We need more information about the resource and a stack trace for identifying the malicious code. was: When you have more than one non-XA resource participating in a multibranch transaction, then you have a problem in your code and sooner or later it will result in inconsistent data. But JBoss (TxConnectionManager) just logs just once a generic message: Prepare called on a local tx. Use of local transactions on a jta transaction with more than one branch may result in inconsistent data in some cases of failure. We need more information about the resource and a stack trace for identifying the malicious code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-4071?page=com.atlassian.jira.plug... ] Vicky Kak updated JBAS-4071: ---------------------------- Component/s: JCA service (was: Other) (was: Transaction Manager (JBossTM)) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-4071?page=com.atlassian.jira.plug... ] Adrian Brock closed JBAS-4071. ------------------------------ Resolution: Out of Date This is no longer relevant. The multiple local resources checking is now in the transaction manager (and not allowed by default since 4.2.x) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira