jms-spec
  1. jms-spec
  2. JMS_SPEC-146

Allow the registration of a message listener via a connection when done within an ManagedExecutorService.

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Labels:
      None

      Description

      Currently, you cannot call setMessageListener when a connection is running with in an application server. I believe we can circumvent this limitation if the registration of the underlying threads is done via a ManagedExecutorService. The spec should be updated to indicate that an implementation should register the delivery code via a ManagedExecutorService.

        Activity

        Hide
        Nigel Deakin added a comment -

        Adding to the list of issues to be considered for JMS 2.1 and tagging accordingly.

        Show
        Nigel Deakin added a comment - Adding to the list of issues to be considered for JMS 2.1 and tagging accordingly.

          People

          • Assignee:
            Unassigned
            Reporter:
            John D. Ament
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: