Return-Path:
not a valid response
error message. What does it
+ mean ?http://localhost:8080/webapp/ServletRedirector?Cactus_Service=RUN_TEST
.
Of course replace webapp
by your webapp context and
replace the port by the one you're using.
+
+ When I run my Cactus test, I'm getting the following : +
+ + + ++ It means that Cactus could not connect to the server side properly. + There could several reasons for this : a valid Redirector URL but + not pointing to the Redirector, a secured resource, etc. +
+
+ To easiest way to diagnosis the problem is to enable Cactus logging
+ (see the Configuration Howto
+ for how to do this). The cactus client log
+ (cactus_client.log
will clearly give the error).
- A default log_client.properties
is already provided
- in the cactus.jar
jar. It is used for
- configuring Log4j, which is the logging framework used by Cactus
- to log debug information.
+ This file is used for configuring Log4j, which is the logging
+ framework used by Cactus to log debug information. A sample
+ log_client.properties
is provided in the Cactus sample
+ application.
+
+ You should put this file in your client side classpath if you wish + to enable logging.
If the Log4j jar is not present on the client side classpath, @@ -300,7 +304,7 @@
- The default log_client.properties
is :
+ The sample log_client.properties
is :
- The default log_server.properties
is :
+ The sample log_server.properties
is :
- If you wish to define another file name and location or other
- logging parameter, just provide your own
- log_server.properties
file (it has to be named this
- way) and put in the WEB-INF/classes
directory of
- your webapp (and hope that the webapp classloader of your server
- picks up the files in WEB-INF/classes
before the ones
- in WEB-INF/lib
, where cactus.jar
- is located ... :) I don't know if this is part of the
- specification). Alternatively, edit the file in
- cactus.jar
!
-
+ Link + | +KaCoMa |