[jbossts-issues] [JBoss JIRA] Closed: (JBTM-69) Work around for JacORB persistent POA bug
Mark Little (JIRA)
jira-events at lists.jboss.org
Tue Oct 19 05:01:54 EDT 2010
[ https://jira.jboss.org/browse/JBTM-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Little closed JBTM-69.
Resolution: Out of Date
> Work around for JacORB persistent POA bug
> Key: JBTM-69
> URL: https://jira.jboss.org/browse/JBTM-69
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 4.2, 4.2.1
> Reporter: Mark Little
> Assignee: Mark Little
> Priority: Minor
> In order to perform recovery in the JTS, we use a persistent IOR reference for the transaction coordinator. Unfortunately there is a bug in JacORB (http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=473) which affects our implementation in a distributed setting. All persistent POAs are named in JacORB using:
> # the implementation name, should be set to a different
> # name in the code of persistent servers
> The bug is that, even if an IOR is obviously from a remote machine, if the implementation name that is embedded in the IOR matches that of the implementation name of the node on which it is being used, JacORB interprets the call as a local invocation!
> We can code around this bug by embedding a unique implementation name in each IOR.
> In the meantime, we will need to document this and inform all users to deploy with unique implementation names in their jacorb.properties files.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues