tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amy Roh <amyroh...@yahoo.com>
Subject Re: [5.0.2] New tag at the end of the week ?
Date Tue, 22 Apr 2003 01:45:56 GMT
Hi Remy, Is the NPE in Mapper fixed with your commit?  I can't reproduce it. Thanks,Amy

Remy Maucherat <remm@apache.org> wrote:Costin Manolache wrote:
> Remy Maucherat wrote:
>>>BTw, part of the preparation for releasing j-t-c I tested it against
>>>tomcat3.3, tomcat-4.0.6 and 4.1.24. All 3 seem to be working fine.
>>
>>Cool ! I definitely haven't been spending time checking 4.0.6, but since
>>it's the same code as 4.1.x with a few additional security checks, I
>>think it's supposed to be ok.
> 
> 
> We could use the "standalone" j-t-c as a dependency in 50. 
> 
> I know we don't agree on the "update jars" mechanism, but if j-t-c can
> work without (major:-) problems with 3.3, 4.0, 4.1 and 5.0 I think we 
> could assume it'll work for 5.0.3, etc. 
> I don't want to reopen this again - but modular and incremental releases can
> simplify a lot of things.

The problem is that "small" "incremental" changes are never properly tested.

Ex: When I wake up this morning, look at the commits (where the messages 
imply they're all safe changes), update everything, ant clean; ant, I get:
GRAVE: Une exception ou une erreur s''est produite dans le conteneur 
durant le traitement de la requ?te
java.lang.NullPointerException
at org.apache.tomcat.util.http.mapper.Mapper.find(Mapper.java:865)
at 
org.apache.tomcat.util.http.mapper.Mapper.internalMap(Mapper.java:502)
at org.apache.tomcat.util.http.mapper.Mapper.map(Mapper.java:474)
at 
org.apache.coyote.tomcat5.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:301)
at 
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:197)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:630)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:463)
at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:568)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:631)
at java.lang.Thread.run(Thread.java:534)

Apparently some change caused the default host name to not properly get 
set in the mapper, but the point is that small changes are the biggest 
problems for regressions.

Remy


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org



---------------------------------
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message