Search

Your Notifications (0)

There are currently no notifications. You're all set!

Knowledge Base
ChemDraw and ChemOffice+ Products Signals Notebook E-Notebook and ChemBioOffice Enterprise Spotfire and Signals Spotfire Products Image Artist Spectrus, Percepta, Katalyst, Luminata and more
Downloads
Downloads
Community
Ideas Portal Product Basics
About Support
Legal Resources Support and Maintenance Plans Product Life Cycle Support News
Contact Support

'wp.events.RoutingSessionListener: HTTP session is about to be destroyed' logged in Spotfire server logs.

Kisiel, Pawel
  • Updated
Date Posted:
Product: TIBCO Spotfire®

Problem:

'wp.events.RoutingSessionListener: HTTP session is about to be destroyed' logged in Spotfire server logs.


Solution:

The following log snippets can be seen in Spotfire server log file (server.log) at multiple places specially when Spotfire server logs are in INFO mode: 

INFO 2019-09-25T15:15:52,060+0200 [] wp.events.RoutingSessionListener: HTTP session is about to be destroyed. Internal session id: 0eec2e1f1bf91e3bbce64afc48534d56
INFO 2019-09-25T15:15:52,060+0200 [] wp.events.RoutingSessionListener: HTTP session is about to be destroyed. Internal session id: a3cf8e4784a846a4b2f83613d1163f0a 
INFO 2019-09-25T15:15:52,060+0200 [] wp.events.RoutingSessionListener: HTTP session is about to be destroyed. Internal session id: 31ef7d634696e5653f6c837f2b258b69  
INFO 2019-09-25T15:15:52,060+0200 [] wp.events.RoutingSessionListener: HTTP session is about to be destroyed. Internal session id: 9eb19efa571e20d2477a0cb8ea0d5580  
INFO 2019-09-25T15:15:52,060+0200 [] wp.events.RoutingSessionListener: HTTP session is about to be destroyed. Internal session id: 4c906f5e897228215d62cc3128ad27b0

This article describes what is the meaning of these log snippets and why it get logged in Spotfire server logs.
  • The 'RoutingSessionListener' mentioned in log snippet performs certain cleanup/shutdown actions that needs to take place when/before HTTP session is destroyed. A session may either be destroyed due to the user logging out, or due to an idle timeout. 
  • Spotfire server's access logs (<Spotfire Server Install>\tomcat\logs\access.log) should show if the users are actually logging out. You can refer attached access.log file for actual user(nmomin@apacanalytics.lab) logout entry.  If this is not the case and if the number of expiring sessions is higher than expected then one need to start by looking at load balanacers or such in front of the Spotfire server, perhaps session cookies get lost or perhaps the load balancer doesn't properly maintain session affinity so that requests within the same session are routed to different servers (resulting in new sessions being created).

Related articles

Comments

0 comments

Article is closed for comments.