Session expired

[cc-2]

Hi all,

I am sure you have all experienced a "Windchill session expired". You start building your search criteria and are then dragged away. When you come back you wants to carry on and you get a message that your session has expired. You lose everything and must start from scratch again.

Is there away to increase the duration of a session or to make it unlimited ?

Thank you

[ptc-940718]

We also have this annoying behavior of search sessions timing out and would love to find a solution. Anyone?

Thanks,
Debbie Wilhelm
JHU/APL

[achukwuka]

Are you using some front-end authentication in conjunction with apache? In my environment that started happening when we implemented Siteminder for front-end authentication. We have since increased the timeout period in siteminder to make it longer.



Thanks

Alexius C. Chukwuka
IT Analyst, PDP Systems
John Deere Power Systems
Product Engineering Center
*Voice: 319-292-8575
*Mobile: 319-429-5336
*FaxFax:319-292-6282
*E-Mail: -

CONFIDENTIALITY. This electronic mail and any files transmitted with it may contain information proprietary to Deere & Company, or one of its subsidiaries or affiliates, and are intended solely for the use of the individual or entity to whom they are addressed, shall be maintained in confidence and not disclosed to third parties without the written consent of the sender. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error and that any use, dissemination, forwarding, printing, or copying of this electronic mail is strictly prohibited. If you have received this electronic mail in error, please immediately notify the sender by return mail.

[ddemay]

Siteminder aside since you are probably using that for SSO and proxy to
windchill, Tomcat in windchill through the web.xml maintains a parameter
that handles timeout of sessions. I do not believe the search page in
windchill uses Ajax functionality behind the scenses to act as a proxy for
http keep alive. Therefore, the connection gets closed and the cookie
JSESSIONID doesn't get updated in your browser. Java developers can store
things in a java server known as session beans. The beans can store things
like the custom search configuration you are trying to setup only to find it
disappear when the session expires and the beans are deleted from tomcat's
memory. Think a shopping cat you add items to but go away and want to
purchase them later, but they are gone.



The only fix for this is to edit the parameter in web.xml or build a
customization to refresh the jsessionid cookie used to track your session.