I have seen this as well (with an older version of Tomcat and the
latest) but thought there was a thread about this a few weeks back ( I
am having problems finding it right now). I am running an older version
of the TDK though. Are you seeing this in the latest release (2.1) or
are you using straight from CVS?
I would like to figure this one out as well, since having to 'cleanup'
the container isn't very fun. From empirical evidence it only occurs
with my container if there was an 'error' or 'exception' - say I start
the container and then request a template that doesn't exist.
ian
Colm McCartan wrote:
>
> Hello all,
>
> I've built several test applications with the newapp framework and have noticed
> the following problem with all of them (apart from newapp itself) across both
> Catalina and Tomcat 3.2.1 (which I use for its performance). When the container
> unloads the servlet either to close down or because of a recompile (with
> reloadable=true in my server.xml) an exception is thrown which stops the
> container correctly closing and restarting. Heres some of the log:
>
> 2001-06-12 03:32:15 - ThreadPool: Caught exception executing
> org.apache.tomcat.service.TcpWorkerThread@40afb9, terminating thread -
> java.lang.StackOverflowError
> at org.apache.turbine.services.BaseServiceBroker.getServiceInstance
> (BaseServiceBroker.java:311)
> at org.apache.turbine.services.BaseServiceBroker.getService
> (BaseServiceBroker.java:260)
> at org.apache.turbine.services.TurbineServices.notice
> (TurbineServices.java:344)
> at org.apache.turbine.services.BaseServiceBroker.getService
> (BaseServiceBroker.java:267)
> at org.apache.turbine.services.TurbineServices.notice
> (TurbineServices.java:344)
> at org.apache.turbine.services.BaseServiceBroker.getService
> (BaseServiceBroker.java:267)
> at org.apache.turbine.services.TurbineServices.notice
> (TurbineServices.java:344)
> at org.apache.turbine.services.BaseServiceBroker.getService
> (BaseServiceBroker.java:267)
> at org.apache.turbine.services.TurbineServices.notice
> (TurbineServices.java:344)
> at org.apache.turbine.services.BaseServiceBroker.getService
> (BaseServiceBroker.java:267)
>
> These last two calls (between BaseServiceBroker.getService and
> TurbineServices.notice) are clearly in a loop which generates the StackOverflow
> as these two fill the rest of the file...
>
> Has anyone experienced this and found a workaround or know what i may have
> managed to break?
>
> cheers,
> colm
> ................................................................
> colm mccartan
> panasonic owl uk
> [EMAIL PROTECTED]
> (44) 131 561 1035
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
+----------------------------------+
[EMAIL PROTECTED]
+----------------------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
