[
https://issues.apache.org/activemq/browse/SMXCOMP-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SMXCOMP-749.
-------------------------------------
Fix Version/s: servicemix-shared-2010.02
Resolution: Fixed
http://svn.apache.org/viewvc?view=revision&revision=946973 add an optional
timeout to the AsyncBaseLifeCycle.prepareShutdown() method,
which is then being used in
http://svn.apache.org/viewvc?view=revision&revision=946975 to get the Camel JBI
endpoints to use to the configured timeout value.
> No shutdown timeout for Camel JBI endpoints that are deployed with a Spring
> XML file in ServiceMix 4
> ----------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-749
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-749
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2010.01
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: servicemix-camel-2010.02, servicemix-shared-2010.02
>
>
> ServiceMix 4 has a shutdown timeout for JBI artifacts to ensure that the
> container or SA can be shutdown in a timely fashion. When a Camel JBI
> endpoint is being deployed using the Spring XML deployment in ServiceMix 4,
> this mechanism can not intervene because there's no real SA involved (or no
> EndpointExporter instance).
> We should improve the OSGi variant of the Camel JBI component to ensure that
> the value that has been configured in the *{{org.apache.servicemix.jbi}}* PID
> is taken into account when shutting down this type of endpoint as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
