On 09/03/2011 15:47, Jess Holle wrote: > Well the exception when invoking destroy() directly is: > > 2011-03-09 09:28:16,238 ERROR [RMI TCP Connection(13)-10.196.0.84] > org.apache.tomcat.util.modeler.BaseModelMBean - Exception invoking > method destroy > org.apache.catalina.LifecycleException: An invalid Lifecycle transition > was attempted ([before_destroy]) for component [Connector[AJP/1.3-8008]] > in state [STARTED] <snip/> > I can kind of understand this -- destroy() does not auto-invoke stop() > and is complaining that the incoming state is not what it expects.
Yes, that is as expected. See: http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/Lifecycle.html > When invoking stop() and then destroy() the destroy() succeeds > [something I missed in my original post], but an exception is still logged: > > 2011-03-09 09:29:21,939 ERROR [RMI TCP Connection(21)-10.196.0.84] > org.apache.catalina.core.StandardService - Failed to stop connector > [Connector[AJP/1.3-8010]] > org.apache.catalina.LifecycleException: An invalid Lifecycle transition > was attempted ([before_stop]) for component [Connector[AJP/1.3-8010]] in > state [DESTROYING] > at > org.apache.catalina.util.LifecycleBase.invalidTransition(LifecycleBase.java:386) Hmm. That looks like a bug. Let me go look at the code... Yep. Fixed in http://svn.apache.org/viewvc?rev=1079930&view=rev Will be in 7.0.11 onwards. > What's more troublesome to me is that with every approach I've tried at > least 1 request still gets through. In some cases this request works > normally. In other cases the request gets a 200 and no content or a > 404. After this initial request things behave more appropriately -- > with the particulars depending on what I try to stop. Let me do some more testing in this area. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
