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-3810 Graceful shutdown support for mod_cluster #6914

Merged
merged 1 commit into from Nov 19, 2014

Conversation

stuartwdouglas
Copy link
Contributor

No description provided.

@stuartwdouglas
Copy link
Contributor Author

@jfclere @rhusar does this look ok to you guys?

@wildfly-ci
Copy link

Windows Build 521 is now running using a merge of 8249112

@wildfly-ci
Copy link

Linux Build 5418 is now running using a merge of 8249112

@wildfly-ci
Copy link

Linux with security manager Build 407 is now running using a merge of 8249112

@wildfly-ci
Copy link

Linux with security manager Build 407 outcome was SUCCESS using a merge of 8249112
Summary: Tests passed: 796, ignored: 244 Build time: 0:06:27

@wildfly-ci
Copy link

Linux Build 5418 outcome was FAILURE using a merge of 8249112
Summary: Execution timeout (new); tests passed: 2916, ignored: 239; org.wildfly:wildfly-testsuite-integration-domain Build time: 3:00:12

Build problems:

Execution timeout
Process exited with code 137

@wildfly-ci
Copy link

Windows Build 521 outcome was FAILURE using a merge of 8249112
Summary: Execution timeout (new); tests passed: 2947, ignored: 239; org.wildfly:wildfly-testsuite-integration-domain Build time: 3:00:21

Build problems:

Execution timeout
Process exited with code 1

@wildfly-ci
Copy link

Linux Build 5438 is now running using a merge of 99dfd12

@wildfly-ci
Copy link

Linux with security manager Build 427 is now running using a merge of 99dfd12

@wildfly-ci
Copy link

Windows Build 541 is now running using a merge of 99dfd12

@wildfly-ci
Copy link

Linux with security manager Build 427 outcome was SUCCESS using a merge of 99dfd12
Summary: Tests passed: 796, ignored: 244 Build time: 0:06:55

@wildfly-ci
Copy link

Windows Build 541 outcome was SUCCESS using a merge of 99dfd12
Summary: Tests passed: 2996, ignored: 239, muted: 1 Build time: 0:51:59

@wildfly-ci
Copy link

Linux Build 5438 outcome was FAILURE using a merge of 99dfd12
Summary: Tests failed: 770 (770 new), passed: 772, ignored: 196, muted: 1 Build time: 2:47:36

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.smoke.rar.RarTestCase.helloWorld: javax.naming.NameNotFoundException: eis/HelloWorld -- service jboss.naming.context.java.eis.HelloWorld
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)

org.jboss.as.test.smoke.rar.RarTestCase.helloWorld2: javax.naming.NameNotFoundException: eis/HelloWorld -- service jboss.naming.context.java.eis.HelloWorld
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)

org.jboss.as.test.smoke.jaxrs.JaxrsTestCase.testJaxrs: java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: HTTP Status 404 Response: <html><head><title>Error</title></head><body>Not Found</body></html>
    at java.util.concurrent.FutureTask.report(FutureTask.java:122)
    at java.util.concurrent.FutureTask.get(FutureTask.java:202)

org.jboss.as.test.smoke.ejb3.jndi.EarDeploymentEjbJndiBindingTestCase.testLocalBindingsOnSFSB: javax.naming.NameNotFoundException: ear-deployment-ejb3-binding/ejb3-jndi-binding-test/SampleSFSB!org.jboss.as.test.smoke.ejb3.jndi.Echo -- service jboss.naming.context.java.global.ear-deployment-ejb3-binding.ejb3-jndi-binding-test."SampleSFSB!org.jboss.as.test.smoke.ejb3.jndi.Echo"
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)

org.jboss.as.test.smoke.ejb3.jndi.EarDeploymentEjbJndiBindingTestCase.testLocalBindingsOnSLSB: javax.naming.NameNotFoundException: ear-deployment-ejb3-binding/ejb3-jndi-binding-test/SampleSLSB!org.jboss.as.test.smoke.ejb3.jndi.Echo -- service jboss.naming.context.java.global.ear-deployment-ejb3-binding.ejb3-jndi-binding-test."SampleSLSB!org.jboss.as.test.smoke.ejb3.jndi.Echo"
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)

org.jboss.as.test.smoke.ejb3.jndi.EarDeploymentEjbJndiBindingTestCase.testRemoteBindingsOnSFSB: javax.naming.NameNotFoundException: ear-deployment-ejb3-binding/ejb3-jndi-binding-test/SampleSFSB!org.jboss.as.test.smoke.ejb3.jndi.RemoteEcho -- service jboss.naming.context.java.global.ear-deployment-ejb3-binding.ejb3-jndi-binding-test."SampleSFSB!org.jboss.as.test.smoke.ejb3.jndi.RemoteEcho"
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)

org.jboss.as.test.smoke.ejb3.jndi.EarDeploymentEjbJndiBindingTestCase.testRemoteBindingsOnSLSB: javax.naming.NameNotFoundException: ear-deployment-ejb3-binding/ejb3-jndi-binding-test/SampleSLSB!org.jboss.as.test.smoke.ejb3.jndi.RemoteEcho -- service jboss.naming.context.java.global.ear-deployment-ejb3-binding.ejb3-jndi-binding-test."SampleSLSB!org.jboss.as.test.smoke.ejb3.jndi.RemoteEcho"
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)

