Mantis Bugtracker

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0005521 [Resin] crash always 09-07-13 01:55 09-26-13 11:25
Reporter arjan_tijms View Status public  
Assigned To ferg
Priority normal Resolution fixed  
Status closed   Product Version 4.0.36
Summary 0005521: cookie-config and tracking-mode not supported by Resin
Description A web.xml file for Servlet 3.0, containing the following content will cause a fatal crash in Resin 4.0.36

<?xml version="1.0" encoding="UTF-8"?>
<web-app version="3.0" xmlns="" [^]
    xmlns:xsi="" [^]
    xsi:schemaLocation=" [^]" [^]

The error reported is:

{resin-port-8080-48} WEB-INF/web.xml:129: <cookie-config> is an unexpected tag (parent <session-config> starts at 127).
                       127: <session-config>
                       129: <cookie-config>
                       130: <http-only>true</http-only>
                       131: </cookie-config>
                       <session-timeout xmlns=""> [^] is expected,
                       or </session-config> may close.

This is of course not correct. <cookie-config> is perfectly valid to be at that location. The particular web.xml works on every other Servlet 3.0 container (JBoss EAP 6.1, GlassFish 3.1.22, TomEE 1.5.2, Liberty 8.5.5, WebLogic 12.1.2, etc etc).

Programmatically setting this in a ServletContainerInitializer doesn't work either. The following code will thrown an exception in Resin 4.0.36:

Set<SessionTrackingMode> trackingModes = new HashSet<SessionTrackingMode>();

The exception is:

 {resin-53} Could not set session config
                      java.lang.UnsupportedOperationException: unimplemented
                          at com.caucho.server.webapp.ServletContextImpl.setSessionTrackingModes(

The same code however works in every other Servlet 3.0 container. Since these methods are in the official Java EE API, I guess they should be implemented (apparently the TCK did not test these particular ones?)
Additional Information
Attached Files

- Relationships

- Notes
09-26-13 11:25


The API missing from the TCK is a surprise (although it's almost always the case that the TCK has some holes.)

The XML is less of a surprise, because it's a heavier-weight test to check XML than the APIs, and so the TCK does less of that. The XML testing is generally more of our responsibility.

- Issue History
Date Modified Username Field Change
09-07-13 01:55 arjan_tijms New Issue
09-26-13 11:25 ferg Note Added: 0006326
09-26-13 11:25 ferg Assigned To  => ferg
09-26-13 11:25 ferg Status new => closed
09-26-13 11:25 ferg Resolution open => fixed
09-26-13 11:25 ferg Fixed in Version  => 4.0.38

Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed.
26 unique queries executed.
Powered by Mantis Bugtracker