[GLASSFISH-15579] Document in release note that JMS connections and sessions should not be cached in a stateless session bean Created: 14/Jan/11  Updated: 14/Jan/11  Resolved: 14/Jan/11

Status: Resolved
Project: glassfish
Component/s: docs
Affects Version/s: 3.1_ms07
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Nigel Deakin Assignee: Paul Davies
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


Please document open issue http://java.net/jira/browse/GLASSFISH-15558 in the GlassFish 3.1 release note as follows:

A stateless session bean should not save JMS connections or sessions in fields of the bean. Applications that do so may encounter errors.

To avoid this issue, if a stateless session bean's business method requires the use of a JMS connection and session then the business method should create the JMS connection and session, use it to send or receive messages, and then close the connection and session before returning. This is GlassFish issue 15558.

Comment by Paul Davies [ 14/Jan/11 ]

This issue is unnecessary. To mark an engineering issue for inclusion in the GlassFish 3.1 Release Notes, add the tag 3_1-releasenotes to the issue.

I have added the tag 3_1-releasenotes and the suggested text from this issue to GLASSFISH-15558.

Generated at Tue Apr 28 16:13:21 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.