[JMS_SPEC-146] Allow the registration of a message listener via a connection when done within an ManagedExecutorService. Created: 25/Jan/14 Updated: 29/Jun/15
|Reporter:||John D. Ament||Assignee:||Unassigned|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
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.
|Comment by Nigel Deakin [ 04/Feb/14 ]|
Adding to the list of issues to be considered for JMS 2.1 and tagging accordingly.