[
https://issues.apache.org/jira/browse/CXF-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025644#comment-13025644
]
David Liu commented on CXF-3473:
--------------------------------
Thanks Willem, I think it also would be good to allow user to config their own
Excutor. e.g. have a property for get/set Executor.
David
> Thread issue in CXF LocalConduit and LocalDestination
> -----------------------------------------------------
>
> Key: CXF-3473
> URL: https://issues.apache.org/jira/browse/CXF-3473
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2, 2.4
> Reporter: David Liu
> Assignee: Willem Jiang
>
> In CXF's LocalConduit and LocalDestination, it always creates a new Thread
> to process Request message and Response message. It will cause performance
> issue if we use Local transport for internal message routing.
> Can we use Executor instead of creating thread? thanks.
> In LocalDestination.java:
> {code}
> final Runnable receiver = new Runnable() {
> public void run() {
> if (exchange != null) {
> exchange.setInMessage(m);
> }
> conduit.getMessageObserver().onMessage(m);
> }
> };
>
> new Thread(receiver).start();
> {code}
> In LocalConduit:
> {code}
> final Runnable receiver = new Runnable() {
> public void run() {
> ExchangeImpl ex = new ExchangeImpl();
> ex.setInMessage(inMsg);
> ex.put(IN_EXCHANGE, exchange);
> destination.getMessageObserver().onMessage(inMsg);
> }
> };
> new Thread(receiver).start();
> {code}
> David
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
