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:<br><br>org.infinispan.CacheException: Unable to invoke method public void org.infinispan.jmx.CacheJmxRegistration.start() on object of type CacheJmxRegistration<br>
��� at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:238)<br>��� at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:899)<br>��� at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:649)<br>
��� at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:638)<br>��� at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:541)<br>��� at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:191)<br>
��� at org.infinispan.CacheImpl.start(CacheImpl.java:519)<br>��� at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:683)<br>��� at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:646)<br>
��� at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:546)<br>��� at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:518)<br>��� at org.infinispan.query.config.DefaultCacheInheritancePreventedTest.verifyIndexEnabledCorrectly(DefaultCacheInheritancePreventedTest.java:63)<br>
Caused by: org.infinispan.jmx.JmxDomainConflictException: Domain already registered org.infinispan<br>��� at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:73)<br>��� at org.infinispan.jmx.CacheJmxRegistration.updateDomain(CacheJmxRegistration.java:154)<br>
��� at org.infinispan.jmx.CacheJmxRegistration.buildRegistrar(CacheJmxRegistration.java:146)<br>��� at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:59)<br>��� at org.infinispan.jmx.CacheJmxRegistration.start(CacheJmxRegistration.java:84)<br>
��� at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>��� at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)<br>��� at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)<br>
��� at java.lang.reflect.Method.invoke(Method.java:601)<br>��� at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:236)<br>��� ... 31 more<br><br><br><br><div class="gmail_quote">On Mon, Sep 17, 2012 at 3:36 PM, Dan Berindei <span dir="ltr"><<a href="mailto:dan.berindei@gmail.com" target="_blank">dan.berindei@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sanne, you should know more about your laptop than we do :)<br><br>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...<br>
<br>Cheers<span class="HOEnZb"><font color="#888888"><br>Dan</font></span><div class="HOEnZb"><div class="h5"><br><br><br><div class="gmail_quote">On Mon, Sep 17, 2012 at 1:32 PM, Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne@infinispan.org" target="_blank">sanne@infinispan.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm again in the situation of not being able to run the testsuite: it<br>
hangs while running the core testsuite.<br>
<br>
Anyone has a clue of why it's always my laptop not being able to complete it?<br>
<br>
Cheers,<br>
Sanne<br>
<div><div><br>
On 17 September 2012 11:35, Dan Berindei <<a href="mailto:dan.berindei@gmail.com" target="_blank">dan.berindei@gmail.com</a>> wrote:<br>
> Galder, I'm not sure what's happening in CloudBees, I'll take a look.<br>
> However, I don't think logging is set up properly in any module except for<br>
> core (which has a log4j.xml file in its test jar). Could we add a<br>
> -Dlog4j.configuration argument to the maven command line for all the<br>
> modules?<br>
><br>
> At least some of the failures in run #816 seem to be related to the latest<br>
> JMX changes:<br>
> <a href="https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/org.infinispan$infinispan-server-core/816/testReport/org.infinispan.server.core/MarshallingTest/setUp/#" target="_blank">https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/org.infinispan$infinispan-server-core/816/testReport/org.infinispan.server.core/MarshallingTest/setUp/#</a><br>
><br>
> Cheers<br>
> Dan<br>
><br>
><br>
><br>
> On Mon, Sep 17, 2012 at 11:57 AM, Galder Zamarre�o <<a href="mailto:galder@redhat.com" target="_blank">galder@redhat.com</a>><br>
> wrote:<br>
>><br>
>> It's a bit of a mess:<br>
>> <a href="https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/" target="_blank">https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/</a><br>
>><br>
>> Ever since we integrated ISPN-1424 we haven't had a run that's actually<br>
>> finished.<br>
>><br>
>> I'm currently looking into the issue in<br>
>> <a href="https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/804/console" target="_blank">https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/804/console</a><br>
>> which is stopping the Hot Rod client testsuite from running.<br>
>><br>
>> Could you please have a look to see what's up with the other runs? i.e. I<br>
>> see some issues with JDBC:<br>
>><br>
>> <a href="https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/816/console" target="_blank">https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/816/console</a><br>
>><br>
>> Cheers,<br>
>> --<br>
>> Galder Zamarre�o<br>
>> <a href="mailto:galder@redhat.com" target="_blank">galder@redhat.com</a><br>
>> <a href="http://twitter.com/galderz" target="_blank">twitter.com/galderz</a><br>
>><br>
>> Project Lead, Escalante<br>
>> <a href="http://escalante.io" target="_blank">http://escalante.io</a><br>
>><br>
>> Engineer, Infinispan<br>
>> <a href="http://infinispan.org" target="_blank">http://infinispan.org</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> infinispan-dev mailing list<br>
>> <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a></div></div></blockquote></div><br>
</div></div></blockquote></div><br>