Hi Vincent,

The log4j jar is in the serverpath and the logging is working fine.
I think the fact that the tests are successful in debugmode the only reason is 
that the processing of
the cactustests are more slowly, because the output writing takes a long time.
If the cactustest are processed more quickly on info level logging the most 
tests are failed.
I don't know is the reason cactus or ATG Dynamo 6.4 ?

Any other ideas ?

Thanks,
Andre

-----Original Message-----
From: Vincent Massol [mailto:[EMAIL PROTECTED] 
Sent: 21 February 2005 13:05
To: 'Cactus Users List'
Subject: RE: Problems to run all 249 cactus tests


Hi Andre,

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: lundi 21 f�vrier 2005 13:22
> To: [email protected]
> Subject: Problems to run all 249 cactus tests
> 
> Hi,
> 
> I have a problem to run all my 249 cactus tests togehter.
> I use Ant to run the tests with Log4j on ATG Dynamo 6.4 AppServer. I 
> had an issues to invalidate sessions which is fixed with the 
> DynaCactus (Which extends Cactus and set Session.invalidate in the 
> Redirector Servlet explicit) http://www.onwhichsubject.com/DynaCactus/
> If I run cactus with Log4j debug level I get 11 Errors and 60 
> Failures. If I run cactus with Log4j info level I get 204 Errors and 
> 15 Failures. Each of the 204 Errors is a
> org.apache.cactus.util.ChainedRuntimeException: Failed to get the test 
> result at [http://localhost:80/ServletRedirector.dyn]
> The test are ok, because they are valid in debug log level. By using 
> JUnitEE I can run all 249 test without Runtime Exception (11 Errors 
> and 60 Failures) Which impact has the different log level by running 
> cactus tests ? Can anyone help me to fix this problem ?

It's not supposed to have any effect of course. I can't think of any apart from 
the fact that you may have configured Cactus to use Log4j and that you've 
forgotten to add the log4j jar to your server side classpath...

-Vincent




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to