> After executing the test the SMTP thread is still busily running
> consuming as much CPU as it can get.
The following fragment of the SMTP log is typical:
[DEBUG ] (james.smtp): Command received:
This is bad already. Where is the command? We just changed the read code,
but the original code was "return inReader.readLine().trim();" and I don't
think the replacement is broken.
> [DEBUG ] (james.smtp): Calling reset() default Worker #1017
> [DEBUG ] (james.smtp): Calling reset() default Worker #1423
> [DEBUG ] (james.smtp): Calling reset() default Worker #1652
> [DEBUG ] (james.smtp): Calling reset() default Worker #214
This is also not good. Those numbers are related to threading. Something
feels truely fouled.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
