SonarQube 5.6x版本用户20分钟空闲会话超时配置求助
Fixing Session Timeout in SonarQube 5.6.x
Got it, let's sort out this session timeout issue for SonarQube 5.6.x—this older version doesn't recognize the sonar.web.sessionTimeoutInMinutes config that worked for 6.7.x, since that setting was added in later releases. Instead, we need to tweak the embedded Tomcat configuration that 5.6.x relies on. Here's the step-by-step fix:
- Locate the
server.xmlfile in your SonarQube 5.6.x installation directory, under theconf/folder (full path:_/Sonar_Home/conf/server.xml_) - Open the file and find the
<Connector>tag (it typically defines the default HTTP port, like 9000) - Add the
maxInactiveIntervalattribute to this tag, setting its value to 1200—Tomcat uses seconds for this setting, so 20 minutes × 60 seconds = 1200. Your updated Connector line should look similar to this:<Connector port="9000" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxInactiveInterval="1200"/> - Save the file and restart your SonarQube 5.6.x service to apply the changes
- Verify the fix: log into SonarQube, leave the session idle for 20 minutes, and you should be automatically logged out
If you're running SonarQube 5.6.x on an external (non-embedded) Tomcat server, the same logic applies—just modify the server.xml of your external Tomcat instance and restart it.
内容的提问来源于stack exchange,提问作者user7486728
相关产品推荐
相关产品推荐

