- Phone Support
Home → Hershey's Issues and Solutions → Archive → Changing default Singularity timeout
2.5. Changing default Singularity timeout
To change the amount of time before a user's session expires and the user has to log back in, locate this file: \dcimaging\config\dcstartup.xml. dcimaging is a directory on a root drive of your Singularity server. Within this file, locate the following XML:
<!-- Sessions Properties -->
<StartParam value="com.developercreations.cranium.sessions.jdbc.poolname=dcSystemPool"/>
<StartParam value="com.developercreations.cranium.sessions.defaultmgrname=Sessions"/>
<StartParam value="com.developercreations.cranium.sessions.reapinterval=1200000" />
<StartParam value="com.developercreations.cranium.sessions.timeoutlength=600000" />
<!-- Sessions Properties -->
The two properties that pertain to a user's session timeout are:
- com.developercreations.cranium.sessions.reapinterval
- com.developercreations.cranium.sessions.timeoutlength
To increase or decrease the timeout length, set an appropriate value for the timeoutlength property, highlighted above. Note the units is in milliseconds. The default session timeout is for 10 minutes. Also, the reapinterval property must be changed to be greater than the timeout length value. The reapinterval property indicates the amount of time that must pass before expired sessions are reaped by the system. The default reap interval is for 20 minutes.
For example, to increase the timeout to 20 minutes, set the timeoutlength property to 1200000 and make the reapinterval property greater than 1200000. A suggested practice is to double the timeoutproperty value.
This page was: Helpful |
Not Helpful