jakarta-watchdog-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vanitha.venkatraman" <Vanitha.Venkatra...@eng.sun.com>
Subject Re: OK, What Gives?
Date Fri, 01 Dec 2000 07:07:21 GMT
So, this is what is happening:

With Tomcat-4.0-20001129 and Tomcat-4.0-20001130 builds, the Watchdog tests do
not run, they hang for all targets (all, jsp, jsp-xml, gtestservlet). I could
execute the jsps manually from the browser. So, the war files get deployed on
the server. But the tests do not work from GTest. No idea why this is
happening. GTest has not changed in a while.

I went as far behind as jakarta-tomcat-4.0-20001103 build and all the Watchdog
tests WORK. They execute for all targets.

> I'm trying to get the "jakarta-watchdog-4.0" tests to run against Tomcat 4.0,
> and am not having much luck.  I did a "./build.sh dist" build of Watchdog,
> copied the WAR files to Tomcat's webapps directory, and started Tomcat. 
> Then I did
>     cd <<jakarta-home>>/dist/watchdog/bin
>     ./watchdog.sh all
> and get the following output:
>     Guessing WATCHDOG_HOME from watchdog.sh to ./..
>     Setting WATCHDOG_HOME to ./..
>     Using classpath:
> ./../lib/client.jar:./../lib/testdriver.jar:./../lib/moo.jar:./../lib/ant.jar:./usr/locall/jdk1.2.2/lib/tools.jar:/usr/local/jdk1.2.2/lib/classes.zip
>     Buildfile: ./../conf/jsp-gtest.xml
>     jsp-test:
> and it just hangs.  Running netstat shows that there is an established TCP
> connection on port 8080, so apparently the client has actually contacted the
> server, but there's no output at all.
> Any theories on what is going on?
> Craig McClanahan

View raw message