[
http://jira.jboss.com/jira/browse/JBMESSAGING-920?page=comments#action_12... ]
Kevin Conner commented on JBMESSAGING-920:
------------------------------------------
There were two issues found with remoting on the client side and I have now found an issue
with Messaging.
The ServerSessionEndpoint code contains an executor for each instance. Unfortunately
nothing shuts down the executor which means that the threads created by the executor are
never destroyed.
I modified the messaging code to include a call to executor.shutdownNow() in
ServerSessionEndpoint.close() and this appears to have done the trick.
Make sure JBM 1.2. works with ESB 4.0
-------------------------------------
Key: JBMESSAGING-920
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-920
Project: JBoss Messaging
Issue Type: Task
Components: AS Integration
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Priority: Blocker
Fix For: 1.2.1.CR1
Attachments: NotifyQueuesExample.java
Kurt's report:
I have extracted the 'essence' of what our ESB engine does with JMS messaging.
I'm sending a message to queue/A and then I'm receiving the same message, I do
some cleanup (closing session and connection) and then it starts all over again. Yes for
each message I'm setting up the connection and then cleaning it up.
The problem I'm seeing is the the GC is not able to clean up the JMS objects as it
loops around. So at some point this this example nicely blows up when it runs out of
memory. Your mileage may vary but it usually is around 800 messages.
Any ideas why the GC can't make this work? I've testing this with JBM 1.2 GA. But
I think JBMQ has the same problem. I'm running JDK-1.5.0_10.
JBossMQ crashes too. Although a different error it's also due to running out of
memory.
--
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