[
https://issues.apache.org/jira/browse/OOZIE-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junfan Zhang reassigned OOZIE-3511:
-----------------------------------
Assignee: Junfan Zhang
> Different services orders defined in oozie.services.ext can lead to different
> results
> -------------------------------------------------------------------------------------
>
> Key: OOZIE-3511
> URL: https://issues.apache.org/jira/browse/OOZIE-3511
> Project: Oozie
> Issue Type: Bug
> Reporter: Julia Kinga Marton
> Assignee: Junfan Zhang
> Priority: Major
>
> Based on the order we define the services using {{oozie.services.ext}}
> property can lead to different results.
> For example in the following case the JMS services will fail to start
> correctly:
> {noformat}
> org.apache.oozie.service.ZKLocksService,org.apache.oozie.service.ZKXLogStreamingService,org.apache.oozie.service.ZKJobsConcurrencyService,org.apache.oozie.service.ZKUUIDService,org.apache.oozie.service.EventHandlerService,org.apache.oozie.sla.service.SLAService,org.apache.oozie.service.JMSAccessorService,org.apache.oozie.service.JMSTopicService,org.apache.oozie.service.PartitionDependencyManagerService,org.apache.oozie.service.HCatAccessorService,org.apache.oozie.service.MetricsInstrumentationService
> {noformat}
> If we exchange the JMSTopicService with the EventHandlerService, than if will
> work as expected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
