Strict Session Timeouts erros.

Sun ONE Web Server 6.1SP5 B06/23/2005 22:22

[WARNING] Servlet[RewriterServlet @769307]: The servlet "RewriterServlet" is NOT enforcing strict session timeouts . Be sure to turn on strict session timeout handling or implement the onSession Timeout() event before putting this application into production.

info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[AMBaseServlet@1 7361481]: The servlet "AMBaseServlet" is NOT enforcing strict session timeouts.Be sure to turn on strict session timeout handling or implement the onSessionTi meout() event before putting this application into production.

info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[SMServlet@80118 94]: The servlet "SMServlet" is NOT enforcing strict session timeouts. Be sureto turn on strict session timeout handling or implement the onSessionTimeout() e vent before putting this application into production.

info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[UMServlet@39963 31]: The servlet "UMServlet" is NOT enforcing strict session timeouts. Be sureto turn on strict session timeout handling or implement the onSessionTimeout() e vent before putting this application into production.

How do I solve these warnings.

[1262 byte] By [azfara] at [2007-11-26 13:46:06]
# 1
you are probably using the jes4 version of web server along with Access Manager and Portal. Web Server does not spit out this error. You will need to work with Portal team to resolve this.by the way, with the upcoming JES5 - this issue seems to have been resolved.
chilidevelopera at 2007-7-8 1:21:00 > top of Java-index,Web & Directory Servers,Web Servers...
# 2

These messages are generated as a result of the Portal Server administration console implementation using the Sun ONE Application Framework, aka JATO. Those modules are not implementing the required onSessionTimeout method however, since the AM/PS admin console really doesn't use the HttpSession to do session management (it uses the AM SSOToken instead), the lack of this implementation is not a problem.

These messages are gone in the PS 7 release which is part of the next JES release because PS no longer uses JATO anymore for the console.

The developer's guide for JATO is at: http://docs.sun.com/app/docs/doc/817-4359 It describes the enforceStrictSessionTimeout flag that may control these warning messages. The following in the portal web.xml may suppress them (I'm not sure about this):

<context-param>

<param-name>jato:enforceStrictSessionTimeout</param-name>

<param-value>true</param-value>

</context-param>

Tom.Mueller@sun.coma at 2007-7-8 1:21:00 > top of Java-index,Web & Directory Servers,Web Servers...