[
https://issues.jboss.org/browse/AS7-4859?page=com.atlassian.jira.plugin.s...
]
Miroslav Novak moved JBPAPP-9100 to AS7-4859:
---------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-4859 (was: JBPAPP-9100)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.2.Final (EAP)
(was: EAP 6.0.0 ER 8)
Component/s: JMS
(was: HornetQ)
Security: (was: Public)
Fix Version/s: 7.1.3.Final (EAP)
(was: TBD EAP 6)
Docs QE Status: (was: NEW)
CLONE - Default value of id-cache-size attribute is potencially
dangerous when very small messages are used
-----------------------------------------------------------------------------------------------------------
Key: AS7-4859
URL:
https://issues.jboss.org/browse/AS7-4859
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.2.Final (EAP)
Reporter: Miroslav Novak
Assignee: Clebert Suconic
Fix For: 7.1.3.Final (EAP)
Hi,
I hit an issue with HornetQ core bridges. I tried test scenario with 4 nodes where:
1) there are two clusters A and B (each contains two nodes)
2) there is hornetq core bridge configured from cluster A to cluster B (A1 -> B1, A2
-> B2)
During sending messages (30KB ByteMessages) to A1 and reading them from B2, node A2 was
killed and started a few times. In the end there were duplicated messages. Problem was in
low value of id-cache-size attribute which is 2000 by default and confirmation-window-size
which is for bridges (1024 * 1024) bytes.
Can be default value of id-cache-size increased so we can avoid this situation? This is
potentially dangerous and hard for admins to realize before the problem occurs.
--
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