Bugs item #731343, was opened at 2003-05-02 13:42 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=731343&group_id=22866
Category: JBossCX Group: v3.2 Status: Open Resolution: Accepted Priority: 5 Submitted By: Mark Little (marklittle) >Assigned to: Adrian Brock (ejort) Summary: Transaction equality test bug Initial Comment: In JBoss 3.2 RC1, the org.jboss.resource.connectionmanager.TxConnectionMa nager class checks for transaction equality using the = operator. In general you can't guarantee that this will work and particularly for distributed transactions. That's why the JTA specification has a specific section in 3.3 on transaction equality: "The transaction manager must implement the Transaction object �s equals method to allow comparison between the target object and another Transaction object." I think this may happen in more than just this class as well. Mark. ---------------------------------------------------------------------- >Comment By: Adrian Brock (ejort) Date: 2003-06-26 16:41 Message: Logged In: YES user_id=9459 This has been fixed in TxConnectionManager ---------------------------------------------------------------------- Comment By: Scott M Stark (starksm) Date: 2003-05-06 12:35 Message: Logged In: YES user_id=175228 Its ii and obviously this needs to be fixed. Please submit a patch. ---------------------------------------------------------------------- Comment By: Mark Little (marklittle) Date: 2003-05-06 09:03 Message: Logged In: YES user_id=754951 It may work for JBoss tm, but I was under the impression that JBoss was supposed to be pluggable in that other services could be switched for those that ship? Now there are obviously two approaches to doing an app. server: (i) the closed, proprietary approach where it just isn't possible/feasible to replace services such as transactions, messaging etc. (The IBM/BEA route). or (ii) the open approach, where services can be swapped because all interactions with them occur across open boundaries. (The HP route). Both approaches are valid, but I was under the impression that JBoss had taken approach (ii). If that's not the case then can you let me know? If it is, then this obviously needs fixing. Thanks, Mark. ---------------------------------------------------------------------- Comment By: David Jencks (d_jencks) Date: 2003-05-02 17:05 Message: Logged In: YES user_id=60525 You're right, but this is unlikely to cause problems with the jboss tm. Except during recover (in jboss 4) there is only one instance of a particular transaction in a vm. This is also true for imported transaction in jb4. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=731343&group_id=22866 ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
