[
https://issues.jboss.org/browse/AS7-5394?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil commented on AS7-5394:
----------------------------------
your conf looks ok.
you divert (non-exclusively) messages sent to the jms.topic.livescoresTopic to the
jms.queue.proxy-queue.
this address is bound to the jms.queue.proxy-queue that is bridged to the
jms.topic.livescoresTopic on the *other* server using the jms-remote-connector (I assume
its socket-binding is correct and points to the other server).
Are you able to consume messages on the other server before blocking the JMS traffic?
Do you have errors in your logs?
MemoryLeak (StackTraceElement objects) in JMS 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), 7.1.3.Final (EAP)
Reporter: Epi Vou
Assignee: Jeff Mesnil
Attachments: bug.png
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