[
https://issues.jboss.org/browse/AS7-5394?page=com.atlassian.jira.plugin.s...
]
Epi Vou commented on AS7-5394:
------------------------------
From the stacktrace printed on the logs, it seems that the bug has
something to do with this code :
{code}
try
{
producer.send(dest, message);
}
catch (final HornetQException e)
{
log.warn("Unable to send message " + ref + ", will try again once
bridge reconnects", e);
// We remove this reference as we are returning busy which means the reference
will never leave the Queue.
// because of this we have to remove the reference here
refs.remove(ref);
executor.execute(new Runnable()
{
public void run()
{
connectionFailed(e, false);
}
});
return HandleStatus.BUSY;
}
{code}
It seems to me like the executor never runs the code, and this must be the reason why all
these StackTraceElements pile up in the heap.
So this must be clearly a hornetq issue, maybe it should be better if we reproduce it on
standalone hornetq server and post it on the hornetq project issues....
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