[
http://jira.jboss.com/jira/browse/JBAS-4607?page=all ]
Adrian Brock closed JBAS-4607.
------------------------------
Resolution: Done
Done. The fix is relatively trivial.
It involves only rolling back when we know there is an error
(we don't want to mask the real error if we know it)
i.e. something invoked setRollbackOnly on the TMS or Session.
otherwise we try to commit, which will raise an error if it timed out.
Transaction timeout is not raising a JMSException in the JBossMQ
Persistence manager or StateManager
----------------------------------------------------------------------------------------------------
Key: JBAS-4607
URL:
http://jira.jboss.com/jira/browse/JBAS-4607
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
In JBossMQ, if something other than the jdbc2 PersistenceManager or StateManager
marks a transaction as "setRollbackOnly", e.g. a transaction timeout
then they both silently rollback the exception without throwing an Exception.
An Exception should be thrown to tell the caller that the operation failed.
--
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