| Summary: | EPNManager is present in RTGC-only configuration | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Jiri Pechanec <jpechane> |
| Component: | Configuration | Assignee: | Gary Brown <gbrown> |
| Status: | CLOSED NOTABUG | QA Contact: | Jiri Sedlacek <jsedlace> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | atangrin, oskutka, soa-p-jira |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-27 09:26:13 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
This component is different from the EventProcessorNetwork Manager - this component is responsible for listening for events from switchyard, so is fine in the rtgov client installation. I overlook it is not EventProcessor-NETWORK-Manager |
See startup log 11:08:23,987 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-5) JNDI bindings for session bean named EventProcessorManager in deployment unit deployment "overlord-rtgov.war" are as follows: java:global/overlord-rtgov/EventProcessorManager!org.overlord.rtgov.internal.switchyard.EventProcessorManager java:app/overlord-rtgov/EventProcessorManager!org.overlord.rtgov.internal.switchyard.EventProcessorManager java:module/EventProcessorManager!org.overlord.rtgov.internal.switchyard.EventProcessorManager java:global/overlord-rtgov/EventProcessorManager java:app/overlord-rtgov/EventProcessorManager java:module/EventProcessorManager