The HA version of the UnifiedInvokerProxy allows clients running transactions to fail over when they should not. See JBAS-4950. This is a much more serious problem than the reverse, not allowing failover when it should be allowed, since allowing failover can result in inconsistent tx results, while not allowing it just means the tx gets rolled back unnecessarily.
Description
The HA version of the UnifiedInvokerProxy allows clients running transactions to fail over when they should not. See JBAS-4950. This is a much more serious problem than the reverse, not allowing failover when it should be allowed, since allowing failover can result in inconsistent tx results, while not allowing it just means the tx gets rolled back unnecessarily.
Brian Stansberry [19/Nov/07 02:28 PM]
Looks like Galder's fixed JBAS-4950, so unless there's something really tricky I don't see why he or I couldn't port it to an EAP branch this week.
Bug
Resolved
Critical
Transaction failover authorisation is broken within UnifiedInvokerHAProxy
