You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Geert Schuring (JIRA)" <ji...@apache.org> on 2010/12/27 13:51:46 UTC
[jira] Commented: (SMX4NMR-233) NMR should block if target service
is unavailable to facilitate lazy init of services and/or temporary
abscence of a service.
[ https://issues.apache.org/jira/browse/SMX4NMR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975246#action_12975246 ]
Geert Schuring commented on SMX4NMR-233:
----------------------------------------
When using clustering this already happens as the request message remains in the message queue until a client processes it. I agree that the NMR should behave similarly when only local endpoints are used.
> NMR should block if target service is unavailable to facilitate lazy init of services and/or temporary abscence of a service.
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: SMX4NMR-233
> URL: https://issues.apache.org/jira/browse/SMX4NMR-233
> Project: ServiceMix NMR
> Issue Type: Improvement
> Reporter: Adrian Trenaman
>
> Right now, if you use the NMR within ServiceMix 4 (I'm using 4.3 FUSE), an invocation on a service that is not registered on the NMR will fail immediately. It would be better if it did not fail, but block for a period of time (say 30 seconds, similar to the delay on an OSGi service in blueprint / Spring DM) and only fail if the target has not returned in the delay period. This way we can handle temporary outages of backend services and service updates.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.