brother_of_karamazov
Legendary Poster
Anyone else get really annoyed when the WebSphere admin console times out in 30 minutes? I mean, security & timeout rules are for end users right?
To change the timeout in WAS6:
1. Edit the ${WAS_HOME}/systemApps/adminconsole.ear/deployment.xml file in a text editor.
2. Locate the xml statement <tuningParams xmi:id="TuningParams_1088453565469"
maxInMemorySessionCount="1000" allowOverflow="true" writeFrequency="TIME_BASED_WRITE"
writeInterval="10" writeContents="ONLY_UPDATED_ATTRIBUTES" invalidationTimeout="30">
3. Change the invalidationTimeout value to the desired session timeout. The default is 30.
4. Save the ${WAS_HOME}/systemApps/adminconsole.ear/deployment.xml file.
5. Restart the application server.
To change the timeout in WAS6:
1. Edit the ${WAS_HOME}/systemApps/adminconsole.ear/deployment.xml file in a text editor.
2. Locate the xml statement <tuningParams xmi:id="TuningParams_1088453565469"
maxInMemorySessionCount="1000" allowOverflow="true" writeFrequency="TIME_BASED_WRITE"
writeInterval="10" writeContents="ONLY_UPDATED_ATTRIBUTES" invalidationTimeout="30">
3. Change the invalidationTimeout value to the desired session timeout. The default is 30.
4. Save the ${WAS_HOME}/systemApps/adminconsole.ear/deployment.xml file.
5. Restart the application server.