[
https://issues.jboss.org/browse/AS7-5394?page=com.atlassian.jira.plugin.s...
]
Epi Vou commented on AS7-5394:
------------------------------
Hello again,
Yesterday I made a change on BridgeImpl.java at the part of the code that I have
referenced above, so that the connectionFailed() routine is not called by the executor,
but in the same thread handling the exception. I run the test the whole day and the issue
seems resolved. However I believe someone with deeper knowledge of HornetQ should have a
look at this, I guess there is a reason why the connectionFailed() routine is called
through an executor...
MemoryLeak in core bridges when the connection times out
--------------------------------------------------------
Key: AS7-5394
URL:
https://issues.jboss.org/browse/AS7-5394
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.2.Final (EAP)
Reporter: Epi Vou
Assignee: Jeff Mesnil
Attachments: bug.png, jboss1-logs.tar.gz, jboss2-logs.tar.gz
A jboss server eventually will start throwing OutOfMemory exceptions when it is
configured to forward jms messages to another server using a bridge, and the network is
unstable.
--
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