[
https://issues.apache.org/activemq/browse/SMX4-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen reassigned SMX4-106:
------------------------------------
Assignee: Gert Vanthienen
> Slow startup can cause bridge-sa deployment to fail
> ---------------------------------------------------
>
> Key: SMX4-106
> URL: https://issues.apache.org/activemq/browse/SMX4-106
> Project: ServiceMix 4
> Issue Type: Bug
> Affects Versions: 4.0-m1
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Priority: Minor
> Fix For: 4.0-m2
>
>
> If you start the container and deploy the bridge example too soon, it will
> fail to deploy because the ActiveMQ broker isn't running yet. It only gets
> started after the installation of the ActiveMQ bundles, which is fairly late
> in the startup process.
> We could
> - try to get the ActiveMQ broker running sooner - the MOM is important
> element of any ESB solution anyway, so it makes sense to get it up sooner
> - improve ServiceMix 4 startup time (perhaps we need to rework SMX4KNL-77 to
> retry the pending bundles every x seconds if something changed instead of for
> every bundle)
> - improve the JMS endpoints so they can start without a connection to the
> broker -- just like they can recover from a loss of connectivity
> Which (if not all) of these solutions should we implement?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
