glassfish
  1. glassfish
  2. GLASSFISH-15579

Document in release note that JMS connections and sessions should not be cached in a stateless session bean

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.1_ms07
    • Fix Version/s: None
    • Component/s: docs
    • Labels:
      None

      Description

      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.

        Activity

          People

          • Assignee:
            Paul Davies
            Reporter:
            Nigel Deakin
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: