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.

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

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

              Dates

              • Created:
                Updated: