Re: destory method is called twice while the child is destoryed directly

Yes, I am using 7.0.4. Will create a entry in the bugzila system Thanks. 2010/10/28 Mark Thomas > On 28/10/2010 02:20, Ivan wrote: > > Thanks for clarifying it, so do the devs have plan for it ? > > Yes. What? Fix it. When? TBD. > > Creating a bugzilla entry will ensure it doesn't get forgotten.

Re: destory method is called twice while the child is destoryed directly

On 28/10/2010 02:20, Ivan wrote: > Thanks for clarifying it, so do the devs have plan for it ? Yes. What? Fix it. When? TBD. Creating a bugzilla entry will ensure it doesn't get forgotten. I see you still haven't told us which version you are using. I assume you've tested 7.0.4. Mark > Hope it

Re: destory method is called twice while the child is destoryed directly

Thanks for clarifying it, so do the devs have plan for it ? Hope it could be fixed soon. 2010/10/27 Mark Thomas > On 27/10/2010 06:43, Ivan wrote: > > Hi, > > While calling the method destory() on the StandardContext directly, > it > > seems that the method destoryInternal() is called twice

Re: destory method is called twice while the child is destoryed directly

Thanks for clarifying it, does the devs have plan for it ? Hope it could be fixed soon. 2010/10/27 Mark Thomas > On 27/10/2010 06:43, Ivan wrote: > > Hi, > > While calling the method destory() on the StandardContext directly, > it > > seems that the method destoryInternal() is called twice i

Re: destory method is called twice while the child is destoryed directly

On 27/10/2010 06:43, Ivan wrote: > Hi, > While calling the method destory() on the StandardContext directly, it > seems that the method destoryInternal() is called twice in the > LifecycleMBeanBase, the two stacktraces are below : > a. LifecycleMBeanBase.unregister(ObjectName) line: 191 >

destory method is called twice while the child is destoryed directly

Hi, While calling the method destory() on the StandardContext directly, it seems that the method destoryInternal() is called twice in the LifecycleMBeanBase, the two stacktraces are below : a. LifecycleMBeanBase.unregister(ObjectName) line: 191 LifecycleMBeanBase.destroyInternal()