tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 50168] destory method is called twice while the child is destoryed directly
Date Tue, 02 Nov 2010 02:08:56 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=50168

--- Comment #3 from Ivan <xhhsld@gmail.com> 2010-11-01 22:08:52 EDT ---
(In reply to comment #1)
> When StandardContext is destroyed is destroys assets is manages which also have
> their own lifecycle. So you might be seeing those log messages. (Most likely
> StandardManager)
> 
> Please reopen with more proof if this diagnosis is wrong.

Not sure I understand your comments clearly. From the stack trace, while
destorying the standcontext directly, it will check check whether its parent is
null, if not, it will call the parent.removeChild() method, but removeChild
method also try to destory the child. (As it does not known who calls the
method).
I will reopen the it, and try to attach a patch file.
thanks.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message