On Sunday 04 January 2004 23:39, Stephen McConnell wrote:
> Problem was deployment timeout. For some reason James goes through the
> initial startup and (as far as cpu consumption is concerned) goes almost
> silent, then finally some activity about 30-45 seconds post deployment.
> To get things
Stephen McConnell wrote:
Niclas Hedhman wrote:
This has been committed to the HEAD, and will be part of the Merlin
3.3 release after some more testing.
Niclas:
I'm getting the following startup failure in James.
Is this related to the deployment timeout? If so I think we need to do
some wo
Niclas Hedhman wrote:
This has been committed to the HEAD, and will be part of the Merlin 3.3
release after some more testing.
Niclas:
I'm getting the following startup failure in James.
Is this related to the deployment timeout? If so I think we need to do
some work on the error message retur
Everyone,
I have taken away the creation of plenty of threads in Merlin, and have
attempted to put in a Deployment Timeout, i.e. If a component or a container
takes too long to deploy, the deployment subsystem will try to interrupt()
the deployment, and if that succeeds, throw a DeploymentExc
