Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server #8149

Merged

Conversation

rhusar
Copy link
Member

@rhusar rhusar commented Sep 18, 2015

Jiras
https://issues.jboss.org/browse/WFLY-6615
https://issues.jboss.org/browse/WFLY-4255
https://issues.jboss.org/browse/WFLY-3532

@jamezp is afraid this might jeopardy testsuite stability and prefers to have this in 11.x
@rachmatowicz believes we cannot support RemoteFailoverTestCase without support for graceful shutdown

@rhusar rhusar changed the title [probably 11.x] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server [11.x probably] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server Sep 18, 2015
@jamezp
Copy link
Member

jamezp commented Sep 18, 2015

retest this please

@bstansberry bstansberry added rebase-this PR has a merge conflict. 11.x labels Sep 22, 2015
@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from 940d7fe to 94c7d33 Compare September 29, 2015 11:21
@rhusar rhusar changed the title [11.x probably] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server [11] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server Sep 29, 2015
@rhusar
Copy link
Member Author

rhusar commented Oct 4, 2015

Just to update on this: this is still undergoing investigation but it is mostly likely uncovering a real problem. The test needs improvements (as discussed on the clustering call last week) as to fail, rather than hang. Primarily @rachmatowicz is investigating now.

@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from 94c7d33 to 3695f28 Compare October 20, 2015 15:33
@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from 3695f28 to 37d9ab8 Compare February 2, 2016 12:28
@rhusar rhusar changed the title [11] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server [11.x] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server Feb 2, 2016
@rhusar
Copy link
Member Author

rhusar commented Feb 2, 2016

retest this please

@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from 37d9ab8 to c92a8aa Compare February 3, 2016 15:49
@jamezp jamezp removed the rebase-this PR has a merge conflict. label Feb 9, 2016
@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from c92a8aa to dfc8d84 Compare February 15, 2016 13:43
@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from dfc8d84 to e4ffd4a Compare March 7, 2016 16:48
@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from e4ffd4a to 6e876d9 Compare April 7, 2016 07:41
@rhusar rhusar changed the title [11.x] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server [10.1.x] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server Apr 7, 2016
@rhusar rhusar changed the title [10.1.x] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server [10.1.x/11.x] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server Apr 7, 2016
@bstansberry
Copy link
Contributor

@rhusar a 1.1.0.Final release of wildfly-arquillian is out so that should be used.

@jamezp Is this ok, assuming the version is bumped to .Final? Is it ok for 10.1 or just 11.0?

@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from 6e876d9 to bc95c00 Compare May 10, 2016 22:42
@rhusar
Copy link
Member Author

rhusar commented May 10, 2016

@bstansberry Thanks for the info, updated to 1.1.0.Final.

@jamezp
Copy link
Member

jamezp commented May 11, 2016

Yes should be good to go for 11.

@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from bc95c00 to b4c628f Compare May 11, 2016 08:46
@bstansberry bstansberry added ready-for-merge Only for use by those with merge permissions! 11.x and removed 11.x labels May 11, 2016
@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from b4c628f to 4ad09ab Compare May 16, 2016 15:58
@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from 4ad09ab to f7dc5c4 Compare June 20, 2016 14:59
@rhusar rhusar changed the title [10.1.x/11.x] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server [11.x] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server Jun 20, 2016
@ctomc
Copy link
Contributor

ctomc commented Jun 23, 2016

@rhusar looking at failures, they do look related to this change.
Well not by this change as such, but with what this change does to behavior of server.
Looks like we have some bad behaving tests or even impl of suspend.

@jamezp
Copy link
Member

jamezp commented Jul 5, 2016

Just placed a hold on this @rhusar since you said you were going to fix it. Once you're done I'll remove the hold label.

@jamezp jamezp self-assigned this Jul 5, 2016
@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from 1976210 to 38225f8 Compare July 26, 2016 22:41
@rhusar
Copy link
Member Author

rhusar commented Jul 27, 2016

I have split the test case into 2 by failover type and asked @rachmatowicz for review.

@jamezp
Copy link
Member

jamezp commented Jul 27, 2016

Perfect, thanks @rhusar. I'll wait for a comment from @rachmatowicz before I change any labels.

@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from 38225f8 to 58eb989 Compare July 28, 2016 16:55
@rachmatowicz
Copy link
Contributor

