From: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; To: "engine-devel" <engine-devel(a)ovirt.org&gt; Sent: Thursday, May 2, 2013 11:11:03 PM Subject: [Engine-devel] Error looking up infinispan/ovirt-engine Hello, I get these (lots of these) using latest master... anyone knows what was changed? At server.log I see: --- 2013-05-02 19:58:08,046 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 21) JBAS010280: Activating Infinispan subsystem. <snip> 2013-05-02 19:58:10,155 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.mbean.server (missing) dependents: [service jboss.infinispan.ovirt-engine.config] --- Thanks, Alon --- 2013-05-02 20:02:10,012 ERROR [org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy] (DefaultQuartzScheduler_Worker-7) [4b3a50f7] Failed to lookup resource type: CACHE_CONTAINER. JNDI name: java:jboss/infinispan/ovirt-engine: javax.naming.NameNotFoundException: Error looking up infinispan/ovirt-engine, service service jboss.naming.context.java.jboss.infinispan.ovirt-engine is not started at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_17] at org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy.findBean(EJBUtilsStrategy.java:104) [utils.jar:] at org.ovirt.engine.core.utils.ejb.EjbUtils.findBean(EjbUtils.java:23) [utils.jar:] at org.ovirt.engine.core.utils.cache.CacheManager.getTimeoutBaseCache(CacheManager.java:12) [utils.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.TimeoutBase.getLegal(TimeoutBase.java:51) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:809) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:803) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:799) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase.log(AuditLogableBase.java:437) [dal.jar:] at org.ovirt.engine.core.bll.CommandBase.logCommand(CommandBase.java:1208) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1175) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:318) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:332) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:534) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_17] 2013-05-02 20:02:10,059 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase] (DefaultQuartzScheduler_Worker-7) [4b3a50f7] Error during log command: org.ovirt.engine.core.bll.SetNonOperationalVdsCommand. Exception java.lang.NullPointerException: java.lang.NullPointerException at org.ovirt.engine.core.utils.cache.CacheManager.getTimeoutBaseCache(CacheManager.java:13) [utils.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.TimeoutBase.getLegal(TimeoutBase.java:51) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:809) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:803) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:799) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase.log(AuditLogableBase.java:437) [dal.jar:] at org.ovirt.engine.core.bll.CommandBase.logCommand(CommandBase.java:1208) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1175) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:318) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:332) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:534) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_17] 2013-05-02 20:02:10,360 ERROR [org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy] (DefaultQuartzScheduler_Worker-7) [4b3a50f7] Failed to lookup resource type: CACHE_CONTAINER. JNDI name: java:jboss/infinispan/ovirt-engine: javax.naming.NameNotFoundException: Error looking up infinispan/ovirt-engine, service service jboss.naming.context.java.jboss.infinispan.ovirt-engine is not started at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_17] at org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy.findBean(EJBUtilsStrategy.java:104) [utils.jar:] at org.ovirt.engine.core.utils.ejb.EjbUtils.findBean(EjbUtils.java:23) [utils.jar:] at org.ovirt.engine.core.utils.cache.CacheManager.getTimeoutBaseCache(CacheManager.java:12) [utils.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.TimeoutBase.getLegal(TimeoutBase.java:51) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:809) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:803) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:799) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase.log(AuditLogableBase.java:437) [dal.jar:] at org.ovirt.engine.core.bll.CommandBase.logCommand(CommandBase.java:1208) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1175) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:318) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:332) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:534) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_17] 2013-05-02 20:02:10,407 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase] (DefaultQuartzScheduler_Worker-7) [4b3a50f7] Error during log command: org.ovirt.engine.core.bll.SetNonOperationalVdsCommand. Exception java.lang.NullPointerException: java.lang.NullPointerException at org.ovirt.engine.core.utils.cache.CacheManager.getTimeoutBaseCache(CacheManager.java:13) [utils.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.TimeoutBase.getLegal(TimeoutBase.java:51) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:809) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:803) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:799) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase.log(AuditLogableBase.java:437) [dal.jar:] at org.ovirt.engine.core.bll.CommandBase.logCommand(CommandBase.java:1208) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1175) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:318) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:332) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:534) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_17] _______________________________________________ Engine-devel mailing list Engine-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel

Hi, Thanks... no I did not follow. If -P setup is required then the Makefile should have been changed, else our production and rpms are broken now! Well... looking at the pom.xml, it looks like the jboss standalone is configured with -P setup is used, which is yet another hack introduced to developers... As they do not run our service, and suffer from lack of proper environment and configuration settings. My work[1] is exactly to address this one, to eliminate the need for hacking the product and use our production startup sequence and installation. At ./packaging/services/ovirt-engine.xml.in we already have the infinispan settings. So still need your help. Thanks, Alon

[1] https://github.com/alonbl/ovirt-engine/blob/otopi/README.developer ----- Original Message ----- > From: "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt; > To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; > Cc: "engine-devel" <engine-devel(a)ovirt.org&gt; > Sent: Friday, May 3, 2013 7:10:37 AM > Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine > > Hi Alon, > I might check this later on today. > Did you follow Kublin's email about introducing infinispan? he sent it to > engine-devel (you're supposed during the build to perform -P setup) > > Yair > > > ----- Original Message ----- >> From: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >> To: "engine-devel" <engine-devel(a)ovirt.org&gt; >> Sent: Thursday, May 2, 2013 11:11:03 PM >> Subject: [Engine-devel] Error looking up infinispan/ovirt-engine >> >> Hello, >> >> I get these (lots of these) using latest master... anyone knows what was >> changed? >> >> At server.log I see: >> --- >> 2013-05-02 19:58:08,046 INFO [org.jboss.as.clustering.infinispan] >> (ServerService Thread Pool -- 21) JBAS010280: Activating Infinispan >> subsystem. >> <snip> >> 2013-05-02 19:58:10,155 INFO [org.jboss.as.controller] (Controller Boot >> Thread) JBAS014774: Service status report >> JBAS014775: New missing/unsatisfied dependencies: >> service jboss.mbean.server (missing) dependents: [service >> jboss.infinispan.ovirt-engine.config] >> >> --- >> >> Thanks, >> Alon >> >> --- >> >> 2013-05-02 20:02:10,012 ERROR >> [org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy] >> (DefaultQuartzScheduler_Worker-7) [4b3a50f7] Failed to lookup resource >> type: >> CACHE_CONTAINER. JNDI name: java:jboss/infinispan/ovirt-engine: >> javax.naming.NameNotFoundException: Error looking up >> infinispan/ovirt-engine, service service >> jboss.naming.context.java.jboss.infinispan.ovirt-engine is not started >> at >> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126) >> at >> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) >> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) >> at >> org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123) >> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) >> at javax.naming.InitialContext.lookup(InitialContext.java:411) >> [rt.jar:1.7.0_17] >> at >> org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy.findBean(EJBUtilsStrategy.java:104) >> [utils.jar:] >> at >> org.ovirt.engine.core.utils.ejb.EjbUtils.findBean(EjbUtils.java:23) >> [utils.jar:] >> at >> org.ovirt.engine.core.utils.cache.CacheManager.getTimeoutBaseCache(CacheManager.java:12) >> [utils.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.TimeoutBase.getLegal(TimeoutBase.java:51) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:809) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:803) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:799) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase.log(AuditLogableBase.java:437) >> [dal.jar:] >> at >> org.ovirt.engine.core.bll.CommandBase.logCommand(CommandBase.java:1208) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1175) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:318) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:332) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:534) >> [bll.jar:] >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> [rt.jar:1.7.0_17] >> >> 2013-05-02 20:02:10,059 ERROR >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase] >> (DefaultQuartzScheduler_Worker-7) [4b3a50f7] Error during log command: >> org.ovirt.engine.core.bll.SetNonOperationalVdsCommand. Exception >> java.lang.NullPointerException: java.lang.NullPointerException >> at >> org.ovirt.engine.core.utils.cache.CacheManager.getTimeoutBaseCache(CacheManager.java:13) >> [utils.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.TimeoutBase.getLegal(TimeoutBase.java:51) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:809) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:803) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:799) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase.log(AuditLogableBase.java:437) >> [dal.jar:] >> at >> org.ovirt.engine.core.bll.CommandBase.logCommand(CommandBase.java:1208) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1175) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:318) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:332) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:534) >> [bll.jar:] >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> [rt.jar:1.7.0_17] >> >> 2013-05-02 20:02:10,360 ERROR >> [org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy] >> (DefaultQuartzScheduler_Worker-7) [4b3a50f7] Failed to lookup resource >> type: >> CACHE_CONTAINER. JNDI name: java:jboss/infinispan/ovirt-engine: >> javax.naming.NameNotFoundException: Error looking up >> infinispan/ovirt-engine, service service >> jboss.naming.context.java.jboss.infinispan.ovirt-engine is not started >> at >> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126) >> at >> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) >> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) >> at >> org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123) >> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) >> at javax.naming.InitialContext.lookup(InitialContext.java:411) >> [rt.jar:1.7.0_17] >> at >> org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy.findBean(EJBUtilsStrategy.java:104) >> [utils.jar:] >> at >> org.ovirt.engine.core.utils.ejb.EjbUtils.findBean(EjbUtils.java:23) >> [utils.jar:] >> at >> org.ovirt.engine.core.utils.cache.CacheManager.getTimeoutBaseCache(CacheManager.java:12) >> [utils.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.TimeoutBase.getLegal(TimeoutBase.java:51) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:809) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:803) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:799) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase.log(AuditLogableBase.java:437) >> [dal.jar:] >> at >> org.ovirt.engine.core.bll.CommandBase.logCommand(CommandBase.java:1208) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1175) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:318) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:332) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:534) >> [bll.jar:] >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> [rt.jar:1.7.0_17] >> >> >> 2013-05-02 20:02:10,407 ERROR >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase] >> (DefaultQuartzScheduler_Worker-7) [4b3a50f7] Error during log command: >> org.ovirt.engine.core.bll.SetNonOperationalVdsCommand. Exception >> java.lang.NullPointerException: java.lang.NullPointerException >> at >> org.ovirt.engine.core.utils.cache.CacheManager.getTimeoutBaseCache(CacheManager.java:13) >> [utils.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.TimeoutBase.getLegal(TimeoutBase.java:51) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:809) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:803) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:799) >> [dal.jar:] >> at >> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase.log(AuditLogableBase.java:437) >> [dal.jar:] >> at >> org.ovirt.engine.core.bll.CommandBase.logCommand(CommandBase.java:1208) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1175) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:318) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:332) >> [bll.jar:] >> at >> org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:534) >> [bll.jar:] >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> [rt.jar:1.7.0_17] >> _______________________________________________ >> Engine-devel mailing list >> Engine-devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/engine-devel >> > _______________________________________________ Engine-devel mailing list Engine-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel

----- Original Message ----- > From: "Moti Asayag" <masayag(a)redhat.com&gt; > To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; > Cc: "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt;, "engine-devel" <engine-devel(a)ovirt.org&gt; > Sent: Sunday, May 26, 2013 11:35:40 AM > Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine > > On 05/03/2013 07:23 AM, Alon Bar-Lev wrote: >> >> Hi, >> >> Thanks... no I did not follow. >> >> If -P setup is required then the Makefile should have been changed, else >> our production and rpms are broken now! Well... looking at the pom.xml, it >> looks like the jboss standalone is configured with -P setup is used, which >> is yet another hack introduced to developers... As they do not run our >> service, and suffer from lack of proper environment and configuration >> settings. >> >> My work[1] is exactly to address this one, to eliminate the need for >> hacking the product and use our production startup sequence and >> installation. At ./packaging/services/ovirt-engine.xml.in we already have >> the infinispan settings. >> >> So still need your help. >> Thanks, >> Alon > > I've just started facing the same issue. > Also noticed this in the server.log: > > JBAS014775: New missing/unsatisfied dependencies: > service jboss.mbean.server (missing) dependents: [service > jboss.infinispan.ovirt-engine.config] > > It seems that the generate ovirt-engine.xml under [1] replaces the > infinispan:1.1 version as noted on [2] with infinispan:1.2. I really don't understand the above statement? who/which component have 1.2?

> Is there any version analysing logic which replaces the template for > what seems to be a static part? It is not static[3], it generated based on configuration. If it works with 1.2 then whoever introduced this new dependency should have taken care the production part of the product. BTW: also the old hack of jboss backend/manager/conf/standalone.xml uses 1.1... > [1] var/tmp/ovirt-engine/config/ovirt-engine.xml > [2] share/ovirt-engine/services/ovirt-engine.xml.in [3] packaging/services/ovirt-engine.xml.in >> >> [1] https://github.com/alonbl/ovirt-engine/blob/otopi/README.developer >> >> ----- Original Message ----- >>> From: "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt; >>> To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >>> Cc: "engine-devel" <engine-devel(a)ovirt.org&gt; >>> Sent: Friday, May 3, 2013 7:10:37 AM >>> Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine >>> >>> Hi Alon, >>> I might check this later on today. >>> Did you follow Kublin's email about introducing infinispan? he sent it to >>> engine-devel (you're supposed during the build to perform -P setup) >>> >>> Yair >>> >>> >>> ----- Original Message ----- >>>> From: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >>>> To: "engine-devel" <engine-devel(a)ovirt.org&gt; >>>> Sent: Thursday, May 2, 2013 11:11:03 PM >>>> Subject: [Engine-devel] Error looking up infinispan/ovirt-engine >>>> >>>> Hello, >>>> >>>> I get these (lots of these) using latest master... anyone knows what was >>>> changed? >>>> >>>> At server.log I see: >>>> --- >>>> 2013-05-02 19:58:08,046 INFO [org.jboss.as.clustering.infinispan] >>>> (ServerService Thread Pool -- 21) JBAS010280: Activating Infinispan >>>> subsystem. >>>> <snip> >>>> 2013-05-02 19:58:10,155 INFO [org.jboss.as.controller] (Controller Boot >>>> Thread) JBAS014774: Service status report >>>> JBAS014775: New missing/unsatisfied dependencies: >>>> service jboss.mbean.server (missing) dependents: [service >>>> jboss.infinispan.ovirt-engine.config] >>>> >>>> --- >>>> >>>> Thanks, >>>> Alon >>>> >>>> --- >>>> >>>> 2013-05-02 20:02:10,012 ERROR >>>> [org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy] >>>> (DefaultQuartzScheduler_Worker-7) [4b3a50f7] Failed to lookup resource >>>> type: >>>> CACHE_CONTAINER. JNDI name: java:jboss/infinispan/ovirt-engine: >>>> javax.naming.NameNotFoundException: Error looking up >>>> infinispan/ovirt-engine, service service >>>> jboss.naming.context.java.jboss.infinispan.ovirt-engine is not started >>>> at >>>> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126) >>>> at >>>> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) >>>> at >>>> org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) >>>> at >>>> org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123) >>>> at >>>> org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) >>>> at javax.naming.InitialContext.lookup(InitialContext.java:411) >>>> [rt.jar:1.7.0_17] >>>> at >>>> org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy.findBean(EJBUtilsStrategy.java:104) >>>> [utils.jar:] >>>> at >>>> org.ovirt.engine.core.utils.ejb.EjbUtils.findBean(EjbUtils.java:23) >>>> [utils.jar:] >>>> at >>>> org.ovirt.engine.core.utils.cache.CacheManager.getTimeoutBaseCache(CacheManager.java:12) >>>> [utils.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.TimeoutBase.getLegal(TimeoutBase.java:51) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:809) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:803) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:799) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase.log(AuditLogableBase.java:437) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.bll.CommandBase.logCommand(CommandBase.java:1208) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1175) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:318) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:332) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:534) >>>> [bll.jar:] >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>> [rt.jar:1.7.0_17] >>>> >>>> 2013-05-02 20:02:10,059 ERROR >>>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase] >>>> (DefaultQuartzScheduler_Worker-7) [4b3a50f7] Error during log command: >>>> org.ovirt.engine.core.bll.SetNonOperationalVdsCommand. Exception >>>> java.lang.NullPointerException: java.lang.NullPointerException >>>> at >>>> org.ovirt.engine.core.utils.cache.CacheManager.getTimeoutBaseCache(CacheManager.java:13) >>>> [utils.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.TimeoutBase.getLegal(TimeoutBase.java:51) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:809) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:803) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:799) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase.log(AuditLogableBase.java:437) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.bll.CommandBase.logCommand(CommandBase.java:1208) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1175) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:318) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:332) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:534) >>>> [bll.jar:] >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>> [rt.jar:1.7.0_17] >>>> >>>> 2013-05-02 20:02:10,360 ERROR >>>> [org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy] >>>> (DefaultQuartzScheduler_Worker-7) [4b3a50f7] Failed to lookup resource >>>> type: >>>> CACHE_CONTAINER. JNDI name: java:jboss/infinispan/ovirt-engine: >>>> javax.naming.NameNotFoundException: Error looking up >>>> infinispan/ovirt-engine, service service >>>> jboss.naming.context.java.jboss.infinispan.ovirt-engine is not started >>>> at >>>> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126) >>>> at >>>> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) >>>> at >>>> org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) >>>> at >>>> org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123) >>>> at >>>> org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) >>>> at javax.naming.InitialContext.lookup(InitialContext.java:411) >>>> [rt.jar:1.7.0_17] >>>> at >>>> org.ovirt.engine.core.utils.ejb.EJBUtilsStrategy.findBean(EJBUtilsStrategy.java:104) >>>> [utils.jar:] >>>> at >>>> org.ovirt.engine.core.utils.ejb.EjbUtils.findBean(EjbUtils.java:23) >>>> [utils.jar:] >>>> at >>>> org.ovirt.engine.core.utils.cache.CacheManager.getTimeoutBaseCache(CacheManager.java:12) >>>> [utils.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.TimeoutBase.getLegal(TimeoutBase.java:51) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:809) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:803) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:799) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase.log(AuditLogableBase.java:437) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.bll.CommandBase.logCommand(CommandBase.java:1208) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1175) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:318) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:332) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:534) >>>> [bll.jar:] >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>> [rt.jar:1.7.0_17] >>>> >>>> >>>> 2013-05-02 20:02:10,407 ERROR >>>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase] >>>> (DefaultQuartzScheduler_Worker-7) [4b3a50f7] Error during log command: >>>> org.ovirt.engine.core.bll.SetNonOperationalVdsCommand. Exception >>>> java.lang.NullPointerException: java.lang.NullPointerException >>>> at >>>> org.ovirt.engine.core.utils.cache.CacheManager.getTimeoutBaseCache(CacheManager.java:13) >>>> [utils.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.TimeoutBase.getLegal(TimeoutBase.java:51) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:809) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:803) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector.log(AuditLogDirector.java:799) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase.log(AuditLogableBase.java:437) >>>> [dal.jar:] >>>> at >>>> org.ovirt.engine.core.bll.CommandBase.logCommand(CommandBase.java:1208) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1175) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:318) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:332) >>>> [bll.jar:] >>>> at >>>> org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:534) >>>> [bll.jar:] >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>> [rt.jar:1.7.0_17] >>>> _______________________________________________ >>>> Engine-devel mailing list >>>> Engine-devel(a)ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/engine-devel >>>> >>> >> _______________________________________________ >> Engine-devel mailing list >> Engine-devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/engine-devel >> > >

----- Original Message ----- > From: "Moti Asayag" <masayag(a)redhat.com&gt; > To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; > Cc: "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt;, "engine-devel" <engine-devel(a)ovirt.org&gt; > Sent: Sunday, May 26, 2013 12:19:14 PM > Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine > > On 05/26/2013 11:52 AM, Alon Bar-Lev wrote: >> >> >> ----- Original Message ----- >>> From: "Moti Asayag" <masayag(a)redhat.com&gt; >>> To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >>> Cc: "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt;, "engine-devel" >>> <engine-devel(a)ovirt.org&gt; >>> Sent: Sunday, May 26, 2013 11:35:40 AM >>> Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine >>> >>> On 05/03/2013 07:23 AM, Alon Bar-Lev wrote: >>>> >>>> Hi, >>>> >>>> Thanks... no I did not follow. >>>> >>>> If -P setup is required then the Makefile should have been changed, else >>>> our production and rpms are broken now! Well... looking at the pom.xml, >>>> it >>>> looks like the jboss standalone is configured with -P setup is used, >>>> which >>>> is yet another hack introduced to developers... As they do not run our >>>> service, and suffer from lack of proper environment and configuration >>>> settings. >>>> >>>> My work[1] is exactly to address this one, to eliminate the need for >>>> hacking the product and use our production startup sequence and >>>> installation. At ./packaging/services/ovirt-engine.xml.in we already have >>>> the infinispan settings. >>>> >>>> So still need your help. >>>> Thanks, >>>> Alon >>> >>> I've just started facing the same issue. >>> Also noticed this in the server.log: >>> >>> JBAS014775: New missing/unsatisfied dependencies: >>> service jboss.mbean.server (missing) dependents: [service >>> jboss.infinispan.ovirt-engine.config] >>> >>> It seems that the generate ovirt-engine.xml under [1] replaces the >>> infinispan:1.1 version as noted on [2] with infinispan:1.2. >> >> I really don't understand the above statement? who/which component have >> 1.2? >> > > the template ovirt-engine.xml.in contains: > > <subsystem xmlns="urn:jboss:domain:infinispan:** 1.1 **" > default-cache-container="ovirt-engine"> > > vs > > the generated var/tmp/ovirt-engine/config/ovirt-engine.xml which contains: > > <subsystem xmlns="urn:jboss:domain:infinispan:** 1.2 **" > default-cache-container="ovirt-engine"> > > So it used to work with 1.1 (as defined in the template), but the > generated ovirt-engine.xml replaces the version to 1.2 which cause it > not to work. > > So my question is how the engine-service.py decides to generate the > ovirt-engine.xml with "1.2" version, while the template has "1.1" for > infinispan subsystem element ? Hmmmm!!!!! Good catch! I have never thought that it is possible. The template is generated ok with 1.1, after startup jboss re-write its own configuration and change this to 1.2!!!! Juan, is that normal jboss behavior? Editing its own configuration file?

Regards, Alon Bar-Lev

----- Original Message ----- > From: "Juan Hernandez" <jhernand(a)redhat.com&gt; > To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; > Cc: "Moti Asayag" <masayag(a)redhat.com&gt;, "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt;, "engine-devel" > <engine-devel(a)ovirt.org&gt; > Sent: Monday, May 27, 2013 10:58:43 AM > Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine > > On 05/26/2013 12:09 PM, Alon Bar-Lev wrote: >> >> >> ----- Original Message ----- >>> From: "Moti Asayag" <masayag(a)redhat.com&gt; >>> To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >>> Cc: "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt;, "engine-devel" >>> <engine-devel(a)ovirt.org&gt; >>> Sent: Sunday, May 26, 2013 12:19:14 PM >>> Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine >>> >>> On 05/26/2013 11:52 AM, Alon Bar-Lev wrote: >>>> >>>> >>>> ----- Original Message ----- >>>>> From: "Moti Asayag" <masayag(a)redhat.com&gt; >>>>> To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >>>>> Cc: "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt;, "engine-devel" >>>>> <engine-devel(a)ovirt.org&gt; >>>>> Sent: Sunday, May 26, 2013 11:35:40 AM >>>>> Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine >>>>> >>>>> On 05/03/2013 07:23 AM, Alon Bar-Lev wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> Thanks... no I did not follow. >>>>>> >>>>>> If -P setup is required then the Makefile should have been changed, >>>>>> else >>>>>> our production and rpms are broken now! Well... looking at the pom.xml, >>>>>> it >>>>>> looks like the jboss standalone is configured with -P setup is used, >>>>>> which >>>>>> is yet another hack introduced to developers... As they do not run our >>>>>> service, and suffer from lack of proper environment and configuration >>>>>> settings. >>>>>> >>>>>> My work[1] is exactly to address this one, to eliminate the need for >>>>>> hacking the product and use our production startup sequence and >>>>>> installation. At ./packaging/services/ovirt-engine.xml.in we already >>>>>> have >>>>>> the infinispan settings. >>>>>> >>>>>> So still need your help. >>>>>> Thanks, >>>>>> Alon >>>>> >>>>> I've just started facing the same issue. >>>>> Also noticed this in the server.log: >>>>> >>>>> JBAS014775: New missing/unsatisfied dependencies: >>>>> service jboss.mbean.server (missing) dependents: [service >>>>> jboss.infinispan.ovirt-engine.config] >>>>> >>>>> It seems that the generate ovirt-engine.xml under [1] replaces the >>>>> infinispan:1.1 version as noted on [2] with infinispan:1.2. >>>> >>>> I really don't understand the above statement? who/which component have >>>> 1.2? >>>> >>> >>> the template ovirt-engine.xml.in contains: >>> >>> <subsystem xmlns="urn:jboss:domain:infinispan:** 1.1 **" >>> default-cache-container="ovirt-engine"> >>> >>> vs >>> >>> the generated var/tmp/ovirt-engine/config/ovirt-engine.xml which contains: >>> >>> <subsystem xmlns="urn:jboss:domain:infinispan:** 1.2 **" >>> default-cache-container="ovirt-engine"> >>> >>> So it used to work with 1.1 (as defined in the template), but the >>> generated ovirt-engine.xml replaces the version to 1.2 which cause it >>> not to work. >>> >>> So my question is how the engine-service.py decides to generate the >>> ovirt-engine.xml with "1.2" version, while the template has "1.1" for >>> infinispan subsystem element ? >> >> Hmmmm!!!!! Good catch! I have never thought that it is possible. >> >> The template is generated ok with 1.1, after startup jboss re-write its own >> configuration and change this to 1.2!!!! >> >> Juan, is that normal jboss behavior? Editing its own configuration file? >> > > Yes, it is normal. Hi, What do you suggest to do if application requires specific component version and jboss enforce a different version?

If I understand correctly two versions of jboss can enforce a different version of components. Thanks, Alon

----- Original Message ----- > From: "Juan Hernandez" <jhernand(a)redhat.com&gt; > To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; > Cc: "Moti Asayag" <masayag(a)redhat.com&gt;, "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt;, "engine-devel" > <engine-devel(a)ovirt.org&gt; > Sent: Monday, May 27, 2013 11:13:15 AM > Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine > > On 05/27/2013 10:01 AM, Alon Bar-Lev wrote: >> >> >> ----- Original Message ----- >>> From: "Juan Hernandez" <jhernand(a)redhat.com&gt; >>> To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >>> Cc: "Moti Asayag" <masayag(a)redhat.com&gt;, "Yair Zaslavsky" >>> <yzaslavs(a)redhat.com&gt;, "engine-devel" >>> <engine-devel(a)ovirt.org&gt; >>> Sent: Monday, May 27, 2013 10:58:43 AM >>> Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine >>> >>> On 05/26/2013 12:09 PM, Alon Bar-Lev wrote: >>>> >>>> >>>> ----- Original Message ----- >>>>> From: "Moti Asayag" <masayag(a)redhat.com&gt; >>>>> To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >>>>> Cc: "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt;, "engine-devel" >>>>> <engine-devel(a)ovirt.org&gt; >>>>> Sent: Sunday, May 26, 2013 12:19:14 PM >>>>> Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine >>>>> >>>>> On 05/26/2013 11:52 AM, Alon Bar-Lev wrote: >>>>>> >>>>>> >>>>>> ----- Original Message ----- >>>>>>> From: "Moti Asayag" <masayag(a)redhat.com&gt; >>>>>>> To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >>>>>>> Cc: "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt;, "engine-devel" >>>>>>> <engine-devel(a)ovirt.org&gt; >>>>>>> Sent: Sunday, May 26, 2013 11:35:40 AM >>>>>>> Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine >>>>>>> >>>>>>> On 05/03/2013 07:23 AM, Alon Bar-Lev wrote: >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Thanks... no I did not follow. >>>>>>>> >>>>>>>> If -P setup is required then the Makefile should have been changed, >>>>>>>> else >>>>>>>> our production and rpms are broken now! Well... looking at the >>>>>>>> pom.xml, >>>>>>>> it >>>>>>>> looks like the jboss standalone is configured with -P setup is used, >>>>>>>> which >>>>>>>> is yet another hack introduced to developers... As they do not run >>>>>>>> our >>>>>>>> service, and suffer from lack of proper environment and configuration >>>>>>>> settings. >>>>>>>> >>>>>>>> My work[1] is exactly to address this one, to eliminate the need for >>>>>>>> hacking the product and use our production startup sequence and >>>>>>>> installation. At ./packaging/services/ovirt-engine.xml.in we already >>>>>>>> have >>>>>>>> the infinispan settings. >>>>>>>> >>>>>>>> So still need your help. >>>>>>>> Thanks, >>>>>>>> Alon >>>>>>> >>>>>>> I've just started facing the same issue. >>>>>>> Also noticed this in the server.log: >>>>>>> >>>>>>> JBAS014775: New missing/unsatisfied dependencies: >>>>>>> service jboss.mbean.server (missing) dependents: [service >>>>>>> jboss.infinispan.ovirt-engine.config] >>>>>>> >>>>>>> It seems that the generate ovirt-engine.xml under [1] replaces the >>>>>>> infinispan:1.1 version as noted on [2] with infinispan:1.2. >>>>>> >>>>>> I really don't understand the above statement? who/which component have >>>>>> 1.2? >>>>>> >>>>> >>>>> the template ovirt-engine.xml.in contains: >>>>> >>>>> <subsystem xmlns="urn:jboss:domain:infinispan:** 1.1 **" >>>>> default-cache-container="ovirt-engine"> >>>>> >>>>> vs >>>>> >>>>> the generated var/tmp/ovirt-engine/config/ovirt-engine.xml which >>>>> contains: >>>>> >>>>> <subsystem xmlns="urn:jboss:domain:infinispan:** 1.2 **" >>>>> default-cache-container="ovirt-engine"> >>>>> >>>>> So it used to work with 1.1 (as defined in the template), but the >>>>> generated ovirt-engine.xml replaces the version to 1.2 which cause it >>>>> not to work. >>>>> >>>>> So my question is how the engine-service.py decides to generate the >>>>> ovirt-engine.xml with "1.2" version, while the template has "1.1" for >>>>> infinispan subsystem element ? >>>> >>>> Hmmmm!!!!! Good catch! I have never thought that it is possible. >>>> >>>> The template is generated ok with 1.1, after startup jboss re-write its >>>> own >>>> configuration and change this to 1.2!!!! >>>> >>>> Juan, is that normal jboss behavior? Editing its own configuration file? >>>> >>> >>> Yes, it is normal. >> >> Hi, >> >> What do you suggest to do if application requires specific component >> version and jboss enforce a different version? >> > > Change the application to use the version enforced by JBoss. > >> If I understand correctly two versions of jboss can enforce a different >> version of components. So I ask again ^^^^. If application should run under two versions of jboss which enforce two versions of a component, how can application cope?

>> >> Thanks, >> Alon >> > > > -- > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta > 3ºD, 28016 Madrid, Spain > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. >

From: "Juan Hernandez" <jhernand(a)redhat.com&gt; To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; Cc: "Moti Asayag" <masayag(a)redhat.com&gt;, "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt;, "engine-devel" <engine-devel(a)ovirt.org&gt; Sent: Monday, May 27, 2013 11:20:56 AM Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine On 05/27/2013 10:19 AM, Alon Bar-Lev wrote: > > > ----- Original Message ----- >> From: "Juan Hernandez" <jhernand(a)redhat.com&gt; >> To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >> Cc: "Moti Asayag" <masayag(a)redhat.com&gt;, "Yair Zaslavsky" >> <yzaslavs(a)redhat.com&gt;, "engine-devel" >> <engine-devel(a)ovirt.org&gt; >> Sent: Monday, May 27, 2013 11:13:15 AM >> Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine >> >> On 05/27/2013 10:01 AM, Alon Bar-Lev wrote: >>> >>> >>> ----- Original Message ----- >>>> From: "Juan Hernandez" <jhernand(a)redhat.com&gt; >>>> To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >>>> Cc: "Moti Asayag" <masayag(a)redhat.com&gt;, "Yair Zaslavsky" >>>> <yzaslavs(a)redhat.com&gt;, "engine-devel" >>>> <engine-devel(a)ovirt.org&gt; >>>> Sent: Monday, May 27, 2013 10:58:43 AM >>>> Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine >>>> >>>> On 05/26/2013 12:09 PM, Alon Bar-Lev wrote: >>>>> >>>>> >>>>> ----- Original Message ----- >>>>>> From: "Moti Asayag" <masayag(a)redhat.com&gt; >>>>>> To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >>>>>> Cc: "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt;, "engine-devel" >>>>>> <engine-devel(a)ovirt.org&gt; >>>>>> Sent: Sunday, May 26, 2013 12:19:14 PM >>>>>> Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine >>>>>> >>>>>> On 05/26/2013 11:52 AM, Alon Bar-Lev wrote: >>>>>>> >>>>>>> >>>>>>> ----- Original Message ----- >>>>>>>> From: "Moti Asayag" <masayag(a)redhat.com&gt; >>>>>>>> To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; >>>>>>>> Cc: "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt;, "engine-devel" >>>>>>>> <engine-devel(a)ovirt.org&gt; >>>>>>>> Sent: Sunday, May 26, 2013 11:35:40 AM >>>>>>>> Subject: Re: [Engine-devel] Error looking up infinispan/ovirt-engine >>>>>>>> >>>>>>>> On 05/03/2013 07:23 AM, Alon Bar-Lev wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> Thanks... no I did not follow. >>>>>>>>> >>>>>>>>> If -P setup is required then the Makefile should have been changed, >>>>>>>>> else >>>>>>>>> our production and rpms are broken now! Well... looking at the >>>>>>>>> pom.xml, >>>>>>>>> it >>>>>>>>> looks like the jboss standalone is configured with -P setup is >>>>>>>>> used, >>>>>>>>> which >>>>>>>>> is yet another hack introduced to developers... As they do not run >>>>>>>>> our >>>>>>>>> service, and suffer from lack of proper environment and >>>>>>>>> configuration >>>>>>>>> settings. >>>>>>>>> >>>>>>>>> My work[1] is exactly to address this one, to eliminate the need >>>>>>>>> for >>>>>>>>> hacking the product and use our production startup sequence and >>>>>>>>> installation. At ./packaging/services/ovirt-engine.xml.in we >>>>>>>>> already >>>>>>>>> have >>>>>>>>> the infinispan settings. >>>>>>>>> >>>>>>>>> So still need your help. >>>>>>>>> Thanks, >>>>>>>>> Alon >>>>>>>> >>>>>>>> I've just started facing the same issue. >>>>>>>> Also noticed this in the server.log: >>>>>>>> >>>>>>>> JBAS014775: New missing/unsatisfied dependencies: >>>>>>>> service jboss.mbean.server (missing) dependents: [service >>>>>>>> jboss.infinispan.ovirt-engine.config] >>>>>>>> >>>>>>>> It seems that the generate ovirt-engine.xml under [1] replaces the >>>>>>>> infinispan:1.1 version as noted on [2] with infinispan:1.2. >>>>>>> >>>>>>> I really don't understand the above statement? who/which component >>>>>>> have >>>>>>> 1.2? >>>>>>> >>>>>> >>>>>> the template ovirt-engine.xml.in contains: >>>>>> >>>>>> <subsystem xmlns="urn:jboss:domain:infinispan:** 1.1 **" >>>>>> default-cache-container="ovirt-engine"> >>>>>> >>>>>> vs >>>>>> >>>>>> the generated var/tmp/ovirt-engine/config/ovirt-engine.xml which >>>>>> contains: >>>>>> >>>>>> <subsystem xmlns="urn:jboss:domain:infinispan:** 1.2 **" >>>>>> default-cache-container="ovirt-engine"> >>>>>> >>>>>> So it used to work with 1.1 (as defined in the template), but the >>>>>> generated ovirt-engine.xml replaces the version to 1.2 which cause it >>>>>> not to work. >>>>>> >>>>>> So my question is how the engine-service.py decides to generate the >>>>>> ovirt-engine.xml with "1.2" version, while the template has "1.1" for >>>>>> infinispan subsystem element ? >>>>> >>>>> Hmmmm!!!!! Good catch! I have never thought that it is possible. >>>>> >>>>> The template is generated ok with 1.1, after startup jboss re-write its >>>>> own >>>>> configuration and change this to 1.2!!!! >>>>> >>>>> Juan, is that normal jboss behavior? Editing its own configuration >>>>> file? >>>>> >>>> >>>> Yes, it is normal. >>> >>> Hi, >>> >>> What do you suggest to do if application requires specific component >>> version and jboss enforce a different version? >>> >> >> Change the application to use the version enforced by JBoss. > >> >>> If I understand correctly two versions of jboss can enforce a different >>> version of components. > > So I ask again ^^^^. > > If application should run under two versions of jboss which enforce two > versions of a component, how can application cope? > I don't know.