[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1220) When an JBM client encounters an OOM, it causes to hang the JBM server
Tim Fox (JIRA)
jira-events at lists.jboss.org
Tue Mar 4 12:11:57 EST 2008
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1220?page=comments#action_12401278 ]
Tim Fox commented on JBMESSAGING-1220:
--------------------------------------
We don't have access to any solaris or windows machines to test with.
Tyronne - can you check the following.
After the client has died, the server should detect the failure, and you should get the standard message on the server when the server tries to cleanup resources - can you verify this occurs, and investigate why this does not result in the server side resources being cleaned up.
> 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: Tim Fox
> 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
More information about the jboss-jira
mailing list