Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

JMS ConnectionFactory causing memory leak

76 views
Skip to first unread message

ste...@eccostudio.com

unread,
May 12, 2009, 6:02:47 AM5/12/09
to
Hi,

We're caching a JMS ConnectionFactory to reduce the number of repetitive JNDI lookups in some code deployed under Websphere Application Server 6.0.x. However we're seeing a number of heap dumps and investigation has indicated that this cached object is holding onto a huge number of references within com.ibm.ejs.j2c.poolmanager.PoolManager

We've checked the Sun API for the javax.jms.ConnectionFactory interface and it indicates:

"An administered object should not hold on to any remote resources" and "Clients should think of administered objects as local Java objects. Looking them up should not have any hidden side effects or use surprising amounts of local resources."

The IBM implementation of this interface is com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl. Are we wrong in holding on to a reference of this class or is there some other cause to this large consumption of memory?

Many thanks,

Stephen

Brian S Paskin

unread,
May 12, 2009, 7:13:18 AM5/12/09
to
Hi, which platform are you using and what is the exact version, including FixPaks are you using? If you are using connection pooling and set the number of connections very high, I would expect to have a large memory consumption. Then again, large is relative. What do you consider large and what is your maximum heap size set to?

Regards,
Brian

David Currie

unread,
May 13, 2009, 4:40:11 AM5/13/09
to
Stephen,

You should be fine caching the connection factory. As Brian suggests, it
sounds like your problem is more to do with the number of connections
that are being created on the connection factory.

Regards,
David

0 new messages