[jbosscache-issues] [JBoss JIRA] (JBCACHE-1619) Rollback messages to be broadcast as out-of-band messages so they are not blocked on the receiver's end
Jitka Kudrnacova (JIRA)
jira-events at lists.jboss.org
Mon Sep 17 03:32:34 EDT 2012
[ https://issues.jboss.org/browse/JBCACHE-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718971#comment-12718971 ]
Jitka Kudrnacova edited comment on JBCACHE-1619 at 9/17/12 3:31 AM:
--------------------------------------------------------------------
The attached test case fails with jbosscache-core.jar version 3.2.10.GA from EAP 5.2.0.ER2.
Reopening.
[jkudrnac at jkudrnac ~]$ java -jar /home/jkudrnac/jboss/jboss-eap-5.2.0.ER2/jboss-eap-5.2/jboss-as/server/all/lib/jbosscache-core.jar
Version: 3.2.10.GA
Codename: Malagueta
History: (see http://jira.jboss.com/jira/browse/JBCACHE for details)
was (Author: jkudrnac):
The attached test case fails with jbosscache-core.jar version 3.2.10.GA from EAP 5.2.0.ER2.
Reopening.
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosscache-issues
mailing list