Serge Knystautas wrote:
We have a fledging group of tests for both performance and functionality testing... if you can try to run those against your mod'd version as well, that'd be great.
Serge:
I had to update the DeliveryTest.java source (replacement of all assert( boolean ) statements with assertTrue( boolean ) due to conflict with JDK 1.4 assert statement - aside from that the test ran without problem. I'm running under the default out-of-the-box configuration (file system based storage). However, I know I'm not quite out of the woods just jet. 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:
[DEBUG ] (james.smtp): Command received:
[DEBUG ] (james.smtp): Sent: 500 home Syntax error, command unrecognized:
[DEBUG ] (james.smtp): Sent: 500 home Syntax error, command unrecognized:
[DEBUG ] (james.smtp): Command received:
[DEBUG ] (james.smtp): Sent: 500 home Syntax error, command unrecognized:
[DEBUG ] (james.smtp): Sent: 500 home Syntax error, command unrecognized:
[DEBUG ] (james.smtp): Sent: 500 home Syntax error, command unrecognized:
[DEBUG ] (james.smtp): Command received:
[DEBUG ] (james.smtp): Command received:
With occasional bursts of:
[DEBUG ] (james.smtp): Command received:
[DEBUG ] (james.smtp): Sent: 500 home Syntax error, command unrecognized:
[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
[DEBUG ] (james.smtp): Calling reset() default Worker #1309
[DEBUG ] (james.smtp): Calling reset() default Worker #261
I'm presuming that this is not normal behaviour.
Any suggestions?
Cheers, Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
