0013063: Tomcat restart option and session timeout could collide

Description

If your rebuild is successful but you let the session to time out, application behavior is the same as if session is alive. The difference is that after logging in you will receive a message saying that Tomcat was not restarted.
Message is technically correct. However, user feedback is wrong, since there is no way to know what was the restart for. Was because a Tomcat restart, was because a time out?

Steps To Reproduce

Scenario 1:
Update any module and rebuild.
After the rebuild successful message, use the "Restart container" option.
You are taken to Login page.
Try to login. Login is successful.

Scenario 2:
Update any module and rebuild.
After the rebuild successful message, wait for session expiration.
Use the "Restart container" option.
You are taken to Login page.
Try to login. You receive a message saying that Tomcat was not restarted.

Proposed Solution

I would like to have an extra feedback when timing out. This would apply not only to rebuild window but all time out situations.

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
(0052498) AugustoMauch (manager) 2012-09-24 23:36	Effort: 1 Impact: mid Plan: short

Issue History
Date Modified	Username	Field	Change
2010-04-21 16:05	plujan	New Issue
2010-04-21 16:05	plujan	Assigned To	=> adrianromero
2010-04-21 16:38	adrianromero	Assigned To	adrianromero => alostale
2010-04-21 16:38	adrianromero	Category	01. General setup => A. Platform
2010-04-22 13:26	plujan	Status	new => scheduled
2010-04-22 13:26	plujan	fix_in_branch	=> pi
2011-11-17 15:40	alostale	Assigned To	alostale => marvintm
2011-11-17 15:40	alostale	Type	defect => design defect
2011-11-17 15:40	alostale	fix_in_branch	pi =>
2012-09-24 23:36	AugustoMauch	Note Added: 0052498
2012-09-24 23:36	AugustoMauch	Priority	normal => high