Re: [jBoss-User] hot re-deploy question
Greg Pierce wrote: > Cool... I thought that was already in there. What happens now if you just > redeploy a bean if the container is in the midst of doing real work? The call will continue until its done, but there might be problems with plugins being shutdown. This should be fixed. /Rickard -- Rickard Öberg Email: [EMAIL PROTECTED] http://www.telkel.com http://www.jboss.org http://www.dreambean.com -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
RE: [jBoss-User] hot re-deploy question
Cool... I thought that was already in there. What happens now if you just redeploy a bean if the container is in the midst of doing real work? -Original Message- From: Rickard Öberg [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 24, 2000 3:18 AM To: jBoss Subject: Re: [jBoss-User] hot re-deploy question Hi! Jeremiah Johnson wrote: > Is there defined behavior for a hot re-deploying a jar which happens to replace an instance of a bean that is involved in a transaction? Does that question make sense? To rephrase, if I fix a bug in a stateful session bean and I redeploy the application containing that session bean, do I have to be concerned about trying to time my redeploy so that no clients are making calls to an instance of the bean? Well, an undeploy will shut down the containers and the invocation layers. I guess we could add code in "stop" that makes sure that when "stop" returns no invocations are active, and no invocations are let in. So no, currently it is not well-defined, but we could change that. /Rickard -- Rickard Öberg Email: [EMAIL PROTECTED] http://www.telkel.com http://www.jboss.org http://www.dreambean.com -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED] -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
Re: [jBoss-User] hot re-deploy question
Hi! Jeremiah Johnson wrote: > Is there defined behavior for a hot re-deploying a jar which happens to replace an >instance of a bean that is involved in a transaction? Does that question make sense? > To rephrase, if I fix a bug in a stateful session bean and I redeploy the >application containing that session bean, do I have to be concerned about trying to >time my redeploy so that no clients are making calls to an instance of the bean? Well, an undeploy will shut down the containers and the invocation layers. I guess we could add code in "stop" that makes sure that when "stop" returns no invocations are active, and no invocations are let in. So no, currently it is not well-defined, but we could change that. /Rickard -- Rickard Öberg Email: [EMAIL PROTECTED] http://www.telkel.com http://www.jboss.org http://www.dreambean.com -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
