You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by ru...@us.ibm.com on 2000/06/29 21:14:36 UTC

Watchdog JSP tests


I must be doing something stupid.

Over the past several weeks, I have tried to run the Watchdog JSP tests and
they have all failed for me.  Each time I have tried to debug it, I've been
stumped or distracted by other things.  Today I actually stayed home from
work to see if I could get past it, and having spent most of the day
without any luck, now I am asking for help...

Context: latest from CVS, on Win2K.  Following the instructions in
jakarta-watchdog README.

The servlet tests pass.

Every JSP test fails.  Here's an example:
   Ctx( 127.0.0.1: ): Status Handler: 404 req=R(  +
   /jsp-tests/jsp/HelloWorld.jsp +  null)
   Ctx( 127.0.0.1: ): Handler tomcat.notFoundHandler(null/null)
   tomcat.notFoundHandler

The JSP examples all work.

Suggestions?

- Sam Ruby



Re: Watchdog JSP tests

Posted by "Craig R. McClanahan" <Cr...@eng.sun.com>.
rubys@us.ibm.com wrote:

> I must be doing something stupid.
>
> Over the past several weeks, I have tried to run the Watchdog JSP tests and
> they have all failed for me.  Each time I have tried to debug it, I've been
> stumped or distracted by other things.  Today I actually stayed home from
> work to see if I could get past it, and having spent most of the day
> without any luck, now I am asking for help...
>
> Context: latest from CVS, on Win2K.  Following the instructions in
> jakarta-watchdog README.
>
> The servlet tests pass.
>
> Every JSP test fails.  Here's an example:
>    Ctx( 127.0.0.1: ): Status Handler: 404 req=R(  +
>    /jsp-tests/jsp/HelloWorld.jsp +  null)
>    Ctx( 127.0.0.1: ): Handler tomcat.notFoundHandler(null/null)
>    tomcat.notFoundHandler
>
> The JSP examples all work.
>
> Suggestions?
>

I was successful running Watchdog against Tomcat 3.2dev as of yesterday morning
(once the compile errors were fixed).  My usual process is:
* Build Watchdog with the "dist" target
* Go to $JAKARTA_HOME/dist/watchdog/webapps
* Copy the two war files to Tomcat's webapps dir
* Start Tomcat
* Go to $JAKARATA_HOME/dist/watchdog/bin
* Execute "./watchdog.sh servlet > servlet-tests.log"
* Execute "./watchdog.sh jsp > jsp-tests.log"

I will try the current Tomcat code later today.  You should find one JSP test
failure (and there's going to be another one as soon as I fix the test; it's
the same issue in Tomcat).  The failing test is:

    /jsp-tests/jsp/engine/PageContext/positiveForward.jsp

where the test (correctly) expects <jsp:forward> to have cleared the data
buffer.  I've stared at the Tomcat code for a long time and cannot figure out
why it is failing -- it appears that the resetBuffer() method is getting called
appropriately.

>
> - Sam Ruby
>

Craig



Re: Watchdog JSP tests

Posted by Costin Manolache <co...@eng.sun.com>.
>
> Context: latest from CVS, on Win2K.  Following the instructions in
> jakarta-watchdog README.
>
> The servlet tests pass.
>
> Every JSP test fails.  Here's an example:
>    Ctx( 127.0.0.1: ): Status Handler: 404 req=R(  +
>    /jsp-tests/jsp/HelloWorld.jsp +  null)
>    Ctx( 127.0.0.1: ): Handler tomcat.notFoundHandler(null/null)
>    tomcat.notFoundHandler
>
> The JSP examples all work.

I have all but one watchdog test running, and most tomcat tests (
except few where 404 is returned instead of 400 or redirect instead of
content - the behavior changed a bit )