not really... 180s iirc

It did look like that 2 teamcity apps were running. And if the CPU is
hogged by the teamcity agent, then starting might take longer...

Martijn

On Sun, Nov 8, 2009 at 9:38 PM, Johan Compagner <[email protected]> wrote:
> there is a script running that looks if tomcat is running ok and if not it
> will terminate the process and starts it over
> it does the check 400 seconds but if tomcat doesnt restart before that then
> it will constantly restart it..
>
> But is it really taking that much time to up all the webapps? phh
>
>
> On Sun, Nov 8, 2009 at 19:54, Martijn Dashorst
> <[email protected]>wrote:
>
>> Wicketstuff constantly reboots the tomat server... causing the 503, a
>> quick glance at the logs doesn't show anything special...
>>
>> Martijn
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.4 increases type safety for web applications
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
>>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0

Reply via email to