Add some customer-facing logging about when web applications either are or are not instrumented for clustered session.

Type: New Feature
Status: Closed
Priority: 2 Major
Resolution: Fixed
Component/s: Sessions
Labels:

Assignee: teck
Reporter: nharward
Created: June 15, 2007
Votes: 0
Watchers: 0
Updated:
April 10, 2009
Resolved:
December 16, 2008

Description

We seem to get a lot of forum traffic about sessions not working correctly, and some of the big questions seem to be ‘is my configuration correct? do I have the right web-app names?’

We should add some very basic customer logging about every web application that is or is not instrumented for use with Terracotta Sessions.

Comments

Himadri Singh 2009-03-27

Start session configurator
Start terracotta session enabled applications
In the client logs following lines are printed showing which applications are clustered

2009-03-27 04:23:55,000 [main] INFO com.terracottatech.general - New logging session started. 2009-03-27 04:23:55,046 [main] INFO com.terracottatech.console - Terracotta Enterprise 3.0.0-nightly, as of 20090326-150316 (Revision 3796-12346 by cruise@su10mo5 from 3.0) … … 2009-03-27 04:23:59,562 [main] INFO com.terracottatech.dso - Clustered HTTP sessions IS enabled for [Townsend]. matched [Townsend] 2009-03-27 04:24:00,843 [main] INFO com.terracottatech.dso - Clustered HTTP sessions IS enabled for [DepartmentTaskList]. matched [DepartmentTaskList] 2009-03-27 04:24:01,875 [main] INFO com.terracottatech.dso - Clustered HTTP sessions IS enabled for [Cart]. matched [Cart]

verified in rev 12346