[JBoss JIRA] (JBCACHE-1619) Rollback messages to be broadcast as out-of-band messages so they are not blocked on the receiver's end
7:16 p.m.
Dennis Reed created JBCACHE-1619:
------------------------------------
Summary: 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
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
8:04 p.m.
[
https://issues.jboss.org/browse/JBCACHE-1619?page=com.atlassian.jira.plug...
]
Dennis Reed resolved JBCACHE-1619.
----------------------------------
Resolution: Done
Fixed in 3.2.10
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
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
1:15 p.m.
[
https://issues.jboss.org/browse/JBCACHE-1619?page=com.atlassian.jira.plug...
]
Dennis Reed updated JBCACHE-1619:
---------------------------------
Attachment: JBCACHE-1619-test.zip
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
1:19 p.m.
[
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
2:30 a.m.
[
https://issues.jboss.org/browse/JBCACHE-1619?page=com.atlassian.jira.plug...
]
Jitka Kudrnacova reopened JBCACHE-1619:
---------------------------------------
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
2:32 a.m.
[
https://issues.jboss.org/browse/JBCACHE-1619?page=com.atlassian.jira.plug...
]
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@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
2:45 p.m.
[
https://issues.jboss.org/browse/JBCACHE-1619?page=com.atlassian.jira.plug...
]
Dennis Reed resolved JBCACHE-1619.
----------------------------------
Resolution: Done
The test case also fails on a similar issue JBCACHE-1621, which you're seeing.
(JBCACHE-1621 didn't make the 3.2.10 cutoff).
To verify this fix, you can look for the following in output.log showing whether
RollbackCommand is using OOB:
2012-09-17 14:37:01,243 TRACE [org.jboss.cache.RPCManagerImpl] (Thread-2)
callRemoteMethods(): valid members are null methods:
ReplicateCommand{cmds=RollbackCommand{gtx=GlobalTransaction:<127.0.0.1:55200>:1}}
Using OOB? true modeToUse: 6
With JBCACHE-1619, it should show "Using OOB? true"
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
12:11 a.m.
[
https://issues.jboss.org/browse/JBCACHE-1619?page=com.atlassian.jira.plug...
]
Jitka Kudrnacova commented on JBCACHE-1619:
-------------------------------------------
Sorry for the confusion and thank you for the information. Will verify when time allows.
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
12:15 a.m.
[
https://issues.jboss.org/browse/JBCACHE-1619?page=com.atlassian.jira.plug...
]
Jitka Kudrnacova edited comment on JBCACHE-1619 at 9/18/12 1:13 AM:
--------------------------------------------------------------------
Sorry for the false alarm and thank you for the information. Will verify when time
allows.
was (Author: jkudrnac):
Sorry for the confusion and thank you for the information. Will verify when time
allows.
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
4240
days inactive
4287
days old
jbosscache-issues@lists.jboss.org
8 comments
2 participants
participants (2)
-
Dennis Reed (JIRA) -
Jitka Kudrnacova (JIRA)