[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:
-----------------------------------------------------
How to reproduce this issue with the attached win32 test case (testcase_win32.zip) :
1 ) edit Java files to point to the JMS provider
2 ) edit *.bat files to set the class path accordingly
3 ) execute the runSubscriber.bat then runPublisher.bat
4 ) in a few seconds, the SimpleTopicSubscriber.java will get hang, when this happens
5 ) execute the runTestSubscriber.bat then runTestPublisher.bat
6 ) you can notice that the JMS provider isn't responsive at this point
Tyronne
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
Environment: Fedora 8, JBM-1.4.0-SP3, JDK-1.5.0_14
Reporter: Tyronne Wickramarathne
Assigned To: Tim Fox
Attachments: 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