[
https://issues.apache.org/activemq/browse/SMX4-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59004#action_59004
]
Gert Vanthienen edited comment on SMX4-519 at 4/21/10 5:35 AM:
---------------------------------------------------------------
Fixed in http://svn.apache.org/viewvc?view=revision&revision=936226
You can now specify *{{from("nmr:Service?synchronous=true")}}* to handle the
incoming NMR exchange on the sender's thread instead of using a new thread from
the thread pool.
was (Author: gertvanthienen):
Fixed in http://svn.apache.org/viewvc?view=revision&revision=936226
You can now specify *{{from("nmr:Service?synchronous=true}}* to handle the
incoming NMR exchange on the sender's thread instead of using a new thread from
the thread pool.
> Allow configuring Camel NMR endpoint to bypass thread pool for handling
> exchanges
> ---------------------------------------------------------------------------------
>
> Key: SMX4-519
> URL: https://issues.apache.org/activemq/browse/SMX4-519
> Project: ServiceMix 4
> Issue Type: Bug
> Affects Versions: 4.2.0
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: 4.4.0
>
>
> When an NMR Exchange gets delivered to a Camel *{{nmr:...}}* endpoint, the
> default behavior is to handle the Exchange in a separate thread from the
> NMR's Endpoint thread pool. The NMR endpoint can also be configured to use a
> Channel which handles the Exchange delivery on the sender's thread, so we
> should expose this option to the Camel NMR endpoint by adding support for a
> URI parameter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
