Bug 972400
Summary: | Error looking up infinispan/ovirt-engine, service service jboss.naming.context.java.jboss.infinispan.ovirt-engine is not started | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Alon Bar-Lev <alonbl> |
Component: | ovirt-engine | Assignee: | Yair Zaslavsky <yzaslavs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Barak Dagan <bdagan> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | acathrow, amureini, bazulay, dougsland, iheim, jkt, juan.hernandez, lpeer, mperina, oourfali, pstehlik, Rhev-m-bugs, yeylon, yzaslavs |
Target Milestone: | --- | ||
Target Release: | 3.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | infra | ||
Fixed In Version: | is3 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alon Bar-Lev
2013-06-09 07:34:29 UTC
Juan, last time we addressed this issue, you forwarded our thread to rhev-jboss. IIRC did not see any comments on this. Do we have at least any workaround we can do for now? You may try this patch: --- a/packaging/services/ovirt-engine.xml.in +++ b/packaging/services/ovirt-engine.xml.in @@ -9,6 +9,7 @@ <extension module="org.jboss.as.ee"/> <extension module="org.jboss.as.ejb3"/> <extension module="org.jboss.as.jaxrs"/> + <extension module="org.jboss.as.jmx"/> <extension module="org.jboss.as.jpa"/> <extension module="org.jboss.as.logging"/> <extension module="org.jboss.as.naming"/> @@ -35,6 +36,14 @@ </system-properties> + <management> + <management-interfaces> + <native-interface> + <socket-binding native="management"/> + </native-interface> + </management-interfaces> + </management> + <profile> <subsystem xmlns="urn:jboss:domain:logging:1.1"> @@ -216,6 +225,11 @@ </default-workmanager> </subsystem> + <subsystem xmlns="urn:jboss:domain:jmx:1.1"> + <show-model value="true"/> + <remoting-connector/> + </subsystem> + <subsystem xmlns="urn:jboss:domain:jpa:1.0"> <jpa default-datasource=""/> </subsystem> @@ -311,6 +325,7 @@ <socket-binding name="remoting" port="8703"/> <socket-binding name="txn-recovery-environment" port="8704"/> <socket-binding name="txn-status-manager" port="8705"/> + <socket-binding name="management" port="8706"/> </socket-binding-group> </server> The patch solves the issue on my development machine. Thanks Moving to modified as the change has been merged in the upstream master branch, so it will be part of downstream 3.3 after the next rebase. verified on is13. Can't find that error in my logs. Closing - RHEV 3.3 Released Closing - RHEV 3.3 Released Closing - RHEV 3.3 Released |