tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Downey <steve.dow...@netfolio.com>
Subject RE: Tester results
Date Sun, 18 Mar 2001 16:48:34 GMT
Yes, it's a recent version, pulled from CVS shortly after you checked in the
fix to tester for the changes to the Filter API.
I ran all of the tests, using bin/tester.bat, and I have added manager to
the list of tomcat roles.

I don't see anything that looks odd in the logs. Here's the section from
localhost_log
2001-03-18 11:37:02 Session01: init
2001-03-18 11:37:02 Session02: init
2001-03-18 11:37:02 Manager: restart: Reloading web application at '/tester'
2001-03-18 11:37:02 StandardContext[/tester]: Reloading this Context has
started
2001-03-18 11:37:02 Jndi02: destroy
2001-03-18 11:37:02 GetParameterMap00: destroy
2001-03-18 11:37:02 Jndi01: destroy
2001-03-18 11:37:02 GetHeaders01: destroy
2001-03-18 11:37:02 SetBufferSize01: destroy
2001-03-18 11:37:02 Include02: destroy
2001-03-18 11:37:02 Include01: destroy
2001-03-18 11:37:02 SetLocale01: destroy
2001-03-18 11:37:02 GetQueryString01: destroy
2001-03-18 11:37:02 GetParameter01: destroy
2001-03-18 11:37:02 Forward01: destroy
2001-03-18 11:37:02 Include02a: destroy
2001-03-18 11:37:02 GetInputStream01: destroy
2001-03-18 11:37:02 Resources04: destroy
2001-03-18 11:37:02 Session02: destroy
2001-03-18 11:37:02 Resources03: destroy
2001-03-18 11:37:02 Authentication02: destroy
2001-03-18 11:37:02 Session01: destroy
2001-03-18 11:37:02 Resources02: destroy
2001-03-18 11:37:02 Reset01: destroy
2001-03-18 11:37:02 Authentication01: destroy
2001-03-18 11:37:02 Resources01: destroy
2001-03-18 11:37:02 Aggregate02: destroy
2001-03-18 11:37:02 Aggregate01: destroy
2001-03-18 11:37:02 Manager[/tester]: Seeding random number generator class
java.security.SecureRandom
2001-03-18 11:37:02 Manager[/tester]: Seeding of random number generator has
been completed
2001-03-18 11:37:02 StandardContext[/tester]: Reloading this Context is
completed
2001-03-18 11:37:02 Session03: init
2001-03-18 11:37:02 Session01: init
2001-03-18 11:37:02 Session02: init
2001-03-18 11:37:02 Manager: restart: Reloading web application at '/tester'
2001-03-18 11:37:02 StandardContext[/tester]: Reloading this Context has
started
2001-03-18 11:37:02 Session03: destroy
2001-03-18 11:37:02 Session02: destroy
2001-03-18 11:37:02 Session01: destroy
2001-03-18 11:37:02 Manager[/tester]: Seeding random number generator class
java.security.SecureRandom
2001-03-18 11:37:02 Manager[/tester]: Seeding of random number generator has
been completed
2001-03-18 11:37:02 StandardContext[/tester]: Reloading this Context is
completed
2001-03-18 11:37:02 Session03: init

and from localhost_access_log
127.0.0.1 - - [18/Mar/2001:11:37:01 -0500] "GET /tester/Session01 HTTP/1.1"
200 29
127.0.0.1 - - [18/Mar/2001:11:37:01 -0500] "GET /tester/Session02 HTTP/1.1"
200 29
127.0.0.1 - tomcat [18/Mar/2001:11:37:01 -0500] "GET /manager/reload
HTTP/1.1" 200 67
127.0.0.1 - - [18/Mar/2001:11:37:01 -0500] "GET /tester/Session03 HTTP/1.1"
200 84
127.0.0.1 - - [18/Mar/2001:11:37:01 -0500] "GET /tester/WrappedSession01
HTTP/1.1" 200 320
127.0.0.1 - - [18/Mar/2001:11:37:01 -0500] "GET /tester/WrappedSession02
HTTP/1.1" 200 262
127.0.0.1 - tomcat [18/Mar/2001:11:37:02 -0500] "GET /manager/reload
HTTP/1.1" 200 67
127.0.0.1 - - [18/Mar/2001:11:37:02 -0500] "GET /tester/WrappedSession03
HTTP/1.1" 200 385

	-SMD

> -----Original Message-----
> From: Craig R. McClanahan [mailto:craigmcc@apache.org]
> Sent: Saturday, March 17, 2001 11:18 PM
> To: tomcat-dev@jakarta.apache.org (E-mail)
> Subject: Re: Tester results
> 
> 
> 
> 
> On Sat, 17 Mar 2001, Steve Downey wrote:
> 
> > On Windows 2000 I'm getting failures on tester:
> > FAIL [GET /examples/..] java.io.FileNotFoundException:
> > http://localhost:8080/examples/ <http://localhost:8080/examples/> ..
> 
> This is a Tomcat 4.0 bug (Windows-specific).  It works (at least for
> me) on Linux.
> 
> > FAIL [GET /tester/Session03] Expected data 'Session03 
> PASSED', got data
> > 'Session03 FAILED - No existing session 
> 43687632F490000215A2A42615B6D472'
> > FAIL [GET /tester/WrappedSession03] Expected data 
> 'Session03 PASSED', got
> > data 'Session03 FAILED - No existing session
> > 11239215B4D7D0D5325638B61272F694'
> 
> Could you check your log files for me on this one?  It runs on both
> platforms for me.
> 
> I'm also assuming a couple of other things:
> * You are running the test suite as a whole, or at least the
>   entire "SessionTest" target -- as opposed to calling the
>   tests individually with a browser.  This is required because
>   the previous tests in the target are the ones that set up the
>   session.
> * You have modified your "conf/tomcat-users.xml" to ensure that
>   user "tomcat" is also in role "manager".  Otherwise, the context
>   reloads that the tester tries will not work.
> * You are running a recent build of Tomcat 4.0.  The beta 1 release
>   had some problems with saving and restoring sessions.
> 
> > FAIL [GET /tester/Xerces02] java.io.FileNotFoundException:
> > http://localhost:8080/tester/Xerces02
> > <http://localhost:8080/tester/Xerces02> 
> > FAIL [GET /tester/WrappedXerces02] java.io.FileNotFoundException:
> > http://localhost:8080/tester/WrappedXerces02
> > <http://localhost:8080/tester/WrappedXerces02> 
> >  
> 
> These two are specific to running under JDK 1.3 (including 
> the most recent
> JDK 1.3.0_02 downloads).  The underlying cause is our old 
> friend "package
> sealing violation" (Bugzilla bug report #1002), and I've been 
> fighting it
> all afternoon -- I'm not convinced it is going to be possible to work
> around this without shipping our own unsealed versions of the 
> JAXP parser
> :-(.
> 
> >  
> > On Linux I'm getting failures on Session03, 
> WrappedSession03, as well as
> > Xerces01 and WrappedXerces01
> >  
> > Both are JDK 1.3, 1.3.0-C on Windows and 1.3.0 on Linux.
> >  
> > Is this par, or a configuration or build problem.
> >  
> >  
> > 
> 
> Craig
> 
<><><><><><><><><><><><><><><><><><><><><>This
electronic mail transmission
may contain confidential information and is intended only for the person(s)
named.  Any use, copying or disclosure by any other person is strictly
prohibited.  If you have received this transmission in error, please notify
the sender via e-mail. <><><><><><><><><><><><><><><><><><><><><>

Mime
View raw message