"emuckenhuber" wrote : "bstansberry(a)jboss.com" wrote : Could the
deployment of the acceptor be part of the deployment of the service? It's just a
separate MC bean that depends on the core service.
| |
| | That eliminates the issue of deployment phases.
|
| Yeah i thought it's just a MC bean with an install callback :) It's just a
question when this bean gets deployed. Basically there is no way we can eliminate
deployment phases - where at the moment each Profile represents a deployment phase
(mainDeployer.process()).
| Just think what would happen if you move the "TomcatService" into the
'web.deployer'. This would start the connectors/acceptors/endpoints before even
looking at what's in 'deploy'. Which means that the acceptor would be
available, but without any web app installed. The same would happen if we have multiple
smaller profile description.
|
| Although this is not specific to graceful shutdown it could affect it depending on the
way you signal the acceptors to gracefully stop. If the "central management
bean" is called to signal the shutdown, before we actually stop AS then it could
work. Otherwise the same would happen - we undeploy all user applications, before
undeploying the acceptor deployment.
I agree with your conclusion "if the "central management bean" is called to
signal the shutdown, before we actually stop AS then it could work." But I want to
clarify some re: my understanding of the acceptor and how it ties in to deployment
stages.
AIUI, an acceptor is not scoped to a connector. It's scoped to the thing that handles
requests for a particular component (a webapp, and EJB). In Tomcat terms, it would be the
first thing in the webapp-specific Pipeline that results in a call on the servlet.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267562#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...