|
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----- Correction to my last
email, it’s a JMSReader (queues).
Sorry bout that. -----Original Message----- 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. |
- [JBoss-user] RE: possible JMS memory leak under 3.0.4? Eric J Kaplan
- RE: [JBoss-user] RE: possible JMS memory leak under 3.0... Eric J Kaplan
- RE: [JBoss-user] RE: possible JMS memory leak under 3.0... eric . kaplan