org.jboss.as.test.smoke.ejb3.dd.DDBasedEJBTestCase: org.jboss.as.test.smoke.ejb3.jndi.StandaloneModuleEjbJndiBindingTestCase.testLocalBindingsOnSFSB: javax.naming.NameNotFoundException: ejb3-jndi-binding-test/SampleSFSB!org.jboss.as.test.smoke.ejb3.jndi.Echo -- service jboss.naming.context.java.global.ejb3-jndi-binding-test."SampleSFSB!org.jboss.as.test.smoke.ejb3.jndi.Echo"
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)

org.jboss.as.test.smoke.ejb3.dd.DDBasedEJBTestCase: org.jboss.as.test.smoke.ejb3.jndi.StandaloneModuleEjbJndiBindingTestCase.testLocalBindingsOnSLSB: javax.naming.NameNotFoundException: ejb3-jndi-binding-test/SampleSLSB!org.jboss.as.test.smoke.ejb3.jndi.Echo -- service jboss.naming.context.java.global.ejb3-jndi-binding-test."SampleSLSB!org.jboss.as.test.smoke.ejb3.jndi.Echo"
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)

org.jboss.as.test.smoke.ejb3.dd.DDBasedEJBTestCase: org.jboss.as.test.smoke.ejb3.jndi.StandaloneModuleEjbJndiBindingTestCase.testRemoteBindingsOnSFSB: javax.naming.NameNotFoundException: ejb3-jndi-binding-test/SampleSFSB!org.jboss.as.test.smoke.ejb3.jndi.RemoteEcho -- service jboss.naming.context.java.global.ejb3-jndi-binding-test."SampleSFSB!org.jboss.as.test.smoke.ejb3.jndi.RemoteEcho"
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)

org.jboss.as.test.smoke.ejb3.dd.DDBasedEJBTestCase: org.jboss.as.test.smoke.ejb3.jndi.StandaloneModuleEjbJndiBindingTestCase.testRemoteBindingsOnSLSB: javax.naming.NameNotFoundException: ejb3-jndi-binding-test/SampleSLSB!org.jboss.as.test.smoke.ejb3.jndi.RemoteEcho -- service jboss.naming.context.java.global.ejb3-jndi-binding-test."SampleSLSB!org.jboss.as.test.smoke.ejb3.jndi.RemoteEcho"
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)


##### there are 760 more failed tests, see build details

@stuartwdouglas
Copy link
Contributor Author

Retest this please

@wildfly-ci
Copy link

Linux with security manager Build 439 is now running using a merge of 99dfd12

@wildfly-ci
Copy link

Linux Build 5450 is now running using a merge of 99dfd12

@wildfly-ci
Copy link

Windows Build 553 is now running using a merge of 99dfd12

@wildfly-ci
Copy link

Linux with security manager Build 439 outcome was SUCCESS using a merge of 99dfd12
Summary: Tests passed: 796, ignored: 244 Build time: 0:07:08

@wildfly-ci
Copy link

Windows Build 553 outcome was SUCCESS using a merge of 99dfd12
Summary: Tests passed: 2996, ignored: 239, muted: 1 Build time: 0:51:44

@wildfly-ci
Copy link

Linux Build 5450 outcome was FAILURE using a merge of 99dfd12
Summary: Tests failed: 1 (1 new), passed: 2995, ignored: 239, muted: 1 Build time: 0:54:09

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize: javax.ejb.EJBException: java.lang.IllegalStateException: WFLYCLEJBINF0008: Stateful session bean {[105, 39, 10, 99, 46, 12, 69, 95, -79, 94, -103, 114, 75, -23, 10, -59]} refers to an invalid bean group 55b5d11b-d76a-46e1-aa7f-1551d6c28a12
    at org.wildfly.clustering.ejb.infinispan.bean.InfinispanBeanFactory.createBean(InfinispanBeanFactory.java:75)
    at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager.findBean(InfinispanBeanManager.java:266)

@rhusar
Copy link
Member

rhusar commented Nov 14, 2014

Unfortunately I haven't finished reviewing this, but last I was wondering whether we don't have to do a modcluster shutdown instead. But if the listener/connector is still handling CPING/CPONG for AJP and OPTIONS for HTTP when suspended then it shouldn't be a problem.

@jfclere
Copy link
Contributor

jfclere commented Nov 14, 2014

Not answering to CPING or OPTIONS will just mark the node in error (in some cases after a timeout)

@rhusar
Copy link
Member

rhusar commented Nov 14, 2014

Looking again at the code and design proposal, the server should answer to ping mechanisms even when paused. Therefore, I think this PR looks good and does what we need. 👍

@bstansberry
Copy link
Contributor

Based on the above comments, I'm marking this ready for merge.

@bstansberry bstansberry added the ready-for-merge Only for use by those with merge permissions! label Nov 18, 2014
bstansberry added a commit that referenced this pull request Nov 19, 2014
WFLY-3810 Graceful shutdown support for mod_cluster
@bstansberry bstansberry merged commit d7d833f into wildfly:master Nov 19, 2014
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
5 participants