Skip to main content
Anonymous
February 3, 2014
Solved

"inactive sessions" generated by windchill

  • February 3, 2014
  • 1 reply
  • 1454 views

Lately we have had our IT department send us alerts that the database that Windchill is using has too many "inactive sessions". Often more than 150. While I know that inactive session is perfectly normal state for a particular session to be in, 150 inactive sessions still sounds a too many. Our guess is that for some reason Windchill is not releasing the sessions that it establishes with the database. What can we check/tweak to stop the inactive sessions from getting piled up?

Best answer by

We were able to fix the issue by setting the property wt.pom.connectionCloserIdleTimeout to a value of 1800. After setting this property we notice that db sessions get ternminated after they have been waiting for more than 1800 seconds (30mins) as intended. Pile up of inactive db sesions does not happen any more.

1 reply

Anonymous
Answer
February 10, 2014

We were able to fix the issue by setting the property wt.pom.connectionCloserIdleTimeout to a value of 1800. After setting this property we notice that db sessions get ternminated after they have been waiting for more than 1800 seconds (30mins) as intended. Pile up of inactive db sesions does not happen any more.

    Terms & ConditionsAccessibility statement