Summary: | 404 due to NullPointer in Mapper.java | ||
---|---|---|---|
Product: | Tomcat 8 | Reporter: | mmikolajczyk |
Component: | Catalina | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | P2 | ||
Version: | 8.0.29 | ||
Target Milestone: | ---- | ||
Hardware: | PC | ||
OS: | Linux |
Description
mmikolajczyk
2016-03-31 11:11:06 UTC
Certainly this sort of occurrence is not going to be logged. Besides concurrent recycling, I don't really see what could cause it as mappingData.context is set right before calling internalMapWrapper, so it's really something that is up to you to debug. IMO this should be INVALID until you demonstrate some reasonably legitimate course of action that leads to the NPE. 1. Sample configuration / steps to reproduce the issue = ? 2. Diffs are preferred in Unified Diff format http://tomcat.apache.org/bugreport.html#How_to_submit_patches_and_enhancement_requests Looking at 8.0.x Mapper.java, I think that in both mentioned places mappingData.context.getMapperContextRootRedirectEnabled() has be replaced with obtaining the context from ContextVersion object. Both places have it, so I see no reason why context is retrieved from mappingData. A test case is TBD. Ok, so mappingData.context -> contextVersion.object. No problem. Since I don't see how mappingData.context becomes null, mappingData.wrapper probably also gets reset as well which will randomly mess up the mapping algorithm. Ok, I applied this for 9M5, 8.5.1, 8.0.34. |