@jamezp Had a detailed look at this PR and all is well. This is a significant milestone for us in terms of being able to test with clean shutdown, so any help getting this merged quickly would be appreciated.

@jamezp jamezp removed their assignment Jul 29, 2016
@jamezp jamezp added ready-for-merge Only for use by those with merge permissions! and removed hold PR should not be merged for some reason. labels Jul 29, 2016
@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from 58eb989 to f14e465 Compare July 30, 2016 19:08
@rhusar
Copy link
Member Author

rhusar commented Aug 2, 2016

BTW I have started about 40 CI runs for this PR and all is good.

@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from f14e465 to 6bbc2e2 Compare August 15, 2016 20:19
@rhusar
Copy link
Member Author

rhusar commented Aug 18, 2016

Anything holding this back? Marked read-for-merge 3 weeks ago and master is already branched.

@jamezp
Copy link
Member

jamezp commented Aug 18, 2016

When I first labeled it master wasn't at 11.x yet. Let's retest this please one more time.

@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from 6bbc2e2 to b30367a Compare August 18, 2016 16:21
@rhusar
Copy link
Member Author

rhusar commented Aug 18, 2016

Started a bunch of runs; around 15.

@jamezp
Copy link
Member

jamezp commented Aug 18, 2016

Yeah I noticed that after I typed the message :)

@wildfly-ci
Copy link

Windows Build 5233 outcome was FAILURE using a merge of b30367a
Summary: Tests failed: 1 (1 new), passed: 3421, ignored: 195 Build time: 01:39:01

Failed tests

org.jboss.as.test.clustering.cluster.web.ConcurrentFineWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover: java.lang.AssertionError: Session failed to replicate after container 1 was shutdown. expected:<3> but was:<2>
    at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:155)
    at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:108)
------- Stdout: -------
18:20:31,816 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
18:20:31,817 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
18:20:31,817 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
18:20:31,855 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\2e\b0c5f06f4f87cab865df04fe94d090fc3ec0ea\content
18:20:31,861 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "fine-concurrent-distributable.war" (runtime-name: "fine-concurrent-distributable.war")
18:20:31,926 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
18:20:31,926 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
18:20:31,927 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
18:20:31,938 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment fine-concurrent-distributable.war
18:20:31,957 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "fine-concurrent-distributable.war"' are as follows:

    java:global/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
    java:app/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
    java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
    java:jboss/exported/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
    java:global/fine-concurrent-distributable/TopologyChangeListenerBean
    java:app/fine-concurrent-distributable/TopologyChangeListenerBean
    java:module/TopologyChangeListenerBean

18:20:32,015 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 14) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:20:32,016 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 14) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:20:32,031 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 32) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:20:32,032 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 32) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:20:32,041 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 73) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:20:32,042 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 73) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:20:32,045 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 14) WFLYCLINF0002: Started client-mappings cache from ejb container
18:20:32,069 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) WFLYCLINF0002: Started routing cache from web container
18:20:32,079 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 73) WFLYCLINF0002: Started fine-concurrent-distributable.war cache from web container
18:20:32,519 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 14) WFLYUT0021: Registered web context: /fine-concurrent-distributable
18:20:32,577 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "fine-concurrent-distributable.war" (runtime-name : "fine-concurrent-distributable.war")
18:20:32,926 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
18:20:33,083 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\34\3b4e68492a188f65770dd794fe8677db244d02\content
18:20:33,106 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "fine-concurrent-distributable.war" (runtime-name: "fine-concurrent-distributable.war")
18:20:33,178 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
18:20:33,179 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
18:20:33,179 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.fine-concurrent-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
18:20:33,185 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment fine-concurrent-distributable.war
18:20:33,198 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "fine-concurrent-distributable.war"' are as follows:

    java:global/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
    java:app/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
    java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
    java:jboss/exported/fine-concurrent-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
    java:global/fine-concurrent-distributable/TopologyChangeListenerBean
    java:app/fine-concurrent-distributable/TopologyChangeListenerBean
    java:module/TopologyChangeListenerBean



@wildfly-ci
Copy link

Linux Build 10197 outcome was FAILURE using a merge of b30367a
Summary: Execution timeout (new); tests passed: 2180, ignored: 137 Build time: 01:40:20

