Does this ring a bell with anyone?  Or is this question so outlandish no one’s responding for fear of embarrassing me…

 

Regards

 

Eric

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric J Kaplan
Sent:
Friday, June 27, 2003 9:42 AM
To: 'Eric J Kaplan'; [EMAIL PROTECTED]
Subject: [JBoss-user] RE: possible JMS memory leak under 3.0.4?

 

Correction to my last email, it’s a JMSReader (queues).  Sorry bout that.

 

-----Original Message-----
From: Eric J Kaplan [mailto:[EMAIL PROTECTED]
Sent:
Friday, June 27, 2003 9:37 AM
To: '[EMAIL PROTECTED]'
Subject: possible JMS memory leak under 3.0.4?

 

Hi all

 

I’m seeing what may be a memory leak using a JMSSubscriber in JBoss using JProbe memory debugger.

 

JMSResponseDispatcher.callbacks references Collection$SynchronizedMap that ultimately references a SynchronousRequestImpl, which references a Response, in which result references the data I’m sending over JMS.  The question is, after garbage collection, why would SynchronousRequestImpl still reference this if all of the subscribers have been called back?  How can I confirm that this indeed is the case, that all subscribers have been called back?  Are there any diagnostics I can turn on or look for?

 

Regards

 

Eric J. Kaplan

Armanta, Inc.

350 Mt. Kemble Ave.

Morristown, NJ 07960

 

Reply via email to