You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-user@jakarta.apache.org by "Cvoro, Ozrenko" <Oz...@CIBC.com> on 2005/02/18 21:44:36 UTC
Cactus-13-1-7 and Weblogic 8.1
Hi all,
I have been using for a while Cactus on different Weblogic versions and now
trying to use it on WL 8.1. Well, I thought that I have everything set up
correctly (right jars on a classpath, property files on classpath) but I
still can't get rid of this annoying message:
Failed to get the test results at
[http://localhost:7001/HibernateTrial/ServletRedirector]
org.apache.cactus.util.ChainedRuntimeException: Failed to get the test
results at [http://localhost:7001/HibernateTrial/ServletRedirector] at
org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_ar
oundBody0(DefaultHttpClient.java:92) at
org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_ar
oundBody1$advice(DefaultHttpClient.java:306) at
org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest(De
faultHttpClient.java) at
org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runWebT
est(HttpProtocolHandler.java:159) at
org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest
_aroundBody0(HttpProtocolHandler.java:80) at
org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest
_aroundBody1$advice(HttpProtocolHandler.java:306) at
org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest
(HttpProtocolHandler.java) at
org.apache.cactus.internal.client.ClientTestCaseCaller.runTest(ClientTestCas
eCaller.java:144) at
org.apache.cactus.internal.AbstractCactusTestCase.runBareClient(AbstractCact
usTestCase.java:215) at
org.apache.cactus.internal.AbstractCactusTestCase.runBare(AbstractCactusTest
Case.java:133)org.apache.cactus.internal.client.ParsingException: Not a
valid response [404 Not Found] at
org.apache.cactus.internal.client.connector.http.DefaultHttpClient.
I went through my web.xml and it looks like this:
<web-app>
<servlet>
<servlet-name>ServletRedirector</servlet-name>
<servlet-class>org.apache.cactus.server.ServletTestRedirector</servlet-class
>
</servlet>
<servlet-mapping>
<servlet-name>ServletRedirector</servlet-name>
<url-pattern>/ServletRedirector</url-pattern>
</servlet-mapping>
</web-app>
my cactus.propertis file looks like:
cactus.contextURL=http://localhost:7001/HibernateTrial
cactus.servletRedirectorName=ServletRedirector
The application is deployed (directory), I have needed jars on the client
and server but still this message is puzzling me. I went through almost all
relevant emails on this subject but still no luck.
Is there any other place I should look?
Thanks
Oz
RE: Cactus-13-1-7 and Weblogic 8.1
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Oz,
> -----Original Message-----
> From: Cvoro, Ozrenko [mailto:Ozrenko.Cvoro@CIBC.com]
> Sent: vendredi 18 février 2005 21:45
> To: 'cactus-user@jakarta.apache.org'
> Subject: Cactus-13-1-7 and Weblogic 8.1
>
> Hi all,
>
> I have been using for a while Cactus on different Weblogic versions and
> now
> trying to use it on WL 8.1. Well, I thought that I have everything set up
> correctly (right jars on a classpath, property files on classpath) but I
> still can't get rid of this annoying message:
>
> Failed to get the test results at
> [http://localhost:7001/HibernateTrial/ServletRedirector]
>
> org.apache.cactus.util.ChainedRuntimeException: Failed to get the test
> results at [http://localhost:7001/HibernateTrial/ServletRedirector] at
[snip]
> Case.java:133)org.apache.cactus.internal.client.ParsingException: Not a
> valid response [404 Not Found] at
> org.apache.cactus.internal.client.connector.http.DefaultHttpClient.
This 404 means that the Cactus client side was not able to call the Server
redirector. It probably means that somehow your mapping is not correct
(although it does look fine here). Try starting your webapp, open a browser
and type:
http://localhost:7001/HibernateTrial/ServletRedirector
?Cactus_Service=RUN_TEST
It should return a blank page with no error.
You can also try turning on Cactus logging and check the log file for the
error.
[snip]
-Vincent