I'm looking for some guidance on how to cache JMS connections & sessions in my applications. The app does a JNDI lookup for the queueConnectionFactory & then goes and creates a connection & session for each JMS send. This is causing some performance implications & I was wondering how I would go about caching the connections & sessions so that they would not have to be created everytime.
I'm using WebSphere JMS resources for creating my queueConnectionFactory & queue. On the queueConnectionFactory I am able to define a pool of connections & sessions however, I presume that caching these connections & sessions in my app will improve performance. Is this correct?
Unfortunately using Spring is not an option for my current situation.