[JBoss JIRA] (ISPN-4389) Tests for suppressing state transfer with jmx fail
by William Burns (JIRA)
William Burns created ISPN-4389:
-----------------------------------
Summary: Tests for suppressing state transfer with jmx fail
Key: ISPN-4389
URL: https://issues.jboss.org/browse/ISPN-4389
Project: Infinispan
Issue Type: Bug
Components: Server, State Transfer
Reporter: William Burns
Assignee: William Burns
Fix For: 7.0.0.Alpha5
http://ci.infinispan.org/viewLog.html?buildId=8736&buildTypeId=bt8&tab=bu...
{code}
12:00:43,839 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.infinispan.clustered.default: org.jboss.msc.service.StartException in service jboss.infinispan.clustered.default: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_06]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_06]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_06]
Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.InterruptedException on object of type StateTransferManagerImpl
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:170)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:216)
at org.infinispan.CacheImpl.start(CacheImpl.java:696)
at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:574)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:529)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:409)
at org.infinispan.registry.ClusterRegistryImpl.startRegistryCache(ClusterRegistryImpl.java:136)
at org.infinispan.registry.ClusterRegistryImpl.addListener(ClusterRegistryImpl.java:97)
at org.infinispan.query.remote.ProtobufMetadataManager.ensureInit(ProtobufMetadataManager.java:65)
at org.infinispan.query.remote.ProtobufMetadataManager.getSerializationContext(ProtobufMetadataManager.java:132)
at org.infinispan.query.remote.LifecycleManager.cacheStarting(LifecycleManager.java:114)
at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:228)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:214)
at org.infinispan.CacheImpl.start(CacheImpl.java:696)
at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:574)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:529)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:409)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:423)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:89)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:80)
at org.jboss.as.clustering.infinispan.subsystem.SecurityActions$5.run(SecurityActions.java:101)
at org.jboss.as.clustering.infinispan.subsystem.SecurityActions$5.run(SecurityActions.java:98)
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_06]
at org.jboss.as.clustering.infinispan.subsystem.SecurityActions.startCache(SecurityActions.java:109)
at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:78)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
... 3 more
Caused by: org.infinispan.commons.CacheException: Initial state transfer timed out for cache __cluster_registry_cache__ on node2/clustered
at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:209)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_06]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_06]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_06]
at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_06]
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168)
... 33 more
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (ISPN-4317) Optimize server test suite
by Martin Gencur (JIRA)
[ https://issues.jboss.org/browse/ISPN-4317?page=com.atlassian.jira.plugin.... ]
Martin Gencur commented on ISPN-4317:
-------------------------------------
Thanks for this detailed analysis, Jakub!
> Optimize server test suite
> --------------------------
>
> Key: ISPN-4317
> URL: https://issues.jboss.org/browse/ISPN-4317
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite - Server
> Affects Versions: 7.0.0.Alpha4
> Reporter: Martin Gencur
> Assignee: Jakub Markos
>
> The goal is to make the test execution of server test suite shorter and minimize the number of maven profiles so that most of the tests run in a default profile.
> The first thing to do is to minimize the number of server restarts when running the test suite. This will require adding many different cache configurations to the same Infinispan subsystem.
> Also, look for other ways to minimize test execution time.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (ISPN-4388) Server to use a ManagedScheduledExecutorService for ScheduledExecutorServices
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4388?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-4388:
--------------------------------
Description:
We use ScheduledExecutorServices for both the eviction and and replication queues. However we currently wrap these in EmbeddedCacheManagerConfigurationService with regular ManagedThreadPoolExecutorFactories, where as we should have a ManagedScheduledThreadPoolExecutorFactory to wrap this which would produce the proper type.
Without this it prevents configuring any kind of eviction or replication executor in the server.
{code}
08:36:04,570 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-11) MSC00001: Failed to start service jboss.infinispan.default.default: org.jboss.msc.service.StartException in service jboss.infinispan.default.default: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.eviction.impl.EvictionManagerImpl.start() on object of type EvictionManagerImpl
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:170)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:216)
at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699)
at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408)
at org.infinispan.registry.impl.ClusterRegistryImpl.startRegistryCache(ClusterRegistryImpl.java:146)
at org.infinispan.registry.impl.ClusterRegistryImpl.addListener(ClusterRegistryImpl.java:107)
at org.infinispan.query.remote.ProtobufMetadataManager.ensureInit(ProtobufMetadataManager.java:65)
at org.infinispan.query.remote.ProtobufMetadataManager.getSerializationContext(ProtobufMetadataManager.java:132)
at org.infinispan.query.remote.LifecycleManager.cacheStarting(LifecycleManager.java:114)
at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:228)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:214)
at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699)
at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:422)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:89)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:80)
at org.jboss.as.clustering.infinispan.subsystem.SecurityActions$5.run(SecurityActions.java:101)
at org.jboss.as.clustering.infinispan.subsystem.SecurityActions$5.run(SecurityActions.java:98)
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_51]
at org.jboss.as.clustering.infinispan.subsystem.SecurityActions.startCache(SecurityActions.java:109)
at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:78)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
... 3 more
Caused by: java.lang.ClassCastException: org.jboss.as.clustering.concurrent.ManagedExecutorService cannot be cast to java.util.concurrent.ScheduledExecutorService
at org.infinispan.executors.LazyInitializingScheduledExecutorService.initIfNeeded(LazyInitializingScheduledExecutorService.java:40)
at org.infinispan.executors.LazyInitializingScheduledExecutorService.scheduleWithFixedDelay(LazyInitializingScheduledExecutorService.java:146)
at org.infinispan.eviction.impl.EvictionManagerImpl.start(EvictionManagerImpl.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51]
at org.infinispan.
{code}
http://ci.infinispan.org/viewLog.html?buildId=8736&buildTypeId=bt8&tab=bu...
was:
We use ScheduledExecutorServices for both the eviction and and replication queues. However we currently wrap these in EmbeddedCacheManagerConfigurationService with regular ManagedThreadPoolExecutorFactories, where as we should have a ManagedScheduledThreadPoolExecutorFactory to wrap this which would produce the proper type.
Without this it prevents configuring any kind of eviction or replication executor in the server.
{code}
08:36:04,570 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-11) MSC00001: Failed to start service jboss.infinispan.default.default: org.jboss.msc.service.StartException in service jboss.infinispan.default.default: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.eviction.impl.EvictionManagerImpl.start() on object of type EvictionManagerImpl
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:170)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:216)
at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699)
at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408)
at org.infinispan.registry.impl.ClusterRegistryImpl.startRegistryCache(ClusterRegistryImpl.java:146)
at org.infinispan.registry.impl.ClusterRegistryImpl.addListener(ClusterRegistryImpl.java:107)
at org.infinispan.query.remote.ProtobufMetadataManager.ensureInit(ProtobufMetadataManager.java:65)
at org.infinispan.query.remote.ProtobufMetadataManager.getSerializationContext(ProtobufMetadataManager.java:132)
at org.infinispan.query.remote.LifecycleManager.cacheStarting(LifecycleManager.java:114)
at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:228)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:214)
at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699)
at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:422)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:89)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:80)
at org.jboss.as.clustering.infinispan.subsystem.SecurityActions$5.run(SecurityActions.java:101)
at org.jboss.as.clustering.infinispan.subsystem.SecurityActions$5.run(SecurityActions.java:98)
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_51]
at org.jboss.as.clustering.infinispan.subsystem.SecurityActions.startCache(SecurityActions.java:109)
at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:78)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
... 3 more
Caused by: java.lang.ClassCastException: org.jboss.as.clustering.concurrent.ManagedExecutorService cannot be cast to java.util.concurrent.ScheduledExecutorService
at org.infinispan.executors.LazyInitializingScheduledExecutorService.initIfNeeded(LazyInitializingScheduledExecutorService.java:40)
at org.infinispan.executors.LazyInitializingScheduledExecutorService.scheduleWithFixedDelay(LazyInitializingScheduledExecutorService.java:146)
at org.infinispan.eviction.impl.EvictionManagerImpl.start(EvictionManagerImpl.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51]
at org.infinispan.
{code}
> Server to use a ManagedScheduledExecutorService for ScheduledExecutorServices
> -----------------------------------------------------------------------------
>
> Key: ISPN-4388
> URL: https://issues.jboss.org/browse/ISPN-4388
> Project: Infinispan
> Issue Type: Bug
> Reporter: William Burns
> Assignee: William Burns
>
> We use ScheduledExecutorServices for both the eviction and and replication queues. However we currently wrap these in EmbeddedCacheManagerConfigurationService with regular ManagedThreadPoolExecutorFactories, where as we should have a ManagedScheduledThreadPoolExecutorFactory to wrap this which would produce the proper type.
> Without this it prevents configuring any kind of eviction or replication executor in the server.
> {code}
> 08:36:04,570 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-11) MSC00001: Failed to start service jboss.infinispan.default.default: org.jboss.msc.service.StartException in service jboss.infinispan.default.default: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.eviction.impl.EvictionManagerImpl.start() on object of type EvictionManagerImpl
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:170)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:216)
> at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408)
> at org.infinispan.registry.impl.ClusterRegistryImpl.startRegistryCache(ClusterRegistryImpl.java:146)
> at org.infinispan.registry.impl.ClusterRegistryImpl.addListener(ClusterRegistryImpl.java:107)
> at org.infinispan.query.remote.ProtobufMetadataManager.ensureInit(ProtobufMetadataManager.java:65)
> at org.infinispan.query.remote.ProtobufMetadataManager.getSerializationContext(ProtobufMetadataManager.java:132)
> at org.infinispan.query.remote.LifecycleManager.cacheStarting(LifecycleManager.java:114)
> at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:228)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:214)
> at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:422)
> at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:89)
> at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:80)
> at org.jboss.as.clustering.infinispan.subsystem.SecurityActions$5.run(SecurityActions.java:101)
> at org.jboss.as.clustering.infinispan.subsystem.SecurityActions$5.run(SecurityActions.java:98)
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_51]
> at org.jboss.as.clustering.infinispan.subsystem.SecurityActions.startCache(SecurityActions.java:109)
> at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:78)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
> ... 3 more
> Caused by: java.lang.ClassCastException: org.jboss.as.clustering.concurrent.ManagedExecutorService cannot be cast to java.util.concurrent.ScheduledExecutorService
> at org.infinispan.executors.LazyInitializingScheduledExecutorService.initIfNeeded(LazyInitializingScheduledExecutorService.java:40)
> at org.infinispan.executors.LazyInitializingScheduledExecutorService.scheduleWithFixedDelay(LazyInitializingScheduledExecutorService.java:146)
> at org.infinispan.eviction.impl.EvictionManagerImpl.start(EvictionManagerImpl.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51]
> at org.infinispan.
> {code}
> http://ci.infinispan.org/viewLog.html?buildId=8736&buildTypeId=bt8&tab=bu...
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (ISPN-4388) Server to use a ManagedScheduledExecutorService for ScheduledExecutorServices
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4388?page=com.atlassian.jira.plugin.... ]
William Burns reassigned ISPN-4388:
-----------------------------------
Assignee: William Burns (was: Mircea Markus)
> Server to use a ManagedScheduledExecutorService for ScheduledExecutorServices
> -----------------------------------------------------------------------------
>
> Key: ISPN-4388
> URL: https://issues.jboss.org/browse/ISPN-4388
> Project: Infinispan
> Issue Type: Bug
> Reporter: William Burns
> Assignee: William Burns
>
> We use ScheduledExecutorServices for both the eviction and and replication queues. However we currently wrap these in EmbeddedCacheManagerConfigurationService with regular ManagedThreadPoolExecutorFactories, where as we should have a ManagedScheduledThreadPoolExecutorFactory to wrap this which would produce the proper type.
> Without this it prevents configuring any kind of eviction or replication executor in the server.
> {code}
> 08:36:04,570 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-11) MSC00001: Failed to start service jboss.infinispan.default.default: org.jboss.msc.service.StartException in service jboss.infinispan.default.default: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.eviction.impl.EvictionManagerImpl.start() on object of type EvictionManagerImpl
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:170)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:216)
> at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408)
> at org.infinispan.registry.impl.ClusterRegistryImpl.startRegistryCache(ClusterRegistryImpl.java:146)
> at org.infinispan.registry.impl.ClusterRegistryImpl.addListener(ClusterRegistryImpl.java:107)
> at org.infinispan.query.remote.ProtobufMetadataManager.ensureInit(ProtobufMetadataManager.java:65)
> at org.infinispan.query.remote.ProtobufMetadataManager.getSerializationContext(ProtobufMetadataManager.java:132)
> at org.infinispan.query.remote.LifecycleManager.cacheStarting(LifecycleManager.java:114)
> at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:228)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:214)
> at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:422)
> at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:89)
> at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:80)
> at org.jboss.as.clustering.infinispan.subsystem.SecurityActions$5.run(SecurityActions.java:101)
> at org.jboss.as.clustering.infinispan.subsystem.SecurityActions$5.run(SecurityActions.java:98)
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_51]
> at org.jboss.as.clustering.infinispan.subsystem.SecurityActions.startCache(SecurityActions.java:109)
> at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:78)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
> ... 3 more
> Caused by: java.lang.ClassCastException: org.jboss.as.clustering.concurrent.ManagedExecutorService cannot be cast to java.util.concurrent.ScheduledExecutorService
> at org.infinispan.executors.LazyInitializingScheduledExecutorService.initIfNeeded(LazyInitializingScheduledExecutorService.java:40)
> at org.infinispan.executors.LazyInitializingScheduledExecutorService.scheduleWithFixedDelay(LazyInitializingScheduledExecutorService.java:146)
> at org.infinispan.eviction.impl.EvictionManagerImpl.start(EvictionManagerImpl.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51]
> at org.infinispan.
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (ISPN-4388) Server to use a ManagedScheduledExecutorService for ScheduledExecutorServices
by William Burns (JIRA)
William Burns created ISPN-4388:
-----------------------------------
Summary: Server to use a ManagedScheduledExecutorService for ScheduledExecutorServices
Key: ISPN-4388
URL: https://issues.jboss.org/browse/ISPN-4388
Project: Infinispan
Issue Type: Bug
Reporter: William Burns
Assignee: Mircea Markus
We use ScheduledExecutorServices for both the eviction and and replication queues. However we currently wrap these in EmbeddedCacheManagerConfigurationService with regular ManagedThreadPoolExecutorFactories, where as we should have a ManagedScheduledThreadPoolExecutorFactory to wrap this which would produce the proper type.
Without this it prevents configuring any kind of eviction or replication executor in the server.
{code}
08:36:04,570 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-11) MSC00001: Failed to start service jboss.infinispan.default.default: org.jboss.msc.service.StartException in service jboss.infinispan.default.default: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.eviction.impl.EvictionManagerImpl.start() on object of type EvictionManagerImpl
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:170)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:216)
at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699)
at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408)
at org.infinispan.registry.impl.ClusterRegistryImpl.startRegistryCache(ClusterRegistryImpl.java:146)
at org.infinispan.registry.impl.ClusterRegistryImpl.addListener(ClusterRegistryImpl.java:107)
at org.infinispan.query.remote.ProtobufMetadataManager.ensureInit(ProtobufMetadataManager.java:65)
at org.infinispan.query.remote.ProtobufMetadataManager.getSerializationContext(ProtobufMetadataManager.java:132)
at org.infinispan.query.remote.LifecycleManager.cacheStarting(LifecycleManager.java:114)
at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:228)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:214)
at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699)
at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:422)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:89)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:80)
at org.jboss.as.clustering.infinispan.subsystem.SecurityActions$5.run(SecurityActions.java:101)
at org.jboss.as.clustering.infinispan.subsystem.SecurityActions$5.run(SecurityActions.java:98)
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_51]
at org.jboss.as.clustering.infinispan.subsystem.SecurityActions.startCache(SecurityActions.java:109)
at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:78)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
... 3 more
Caused by: java.lang.ClassCastException: org.jboss.as.clustering.concurrent.ManagedExecutorService cannot be cast to java.util.concurrent.ScheduledExecutorService
at org.infinispan.executors.LazyInitializingScheduledExecutorService.initIfNeeded(LazyInitializingScheduledExecutorService.java:40)
at org.infinispan.executors.LazyInitializingScheduledExecutorService.scheduleWithFixedDelay(LazyInitializingScheduledExecutorService.java:146)
at org.infinispan.eviction.impl.EvictionManagerImpl.start(EvictionManagerImpl.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51]
at org.infinispan.
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (ISPN-4386) JmxManagementIT.testCacheManagerAttributes test failure
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4386?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-4386:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1108122
> JmxManagementIT.testCacheManagerAttributes test failure
> -------------------------------------------------------
>
> Key: ISPN-4386
> URL: https://issues.jboss.org/browse/ISPN-4386
> Project: Infinispan
> Issue Type: Bug
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 7.0.0.Alpha5
>
>
> This test fails every time with
> {code}
> java.lang.AssertionError: expected:<3> but was:<4>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.infinispan.server.test.jmx.management.JmxManagementIT.testCacheManagerAttributes(JmxManagementIT.java:174)
> 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:606)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270)
> at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
> 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:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53)
> 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:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129)
> 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:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
> at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111)
> at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263)
> at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.junit.runners.Suite.runChild(Suite.java:127)
> at org.junit.runners.Suite.runChild(Suite.java:26)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:138)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:62)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:139)
> 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:606)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> {code}
> looking into it deeper it looks like this is caused by a new cache being installed in the server of __cluster_registry_cache__.
> http://ci.infinispan.org/viewLog.html?buildId=8736&buildTypeId=bt8&tab=bu...
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (ISPN-4317) Optimize server test suite
by Jakub Markos (JIRA)
[ https://issues.jboss.org/browse/ISPN-4317?page=com.atlassian.jira.plugin.... ]
Jakub Markos edited comment on ISPN-4317 at 6/11/14 8:58 AM:
-------------------------------------------------------------
Here are my observations:
Currently the server testsuite takes 30 minutes on my PC, and there are 130 server starts (with tests for example configs, which are currently marked as unstable in upstream). Server starts in 5-10 seconds on my machine (in teamcity it's 10-20), so around 15 minutes (30 in TC) are spent on that.
Here is a table of amount of server starts for various tests:
|| tests name || \# server starts || comment / what can be done ||
| jdbc tests | 36 | Most of the tests use memcached cache, which means they can't share the server configuration. Using hotrod instead could reduce this, I'll look into this next. |
| example configurations tests | 30 | Largest chunk is taken by server hinting tests (9 server starts, 3 for each machine/rack/site). Generally I don't think anything can be done about these tests, since their whole purpose is to take the example configuration and test it as is (we still need to do some transformations on them, though). |
| tests for suppressing the state transfer | 22 | I've cut this down to 6, which seems ok. |
| file/remote/custom/leveldb cache stores tests | ~10 | They all need to restart the server to see if entries are really stored. I'll look if they can be somehow grouped together. |
| remote query tests | 6 | Made them share the configuration (see option 2 below), so only 1 now. |
| transport stack tests | 6 | Cut down to 2. |
| Rest security tests | 6 | Can't be reduced, they each need their own definition of rest endpoint. |
| client tests | 5 | They run across different failsafe executions. |
The rest of the tests uses around 10 starts.
Reusing the same configuration for various tests is of course possible. There are 2 ways in doing this:
# put the tests into 1 class
# move the tests to separate failsafe execution so we can use arquillians 'suite' container mode, and create a new category for them (and also a new Unstable category).
The second option is OK, but I think it clutters the testsuite a bit and creates a barrier for writing tests by new people.
I'll look on the jdbc and cachestore tests next, because that promises the biggest time gains.
Other ways to minimize the time would be in the tests themselves (reducing jmx calls for example).
was (Author: jmarkos):
Here are my observations:
Currently the server testsuite takes 30 minutes on my PC, and there are 130 server starts (with tests for example configs, which are currently marked as unstable in upstream). Server starts in 5-10 seconds on my machine (in teamcity it's 10-20), so around 15 minutes are spent on that.
Here is a table of amount of server starts for various tests:
|| tests name || \# server starts || comment / what can be done ||
| jdbc tests | 36 | Most of the tests use memcached cache, which means they can't share the server configuration. Using hotrod instead could reduce this, I'll look into this next. |
| example configurations tests | 30 | Largest chunk is taken by server hinting tests (9 server starts, 3 for each machine/rack/site). Generally I don't think anything can be done about these tests, since their whole purpose is to take the example configuration and test it as is (we still need to do some transformations on them, though). |
| tests for suppressing the state transfer | 22 | I've cut this down to 6, which seems ok. |
| file/remote/custom/leveldb cache stores tests | ~10 | They all need to restart the server to see if entries are really stored. I'll look if they can be somehow grouped together. |
| remote query tests | 6 | Made them share the configuration (see option 2 below), so only 1 now. |
| transport stack tests | 6 | Cut down to 2. |
| Rest security tests | 6 | Can't be reduced, they each need their own definition of rest endpoint. |
| client tests | 5 | They run across different failsafe executions. |
The rest of the tests uses around 10 starts.
Reusing the same configuration for various tests is of course possible. There are 2 ways in doing this:
# put the tests into 1 class
# move the tests to separate failsafe execution so we can use arquillians 'suite' container mode, and create a new category for them (and also a new Unstable category).
The second option is OK, but I think it clutters the testsuite a bit and creates a barrier for writing tests by new people.
I'll look on the jdbc and cachestore tests next, because that promises the biggest time gains.
Other ways to minimize the time would be in the tests themselves (reducing jmx calls for example).
> Optimize server test suite
> --------------------------
>
> Key: ISPN-4317
> URL: https://issues.jboss.org/browse/ISPN-4317
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite - Server
> Affects Versions: 7.0.0.Alpha4
> Reporter: Martin Gencur
> Assignee: Jakub Markos
>
> The goal is to make the test execution of server test suite shorter and minimize the number of maven profiles so that most of the tests run in a default profile.
> The first thing to do is to minimize the number of server restarts when running the test suite. This will require adding many different cache configurations to the same Infinispan subsystem.
> Also, look for other ways to minimize test execution time.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (ISPN-4317) Optimize server test suite
by Jakub Markos (JIRA)
[ https://issues.jboss.org/browse/ISPN-4317?page=com.atlassian.jira.plugin.... ]
Jakub Markos commented on ISPN-4317:
------------------------------------
Here are my observations:
Currently the server testsuite takes 30 minutes on my PC, and there are 130 server starts (with tests for example configs, which are currently marked as unstable in upstream). Server starts in 5-10 seconds on my machine (in teamcity it's 10-20), so around 15 minutes are spent on that.
Here is a table of amount of server starts for various tests:
|| tests name || \# server starts || comment / what can be done ||
| jdbc tests | 36 | Most of the tests use memcached cache, which means they can't share the server configuration. Using hotrod instead could reduce this, I'll look into this next. |
| example configurations tests | 30 | Largest chunk is taken by server hinting tests (9 server starts, 3 for each machine/rack/site). Generally I don't think anything can be done about these tests, since their whole purpose is to take the example configuration and test it as is (we still need to do some transformations on them, though). |
| tests for suppressing the state transfer | 22 | I've cut this down to 6, which seems ok. |
| file/remote/custom/leveldb cache stores tests | ~10 | They all need to restart the server to see if entries are really stored. I'll look if they can be somehow grouped together. |
| remote query tests | 6 | Made them share the configuration (see option 2 below), so only 1 now. |
| transport stack tests | 6 | Cut down to 2. |
| Rest security tests | 6 | Can't be reduced, they each need their own definition of rest endpoint. |
| client tests | 5 | They run across different failsafe executions. |
The rest of the tests uses around 10 starts.
Reusing the same configuration for various tests is of course possible. There are 2 ways in doing this:
# put the tests into 1 class
# move the tests to separate failsafe execution so we can use arquillians 'suite' container mode, and create a new category for them (and also a new Unstable category).
The second option is OK, but I think it clutters the testsuite a bit and creates a barrier for writing tests by new people.
I'll look on the jdbc and cachestore tests next, because that promises the biggest time gains.
Other ways to minimize the time would be in the tests themselves (reducing jmx calls for example).
> Optimize server test suite
> --------------------------
>
> Key: ISPN-4317
> URL: https://issues.jboss.org/browse/ISPN-4317
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite - Server
> Affects Versions: 7.0.0.Alpha4
> Reporter: Martin Gencur
> Assignee: Jakub Markos
>
> The goal is to make the test execution of server test suite shorter and minimize the number of maven profiles so that most of the tests run in a default profile.
> The first thing to do is to minimize the number of server restarts when running the test suite. This will require adding many different cache configurations to the same Infinispan subsystem.
> Also, look for other ways to minimize test execution time.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (ISPN-4387) Write Skew Check does not work with Passivation
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-4387?page=com.atlassian.jira.plugin.... ]
Work on ISPN-4387 started by Pedro Ruivo.
> Write Skew Check does not work with Passivation
> -----------------------------------------------
>
> Key: ISPN-4387
> URL: https://issues.jboss.org/browse/ISPN-4387
> Project: Infinispan
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 7.0.0.Alpha4
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Fix For: 7.0.0.Beta1
>
>
> Write Skew Check does not perform the validation correctly when Passivation is enabled.
> Issue:
> The current implementation checks the most recent version/value in DataContainer. However, the entry may be passivated and it is not present in DataContainer. The Write Skew Check will abort the transaction when the transaction read some value (say version V), because it is expecting to find the version V but it does not find the entry. It assumes that the entry was removed and aborts the transaction.
> A more dangerous case is when at least two transactions are writing to a new key. The first commits and before the second transaction is prepared, the entry is passivated. In this case, it assumes the entry does not exists and let the second transaction to commit.
> Solution:
> It needs to try to load the entry from Persistence.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months