[
https://issues.jboss.org/browse/AS7-5394?page=com.atlassian.jira.plugin.s...
]
Epi Vou commented on AS7-5394:
------------------------------
Here's the messaging configuration :
<subsystem xmlns="urn:jboss:domain:messaging:1.2">
<hornetq-server>
<persistence-enabled>true</persistence-enabled>
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<netty-connector name="jms-remote-connector"
socket-binding="jms-remote"/>
<in-vm-connector name="in-vm"
server-id="0"/>
</connectors>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver"
value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm"
server-id="0"/>
</acceptors>
<diverts>
<divert name="proxy-divert">
<routing-name>proxy-divert</routing-name>
<address>jms.topic.livescoresTopic</address>
<forwarding-address>jms.queue.proxy-queue</forwarding-address>
<filter string="filter = 'match_update' OR filter
= 'odds_aagregate_update' OR filter = 'backend_push_event'"/>
<exclusive>false</exclusive>
</divert>
</diverts>
<bridges>
<bridge name="jms-proxy-bridge">
<queue-name>jms.queue.proxy-queue</queue-name>
<forwarding-address>jms.topic.livescoresTopic</forwarding-address>
<ha>false</ha>
<reconnect-attempts>9999999</reconnect-attempts>
<failover-on-server-shutdown>false</failover-on-server-shutdown>
<use-duplicate-detection>false</use-duplicate-detection>
<user>username</user>
<password>password</password>
<static-connectors>
<connector-ref>
jms-remote-connector
</connector-ref>
</static-connectors>
</bridge>
</bridges>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume"
roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<address-settings>
<address-setting match="#">
<dead-letter-address>jms.queue.DLQ</dead-letter-address>
<expiry-address>jms.queue.ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<max-size-bytes>10485760</max-size-bytes>
<address-full-policy>BLOCK</address-full-policy>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
</address-setting>
</address-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry
name="java:jboss/exported/jms/RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<transaction mode="xa"/>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="fileQ">
<entry name="/queue/enetpulse/fileQ"/>
</jms-queue>
<jms-queue name="processingQ">
<entry name="/queue/enetpulse/processingQ"/>
</jms-queue>
<jms-queue name="inCompleteDataQ">
<entry name="/queue/enetpulse/inCompleteDataQ"/>
</jms-queue>
<jms-queue name="persistenceQ">
<entry name="/queue/enetpulse/persistenceQ"/>
</jms-queue>
<jms-queue name="DLQ">
<entry name="/queue/DLQ"/>
</jms-queue>
<jms-queue name="pushNotificationQ">
<entry name="/queue/pushNotificationQ"/>
</jms-queue>
<jms-queue name="proxy-queue">
<entry name="java:/queue/proxy"/>
<durable>true</durable>
</jms-queue>
<jms-topic name="livescoresTopic">
<entry name="topic/livescores"/>
</jms-topic>
</jms-destinations>
</hornetq-server>
</subsystem>
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