@kabir kabir added JBEAP and removed 11.x labels Aug 19, 2016
@@ -218,7 +218,7 @@
<version.org.wildfly.build-tools>1.1.3.Final</version.org.wildfly.build-tools>
<version.org.wildfly.checkstyle-config>1.0.5.Final</version.org.wildfly.checkstyle-config>
<version.org.wildfly.core>3.0.0.Alpha5</version.org.wildfly.core>
<version.org.wildfly.arquillian>1.0.2.Final</version.org.wildfly.arquillian>
<version.org.wildfly.arquillian>1.1.0.Final</version.org.wildfly.arquillian>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should really move to 2.0.0.Final at this point.
Could you update PR to that.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, lets try that, if all passes then we are good.

Copy link
Member Author

@rhusar rhusar Aug 19, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool, all good. Started 10 more runs just in case.

… clean shutdown mechanism when shutting down a server

WFLY-3532 Reenable RemoteFailoverTestCase stabilized by graceful shutdown arquillian support
@rhusar rhusar force-pushed the WFLY-4255_graceful_shutdown_arquillian_support branch from b30367a to 2c5bc76 Compare August 19, 2016 10:14
@wildfly-ci
Copy link

Linux Build 10223 outcome was FAILURE using a merge of 2c5bc76
Summary: Execution timeout (new); tests failed: 1 (1 new), passed: 3438, ignored: 194 Build time: 01:40:07

Failed tests

org.jboss.as.test.integration.ejb.stateful.passivation.ejb2.PassivationSucceedsEJB2TestCase.testPassivationMaxSize: java.rmi.NoSuchObjectException: WFLYEJB0168: Could not find EJB with id UnknownSessionID [5367485269485352515455665253674966516865506550546657505254665654]
    at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:84)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
    at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
    at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
    at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
    at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
    at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636)
    at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
    at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
    at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
    at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
    at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
    at org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:266)
    at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:184)
    at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocation(EJBObjectInterceptor.java:58)
    at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
    at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocation(EJBHomeInterceptor.java:83)
    at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
    at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
    at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
    at org.jboss.as.test.integration.ejb.remote.client.api.interceptor.SimpleEJBClientInterceptor.handleInvocation(SimpleEJBClientInterceptor.java:48)
    at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
    at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:138)
    at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
    at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
    at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
    at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
    at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
    at com.sun.proxy.$Proxy381.remove(Unknown Source)
    at org.jboss.as.test.integration.ejb.stateful.passivation.ejb2.PassivationSucceedsEJB2TestCase.testPassivationMaxSize(PassivationSucceedsEJB2TestCase.java:110)
------- Stdout: -------
 [0m04:44:28,760 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 26) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'passivation-test.jar#main'
 [0m [0m04:44:28,760 INFO  [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 26) HHH000227: Running hbm2ddl schema export
 [0m [0m04:44:28,762 INFO  [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 26) HHH000230: Schema export complete
 [0m [0m04:44:28,763 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 66) ISPN000029: Passivating all entries to disk
 [0m [0m04:44:28,766 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 26) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'passivation-test.jar#main'
 [0m [33m04:44:28,768 WARN  [org.infinispan.factories.ComponentRegistry] (ServerService Thread Pool -- 66) ISPN000189: While stopping a cache or cache manager, one of its components failed to stop: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.eviction.impl.PassivationManagerImpl.passivateAll() throws org.infinispan.persistence.spi.PersistenceException on object of type PassivationManagerImpl
    at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172)
    at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:859)
    at org.infinispan.factories.AbstractComponentRegistry.internalStop(AbstractComponentRegistry.java:664)
    at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:564)
    at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:260)
    at org.infinispan.cache.impl.CacheImpl.stop(CacheImpl.java:869)
    at org.infinispan.cache.impl.CacheImpl.stop(CacheImpl.java:864)
    at org.infinispan.cache.impl.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:331)


@rhusar rhusar changed the title [11.x] WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server WFLY-4255 Allow Arquillian to specify a timeout value for the WildFly clean shutdown mechanism when shutting down a server Aug 19, 2016
@kabir kabir merged commit d9671d3 into wildfly:master Aug 22, 2016
@rhusar rhusar deleted the WFLY-4255_graceful_shutdown_arquillian_support branch August 23, 2016 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge Only for use by those with merge permissions!
Projects
None yet
7 participants