[Jboss-dev-forums] [Deployers on JBoss (Deployers/JBoss)] - Re: JBoss Atomic Farm Deployment

[<ad...@jb...>]

On Atomic Deployments. The aim here is to replace
redeploy == undeploy/deploy
with something as near atomic and undistruptive as possible.

The redeploy will become something like:
* See whether the deployment can be constructed
* If it works, wait for current requests to complete and hold new requests (this is called the "valve")
* Once current requests are done, switch the from old to new deployment, e.g. flip
the jndi bindings and other outward facing references - this may also require some
handoff of state, e.g. handing over cache/session objects
* Remove the old/replaced deployments

NOTE: Because of classloading requirements, the cache/session handover
will almost certain require some of form serialzation. Either passivation of the 
sessions to disk or replication from the other cluster nodes.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876158#3876158

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876158