-
Bug
-
Resolution: Done
-
Major
-
JBossAS-4.2.3.GA, JBossAS-5.0.0.CR2
-
None
-
Low
-
Workaround Exists
-
Transaction sticky target not available should be thrown as ServiceUnavailableException, otherwise
RetryInterceptor (RI) logic does not kick in when the cluster has restarted. The retry would fail as expected
because the previous transaction is no longer available but the RI avoids the client application having to
explicitly re-look home.
Note: UserTransaction has its RetryInterceptor-ish logic within ClientUserTransaction and hence this does
not affect it.
- is incorporated by
-
JBPAPP-1359 JBAS-6153 - Transaction sticky target not available should be thrown as ServiceUnavailableException
- Resolved