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 operational I've set a 60 sec deployment timeout and > things are working fine.
Changed by the yet-to-be-tested kernel.xml Parameters, or by updating the source code's default value?? > Noel - does this sound normal/expected? Typical component behaviour. Aggressive allocation of resources. > p.s. Have update the deployment exceptions to provide information about > the time value associated with the fail condition. Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
