[
https://issues.jboss.org/browse/JBCACHE-1619?page=com.atlassian.jira.plug...
]
Dennis Reed updated JBCACHE-1619:
---------------------------------
Steps to Reproduce:
See README in attached JBCACHE-1619-test.zip.
Note: this test can also trigger the issue in JBCACHE-1621 when run against a jar
containing JBCACHE-1619 but not JBCACHE-1621.
Rollback messages to be broadcast as out-of-band messages so they are
not blocked on the receiver's end
-------------------------------------------------------------------------------------------------------
Key: JBCACHE-1619
URL:
https://issues.jboss.org/browse/JBCACHE-1619
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Replication
Affects Versions: 3.2.9.GA
Reporter: Dennis Reed
Assignee: Dennis Reed
Attachments: JBCACHE-1619-test.zip
Same issue as JBCACHE-1270 for Commit messages.
Without OOB, rollback messages have to wait in the queue behind all other messages.
Processing those messages may need resources being held by the transaction being rolled
back, and will deadlock.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira