[JBoss JIRA] Created: (JBMESSAGING-1220) When an JBM client encounters an OOM, it causes to hang the JBM server
10:06 a.m.
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
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
10:25 a.m.
New subject: [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... ]
Tim Fox commented on JBMESSAGING-1220:
--------------------------------------
Tyronne - can you provide server and client side stack dumps for when this occurs?
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
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
7:30 a.m.
New subject: [JBoss JIRA] Updated: (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=all ]
Tyronne Wickramarathne updated JBMESSAGING-1220:
------------------------------------------------
Attachment: testcase.zip
i have attached a test case to reproduce this issue. however, i did manage to reproduce
this just once on my Fedora box, following the given instructions.
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
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
11:08 a.m.
New subject: [JBoss JIRA] Updated: (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=all ]
Tyronne Wickramarathne updated JBMESSAGING-1220:
------------------------------------------------
Attachment: testcase_win32.zip
This is more a windows specific problem as it's not always reproducible on Linux. i
have attached the test case for this along with the StackTrace, which i took when the
server was not responding.
Windows Env :
Windows Vista Home Premium , JBM-1.4.0-SP3, JDK-1.5.0_14, JBoss-EAP-4.2_CP1
Hardware :
2 GB Ram, 2.2 GHz Core 2 Duo Proc
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
11:22 a.m.
New subject: [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
11:40 a.m.
New subject: [JBoss JIRA] Updated: (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=all ]
Tyronne Wickramarathne updated JBMESSAGING-1220:
------------------------------------------------
Attachment: stack_traces.zip
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: 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
2:35 p.m.
New subject: [JBoss JIRA] Updated: (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=all ]
Tim Fox updated JBMESSAGING-1220:
---------------------------------
Fix Version/s: 1.4.0.SP3.CP02
1.4.1.beta2
Affects Version/s: 1.4.0.SP3_CP01
(was: 1.4.0.SP3)
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
11:11 a.m.
New subject: [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... ]
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
11:13 a.m.
New subject: [JBoss JIRA] Assigned: (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=all ]
Tim Fox reassigned JBMESSAGING-1220:
------------------------------------
Assignee: Tyronne Wickramarathne (was: Tim Fox)
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
11:32 a.m.
New subject: [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:
-----------------------------------------------------
Tim
sure. i will start working on this. will post you with my findings on 06-Mar-2008 by
14:00hrs GMT
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
6:30 a.m.
New subject: [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... ]
Tim Fox commented on JBMESSAGING-1220:
--------------------------------------
I have had a chance to have a look at this.
My initial observations on this case are:
The description reads "buffers an infinite number of messages. " This implies to
me that the prefetchSize has been set to a very large value (default is 150).
With a TCP connection if messages are written to one end of the connection faster than
they are read from the other end of the connection, then eventually the calls to write()
will block. TCP will allow a certain amount of data to be buffered before blocking (TCP
window size).
If prefetchSize has been set to a very large value then you are effectively defaulting to
TCP for flow control.
Default socket timeout is currently set to zero (infinite) so the call to write will block
for ever.
Workaround would be to make sure prefetchSize is set to a value lower than the TCP window
size.
Default TCP window size on Windows and Linux varies so this could account for differences
in behaviour between the operating systems (IIRC it is usually lower on windows ==>
quicker to block).
Unless you can deal with blocking TCP writes you should ensure that prefetch Size is set
to a value that has an effect before the TCP window kicks in.
I will also confer with the remoting team to see if the socket timeout for writes can be
specified separately in the remoting config.
Tyronne - can you verify that setting prefetchSize to a smaller value for the size of
messages solves the problem?
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
9:09 a.m.
New subject: [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... ]
Jeff Wilker commented on JBMESSAGING-1220:
------------------------------------------
I am the customer behind this Jira. This problem will occur on Windows and Solaris with
stock EAP 4.3 installs (prefectSize=150).
I have confirmed that a lower prefectSize (10) appears to resolve the problem on Windows
in our environment.
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
10:42 a.m.
New subject: [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... ]
Tim Fox commented on JBMESSAGING-1220:
--------------------------------------
Hello Jeff-
The actual value of prefetchSize will depend on the size of your messages. The larger your
messages the smaller the prefetchSize.
I'm glad the workaround works, but I will chase the remoting team anyway, to see if we
can introduce a timeout on the server which will prevent the hang even if the prefetch
size is larger.
Thanks for your patience in this. I know this one has taken a long time to resolve.
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
8:36 a.m.
New subject: [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
8:17 a.m.
New subject: [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... ]
Tim Fox commented on JBMESSAGING-1220:
--------------------------------------
We should consider having the remoting timeout for callbacks set to a smaller value by
default. (e..g. 10 seconds)
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
11:48 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1220) Delivery attempts can hang if the TCP buffer is full
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1220?page=all ]
Tim Fox updated JBMESSAGING-1220:
---------------------------------
Summary: Delivery attempts can hang if the TCP buffer is full (was: When an JBM
client encounters an OOM, it causes to hang the JBM server)
Delivery attempts can hang if the TCP buffer is full
----------------------------------------------------
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
12:31 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1220) Delivery attempts can hang if the TCP buffer is full
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1220?page=all ]
Tim Fox closed JBMESSAGING-1220.
--------------------------------
Resolution: Won't Fix
Delivery attempts can hang if the TCP buffer is full
----------------------------------------------------
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
12:31 p.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1220) Delivery attempts can hang if the TCP buffer is full
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1220?page=all ]
Tim Fox reopened JBMESSAGING-1220:
----------------------------------
Delivery attempts can hang if the TCP buffer is full
----------------------------------------------------
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
12:37 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1220) Delivery attempts can hang if the TCP buffer is full
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1220?page=all ]
Tim Fox closed JBMESSAGING-1220.
--------------------------------
Resolution: Done
I have updated the remoting config to use a callbackTimeout of 10000 ms by default.
Delivery attempts can hang if the TCP buffer is full
----------------------------------------------------
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
6400
days inactive
6471
days old
18 comments
3 participants
participants (3)
-
Jeff Wilker (JIRA) -
Tim Fox (JIRA)
-
Tyronne Wickramarathne (JIRA)