You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Andrei Shakirin (JIRA)" <ji...@apache.org> on 2015/12/06 16:26:10 UTC

[jira] [Updated] (CXF-6702) Support external executor for JMS Containers

     [ https://issues.apache.org/jira/browse/CXF-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrei Shakirin updated CXF-6702:
---------------------------------
    Description: 
Currently PollingMessageListenerContainer uses internal ServiceExecutor based on FixedThreadPool to pool received JMS messages.
There is a requirement to provide an option to use external Executor (e.g. ApplicationService executor) for that.

Requirement was discussed in this thread: http://cxf.547215.n5.nabble.com/CXF-3-1-x-missing-taskExecutor-and-unmanaged-threads-td5763221.html 



  was:
Currently PollingMessageListenerContainer uses internal ServiceExecutor based on FixedThreadPool to pool received JMS messages.
There is a requirement to provide an option to use external Executor (e.g. ApplicationService executor) for that.




> Support external executor for JMS Containers
> --------------------------------------------
>
>                 Key: CXF-6702
>                 URL: https://issues.apache.org/jira/browse/CXF-6702
>             Project: CXF
>          Issue Type: Improvement
>          Components: JMS
>            Reporter: Andrei Shakirin
>
> Currently PollingMessageListenerContainer uses internal ServiceExecutor based on FixedThreadPool to pool received JMS messages.
> There is a requirement to provide an option to use external Executor (e.g. ApplicationService executor) for that.
> Requirement was discussed in this thread: http://cxf.547215.n5.nabble.com/CXF-3-1-x-missing-taskExecutor-and-unmanaged-threads-td5763221.html 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)