[
https://issues.apache.org/activemq/browse/SM-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45769#action_45769
]
Ron Gavlin commented on SM-1554:
--------------------------------
Hi Guillaume,
So, how about if this ticket represents the request " the JBI container should
be able to initialize all SAs first, then start them"?
Then, how about if I add a new JIRA to "support inter-SA dependencies to tweak
the SA startup order"?
Thoughts?
- Ron
> Suspending of deploying and starting component
> ----------------------------------------------
>
> Key: SM-1554
> URL: https://issues.apache.org/activemq/browse/SM-1554
> Project: ServiceMix
> Issue Type: Improvement
> Environment: SMX 3.2.x
> Reporter: Ivan Pryvalov
>
> Ivan,
> Startup and shutdown can be hard problems to tackle in this kind of
> environment, where services come and go as SA get deployed and removed. We
> should probably try to find a way to suspend message flows until all SA have
> been started or something else to avoid this kind of problem where a service
> starts sending messages to another one, that hasn't been started yet (because
> that is what you are trying to do here, I assume?). Could you submit a JIRA
> issue for this?
> Regards,
> Gert
> ivan wrote:
> > Hi!
> >
> > I faced following: service's installation can be suspended till needed
> > component (servicemix-bean etc) is installed.
> >
> > Can I use this mechanism to set dependency to some other service, but
> > component? I mean, installation and starting some service (service-unit) A
> > will be suspended till some service (service-unit) B is installed and
> > started.
> >
> > Thanks,
> > Ivan Pryvalov.
> >
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
