After looking at this I found out what the problem is but I am not sure 
exactly how to go about fixing it.  

When BaseServiceBroker.shutdownServices() is called it starts shutting down 
services with the mapping keys looking like the following:

servicename:PullService
servicename:MimeTypeService
servicename:MapBrokerService
servicename:PoolBrokerService
servicename:LocalizationService
servicename:XmlRpcService
servicename:ServletService
servicename:TamboraRulesService
servicename:SecurityService
servicename:UniqueIdService
servicename:LoggingService
servicename:ResourceService
servicename:FactoryService
servicename:UploadService
servicename:VelocityService
servicename:TemplateService
servicename:SchedulerService
servicename:GlobalCacheService
servicename:AssemblerBrokerService
servicename:RunDataService
servicename:PoolService

Once the LoggingService gets shutdown,  it looks like the shutdown loop stops 
and the rest of the services are never shutdown.  This includes the Scheduler 
service.  So then, the Scheduler is still running for a short period of time 
and it errors out when it tries to create a log/notice entry when it creates 
a new worker.

Is this the way that it is supposed to work or should all of the other 
services shutdown methods get called as well?

John


On Tuesday 22 May 2001 03:54, John Thorhauer wrote:
> I am testing the TurbineNonPersistentSchedulerService for the 2.1b2 release
> and am getting the following error when I shutdown tomcat:
>
> java.lang.StackOverflowError
>         at java.lang.String.getChars(String.java:545)
>         at java.lang.StringBuffer.append(StringBuffer.java:393)
>         at java.lang.StringBuffer.<init>(StringBuffer.java:131)
>         at
> org.apache.turbine.services.BaseServiceBroker.getService(BaseServiceBroker.
>java:267) at
> org.apache.turbine.services.TurbineServices.notice(TurbineServices.java:345
>) at
> org.apache.turbine.services.BaseServiceBroker.getService(BaseServiceBroker.
>java:267) at
> org.apache.turbine.services.logging.TurbineLogging.getService(TurbineLoggin
>g.java:78) at
> org.apache.turbine.services.logging.TurbineLogging.getLogger(TurbineLogging
>.java:104) at
> org.apache.turbine.services.schedule.WorkerThread.<init>(WorkerThread.java:
>91) at
> org.apache.turbine.services.schedule.TurbineSchedulerService$MainLoop.run(T
>urbineSchedulerService.java:374) at java.lang.Thread.run(Thread.java:475)
>
> Any ideas on this.
>
> John

-- 
********************************
** John Thorhauer
** [EMAIL PROTECTED]
** take a look at:
**  http://tambora.zenplex.org
**  http://www.zenplex.org
**  http://www.zenplex.com
********************************


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to