[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1220) When an JBM client encounters an OOM, it causes to hang the JBM server
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1220?page=comments#action_1... ]
Tyronne Wickramarathne commented on JBMESSAGING-1220:
-----------------------------------------------------
Remoting team confirmed that, they have implemented a way to prevent this on
JBR-2.2.2-brew. How this is achieved is by setting separate time out parameter for
callback clients on the Remoting configuration. The
http://jira.jboss.com/jira/browse/JBREM-765 describes this fix in detail.
on the Connector MBean config you have to add the callbackTimeout attribute as follows :
<mbean code="org.jboss.remoting.transport.Connector"
name="jboss.messaging:service=Connector,transport=bisocket"
display-name="Bisocket Transport Connector">
<attribute name="Configuration">
<config>
<invoker transport="bisocket">
<attribute name="marshaller"
isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
.............................
.............................
<attribute
name="callbackTimeout">10000</attribute> <!-- HERE -->
.............................
.............................
</invoker>
<handlers>
<handler
subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
</handlers>
</config>
</attribute>
</mbean>
When an JBM client encounters an OOM, it causes to hang the JBM
server
----------------------------------------------------------------------
Key: JBMESSAGING-1220
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1220
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.0.SP3_CP01
Environment: Fedora 8, JBM-1.4.0-SP3, JDK-1.5.0_14
Reporter: Tyronne Wickramarathne
Assigned To: Tyronne Wickramarathne
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
Attachments: stack_traces.zip, testcase.zip, testcase_win32.zip
1. Connect a JMS Topic Subscriber with limited memory (e.g. -Xmx64m), that buffers an
infinite number of messages.
2. Publish messages to JBM, on the same subscribed topic, until the client runs out of
memory.
3. Try to connect another client, publish more messages, etc. You should see the problem
at this point.
4. Kill the OOM client. The system should recover.
5. at this point, the JBM server gets hanged
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira