Galder, I'm not sure what's happening in CloudBees, I'll take a look. However, I don't think logging is set up properly in any module except for core (which has a log4j.xml file in its test jar). Could we add a -Dlog4j.configuration argument to the maven command line for all the modules? At least some of the failures in run #816 seem to be related to the latest JMX changes: https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/org.in... Cheers Dan On Mon, Sep 17, 2012 at 11:57 AM, Galder Zamarreño <galder(a)redhat.com&gt; wrote: > > It's a bit of a mess: > https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/ > > Ever since we integrated ISPN-1424 we haven't had a run that's actually > finished. > > I'm currently looking into the issue in > https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/804/co... > which is stopping the Hot Rod client testsuite from running. > > Could you please have a look to see what's up with the other runs? i.e. I > see some issues with JDBC: > > https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/816/co... > > Cheers, > -- > Galder Zamarreño > galder(a)redhat.com > twitter.com/galderz > > Project Lead, Escalante > http://escalante.io > > Engineer, Infinispan > http://infinispan.org > > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

Sanne, you should know more about your laptop than we do :) I used to always run Maven with the debug agent enabled in order to find and fix this kind of failures, but not anymore. I had one particularly weird issue with core tests failing randomly, and I tracked it down (after a few weeks of on-and-off investigation) to the debug agent: with debugging enabled, it sometimes took > 10 seconds to start a new thread in an existing thread pool, which would break almost any test. After trying to trace it and debug it in every way I could think of, I removed the debug agent from the command line and my machine got back to normal... Cheers Dan On Mon, Sep 17, 2012 at 1:32 PM, Sanne Grinovero <sanne(a)infinispan.org&gt;wrote: > I'm again in the situation of not being able to run the testsuite: it > hangs while running the core testsuite. > > Anyone has a clue of why it's always my laptop not being able to complete > it? > > Cheers, > Sanne > > On 17 September 2012 11:35, Dan Berindei <dan.berindei(a)gmail.com&gt; wrote: > > Galder, I'm not sure what's happening in CloudBees, I'll take a look. > > However, I don't think logging is set up properly in any module except > for > > core (which has a log4j.xml file in its test jar). Could we add a > > -Dlog4j.configuration argument to the maven command line for all the > > modules? > > > > At least some of the failures in run #816 seem to be related to the > latest > > JMX changes: > > > https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/org.in... > > > > Cheers > > Dan > > > > > > > > On Mon, Sep 17, 2012 at 11:57 AM, Galder Zamarreño <galder(a)redhat.com&gt; > > wrote: > >> > >> It's a bit of a mess: > >> https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/ > >> > >> Ever since we integrated ISPN-1424 we haven't had a run that's actually > >> finished. > >> > >> I'm currently looking into the issue in > >> > https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/804/co... > >> which is stopping the Hot Rod client testsuite from running. > >> > >> Could you please have a look to see what's up with the other runs? > i.e. I > >> see some issues with JDBC: > >> > >> > https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/816/co... > >> > >> Cheers, > >> -- > >> Galder Zamarreño > >> galder(a)redhat.com > >> twitter.com/galderz > >> > >> Project Lead, Escalante > >> http://escalante.io > >> > >> Engineer, Infinispan > >> http://infinispan.org > >> > >> > >> _______________________________________________ > >> infinispan-dev mailing list > >> infinispan-dev(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/infinispan-dev > > > > > > > > _______________________________________________ > > infinispan-dev mailing list > > infinispan-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/infinispan-dev > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev >

I'm chasing that same issue. It's most probably caused by some of my config changes, although a git-bisect would be ideal Tristan On 09/17/2012 03:12 PM, Dan Berindei wrote: > BTW, after updating this morning, query and hotrod-client are not finishing properly on my machine either. I'm seeing lots instances of this error: > > org.infinispan.CacheException: Unable to invoke method public void org.infinispan.jmx.CacheJmxRegistration.start() on object of type CacheJmxRegistration > at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:238) > at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:899) > at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:649) > at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:638) > at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:541) > at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:191) > at org.infinispan.CacheImpl.start(CacheImpl.java:519) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:683) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:646) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:546) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:518) > at org.infinispan.query.config.DefaultCacheInheritancePreventedTest.verifyIndexEnabledCorrectly(DefaultCacheInheritancePreventedTest.java:63) > Caused by: org.infinispan.jmx.JmxDomainConflictException: Domain already registered org.infinispan > at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:73) > at org.infinispan.jmx.CacheJmxRegistration.updateDomain(CacheJmxRegistration.java:154) > at org.infinispan.jmx.CacheJmxRegistration.buildRegistrar(CacheJmxRegistration.java:146) > at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:59) > at org.infinispan.jmx.CacheJmxRegistration.start(CacheJmxRegistration.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:236) > ... 31 more > > > > On Mon, Sep 17, 2012 at 3:36 PM, Dan Berindei <dan.berindei(a)gmail.com&gt; wrote: > Sanne, you should know more about your laptop than we do :) > > I used to always run Maven with the debug agent enabled in order to find and fix this kind of failures, but not anymore. I had one particularly weird issue with core tests failing randomly, and I tracked it down (after a few weeks of on-and-off investigation) to the debug agent: with debugging enabled, it sometimes took > 10 seconds to start a new thread in an existing thread pool, which would break almost any test. After trying to trace it and debug it in every way I could think of, I removed the debug agent from the command line and my machine got back to normal... > > Cheers > Dan > > > > On Mon, Sep 17, 2012 at 1:32 PM, Sanne Grinovero <sanne(a)infinispan.org&gt; wrote: > I'm again in the situation of not being able to run the testsuite: it > hangs while running the core testsuite. > > Anyone has a clue of why it's always my laptop not being able to complete it? > > Cheers, > Sanne > > On 17 September 2012 11:35, Dan Berindei <dan.berindei(a)gmail.com&gt; wrote: > > Galder, I'm not sure what's happening in CloudBees, I'll take a look. > > However, I don't think logging is set up properly in any module except for > > core (which has a log4j.xml file in its test jar). Could we add a > > -Dlog4j.configuration argument to the maven command line for all the > > modules? > > > > At least some of the failures in run #816 seem to be related to the latest > > JMX changes: > > https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/org.in... > > > > Cheers > > Dan > > > > > > > > On Mon, Sep 17, 2012 at 11:57 AM, Galder Zamarreño <galder(a)redhat.com&gt; > > wrote: > >> > >> It's a bit of a mess: > >> https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/ > >> > >> Ever since we integrated ISPN-1424 we haven't had a run that's actually > >> finished. > >> > >> I'm currently looking into the issue in > >> https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/804/co... > >> which is stopping the Hot Rod client testsuite from running. > >> > >> Could you please have a look to see what's up with the other runs? i.e. I > >> see some issues with JDBC: > >> > >> https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/816/co... > >> > >> Cheers, > >> -- > >> Galder Zamarreño > >> galder(a)redhat.com > >> twitter.com/galderz > >> > >> Project Lead, Escalante > >> http://escalante.io > >> > >> Engineer, Infinispan > >> http://infinispan.org > >> > >> > >> _______________________________________________ > >> infinispan-dev mailing list > >> infinispan-dev(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/infinispan-dev > > > > > > > > _______________________________________________ > > infinispan-dev mailing list > > infinispan-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/infinispan-dev > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev > > > > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

The cause of this is often using new DefaultCacheManager() in the test suite instead of TestCacheManagerFactory to create a cache manager. On 17 Sep 2012, at 14:16, Manik Surtani <manik(a)jboss.org&gt; wrote: > That might be something I missed - Galder merged in a couple of my PRs this morning. > > On 17 Sep 2012, at 14:15, Tristan Tarrant <ttarrant(a)redhat.com&gt; wrote: > >> I'm chasing that same issue. It's most probably caused by some of my config changes, although a git-bisect would be ideal >> >> Tristan >> >> On 09/17/2012 03:12 PM, Dan Berindei wrote: >>> BTW, after updating this morning, query and hotrod-client are not finishing properly on my machine either. I'm seeing lots instances of this error: >>> >>> org.infinispan.CacheException: Unable to invoke method public void org.infinispan.jmx.CacheJmxRegistration.start() on object of type CacheJmxRegistration >>> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:238) >>> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:899) >>> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:649) >>> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:638) >>> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:541) >>> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:191) >>> at org.infinispan.CacheImpl.start(CacheImpl.java:519) >>> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:683) >>> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:646) >>> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:546) >>> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:518) >>> at org.infinispan.query.config.DefaultCacheInheritancePreventedTest.verifyIndexEnabledCorrectly(DefaultCacheInheritancePreventedTest.java:63) >>> Caused by: org.infinispan.jmx.JmxDomainConflictException: Domain already registered org.infinispan >>> at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:73) >>> at org.infinispan.jmx.CacheJmxRegistration.updateDomain(CacheJmxRegistration.java:154) >>> at org.infinispan.jmx.CacheJmxRegistration.buildRegistrar(CacheJmxRegistration.java:146) >>> at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:59) >>> at org.infinispan.jmx.CacheJmxRegistration.start(CacheJmxRegistration.java:84) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>> at java.lang.reflect.Method.invoke(Method.java:601) >>> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:236) >>> ... 31 more >>> >>> >>> >>> On Mon, Sep 17, 2012 at 3:36 PM, Dan Berindei <dan.berindei(a)gmail.com&gt; wrote: >>> Sanne, you should know more about your laptop than we do :) >>> >>> I used to always run Maven with the debug agent enabled in order to find and fix this kind of failures, but not anymore. I had one particularly weird issue with core tests failing randomly, and I tracked it down (after a few weeks of on-and-off investigation) to the debug agent: with debugging enabled, it sometimes took > 10 seconds to start a new thread in an existing thread pool, which would break almost any test. After trying to trace it and debug it in every way I could think of, I removed the debug agent from the command line and my machine got back to normal... >>> >>> Cheers >>> Dan >>> >>> >>> >>> On Mon, Sep 17, 2012 at 1:32 PM, Sanne Grinovero <sanne(a)infinispan.org&gt; wrote: >>> I'm again in the situation of not being able to run the testsuite: it >>> hangs while running the core testsuite. >>> >>> Anyone has a clue of why it's always my laptop not being able to complete it? >>> >>> Cheers, >>> Sanne >>> >>> On 17 September 2012 11:35, Dan Berindei <dan.berindei(a)gmail.com&gt; wrote: >>> > Galder, I'm not sure what's happening in CloudBees, I'll take a look. >>> > However, I don't think logging is set up properly in any module except for >>> > core (which has a log4j.xml file in its test jar). Could we add a >>> > -Dlog4j.configuration argument to the maven command line for all the >>> > modules? >>> > >>> > At least some of the failures in run #816 seem to be related to the latest >>> > JMX changes: >>> > https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/org.in... >>> > >>> > Cheers >>> > Dan >>> > >>> > >>> > >>> > On Mon, Sep 17, 2012 at 11:57 AM, Galder Zamarreño <galder(a)redhat.com&gt; >>> > wrote: >>> >> >>> >> It's a bit of a mess: >>> >> https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/ >>> >> >>> >> Ever since we integrated ISPN-1424 we haven't had a run that's actually >>> >> finished. >>> >> >>> >> I'm currently looking into the issue in >>> >> https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/804/co... >>> >> which is stopping the Hot Rod client testsuite from running. >>> >> >>> >> Could you please have a look to see what's up with the other runs? i.e. I >>> >> see some issues with JDBC: >>> >> >>> >> https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/816/co... >>> >> >>> >> Cheers, >>> >> -- >>> >> Galder Zamarreño >>> >> galder(a)redhat.com >>> >> twitter.com/galderz >>> >> >>> >> Project Lead, Escalante >>> >> http://escalante.io >>> >> >>> >> Engineer, Infinispan >>> >> http://infinispan.org >>> >> >>> >> >>> >> _______________________________________________ >>> >> infinispan-dev mailing list >>> >> infinispan-dev(a)lists.jboss.org >>> >> https://lists.jboss.org/mailman/listinfo/infinispan-dev >>> > >>> > >>> > >>> > _______________________________________________ >>> > infinispan-dev mailing list >>> > infinispan-dev(a)lists.jboss.org >>> > https://lists.jboss.org/mailman/listinfo/infinispan-dev >>> >>> _______________________________________________ >>> infinispan-dev mailing list >>> infinispan-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >>> >>> >>> >>> >>> _______________________________________________ >>> infinispan-dev mailing list >>> >>> infinispan-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >> >> _______________________________________________ >> infinispan-dev mailing list >> infinispan-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/infinispan-dev > > -- > Manik Surtani > manik(a)jboss.org > twitter.com/maniksurtani > > Platform Architect, JBoss Data Grid > http://red.ht/data-grid > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Manik Surtani manik(a)jboss.org twitter.com/maniksurtani Platform Architect, JBoss Data Grid http://red.ht/data-grid _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

On 18 Sep 2012, at 16:42, Galder Zamarreño wrote: > The JMX issues should be sorted now. Thanks Galder! > > There were two issues here: one was the one manik said, and the other was the fact that we were leaking cache mbeans, and it would result in domain conflicts. > > Both issues solved now. There still are some JMX relate failures in CDI, mind taking a look? https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/826/or...