<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article How to update Tomcat's inactivity timeout value? in PAM Self-Hosted Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/how-to-update-tomcat-s-inactivity-timeout-value/ta-p/1427792</link>
    <description>&lt;P&gt;The PSM HTML5 gateway closes user sessions after 30 minutes every time. The following error from the HTML5 Weblog.&lt;/P&gt;
&lt;P&gt;Error: [PSMGW][19:01:36.712][[Catalina-utility-1]][ERROR][c.c.p.m.s.CAPSMGWHttpSessionListener]: Session inactivity time out expired. Open tunnels will be closed&lt;/P&gt;
&lt;P&gt;This is due to the timeout that contains a default value of 30 minutes.&lt;/P&gt;
&lt;H3&gt;Issue&lt;/H3&gt;
PSM html5 gateway, user sessions are getting closed after 30 mins everytime. the below error from html5 weblog. its affecting our production access. please help to resolve this as soon as posibble. Error: [PSMGW][19:01:36.712][[Catalina-utility-1]][ERROR][c.c.p.m.s.CAPSMGWHttpSessionListener]: Session inactivity time out expired. Open tunnels will be closed

&lt;H3&gt;Environment&lt;/H3&gt;
PSM PSM HTML5 Gateway

&lt;H3&gt;Cause&lt;/H3&gt;
&lt;P&gt;Default time out value is only 30 mins.&lt;/P&gt;
&lt;H3&gt;Resolution&lt;/H3&gt;
&lt;P&gt;Edit the following file:&lt;BR /&gt;/opt/tomcat/webapps/guac/WEB-INF/web.xml&lt;/P&gt;
&lt;P&gt;Locate the following section:&lt;BR /&gt;&amp;lt;session-config&amp;gt;&lt;BR /&gt;&amp;lt;session-timeout&amp;gt;30&amp;lt;/session-timeout&amp;gt;&lt;/P&gt;
&lt;P&gt;Default is 30 minutes. You can change to the desired value and restart tomcat service.&lt;BR /&gt;&lt;BR /&gt;Additional Note:&lt;BR /&gt;There could be issues with connections which uses proxy or other possible reasons which impacted the packet which HTML5 receives. And this will cause the session validation to always fail and hence having the same disconnection behaviour.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We can also workaround by disabling the keepalive checks:&lt;BR /&gt;==&lt;BR /&gt;1. in /opt/tomcat/conf/server.xml addon into settings of connector&lt;BR /&gt;keepAliveTimeout="-1" useKeepAliveResponseHeader="false"&lt;BR /&gt;2. in /opt/tomcat/webapps/guac/WEB-INF/web.xml change from 30 to 1440&amp;nbsp;&lt;BR /&gt;&amp;lt;session-timeout&amp;gt;1440&amp;lt;/session-timeout&amp;gt;&lt;BR /&gt;3. in /etc/opt/CARKpsmgw/webapp/psmgw.conf change from 60 to 0&lt;BR /&gt;KeepAliveInterval=0&lt;BR /&gt;==&lt;/P&gt;
&lt;P&gt;Disclaimer: This is only intended as a workaround. And only configurable with self-hosted RPM deployment of HTML5GW.&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;P&gt;Edit the following file:&lt;/P&gt;
&lt;P&gt;/opt/tomcat/webapps/guac/WEB-INF/web.xml&lt;/P&gt;
&lt;P&gt;Locate the following section:&lt;/P&gt;
&lt;P&gt;&amp;lt;session-config&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;lt;session-timeout&amp;gt;30&amp;lt;/session-timeout&amp;gt;&lt;/P&gt;
&lt;P&gt;Default is 30 minutes. You can change to the desired value and restart tomcat service.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Additional Note:&lt;/P&gt;
&lt;P&gt;There could be issues with connections which uses proxy or other possible reasons which impacted the packet which HTML5 receives. And this will cause the session validation to always fail and hence having the same disconnection behaviour.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We can also workaround by disabling the keepalive checks:&lt;/P&gt;
&lt;P&gt;==&lt;/P&gt;
&lt;P&gt;1. in /opt/tomcat/conf/server.xml addon into settings of connector&lt;/P&gt;
&lt;P&gt;keepAliveTimeout="-1" useKeepAliveResponseHeader="false"&lt;/P&gt;
&lt;P&gt;2. in /opt/tomcat/webapps/guac/WEB-INF/web.xml change from 30 to 1440&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;lt;session-timeout&amp;gt;1440&amp;lt;/session-timeout&amp;gt;&lt;/P&gt;
&lt;P&gt;3. in /etc/opt/CARKpsmgw/webapp/psmgw.conf change from 60 to 0&lt;/P&gt;
&lt;P&gt;KeepAliveInterval=0&lt;/P&gt;
&lt;P&gt;==&lt;/P&gt;
&lt;P&gt;Disclaimer: This is only intended as a workaround. And only configurable with self-hosted RPM deployment of HTML5GW.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 13 Oct 2025 06:57:26 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-10-13T06:57:26Z</dc:date>
    <item>
      <title>How to update Tomcat's inactivity timeout value?</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/how-to-update-tomcat-s-inactivity-timeout-value/ta-p/1427792</link>
      <description>&lt;P&gt;The PSM HTML5 gateway closes user sessions after 30 minutes every time. The following error from the HTML5 Weblog.&lt;/P&gt;
&lt;P&gt;Error: [PSMGW][19:01:36.712][[Catalina-utility-1]][ERROR][c.c.p.m.s.CAPSMGWHttpSessionListener]: Session inactivity time out expired. Open tunnels will be closed&lt;/P&gt;
&lt;P&gt;This is due to the timeout that contains a default value of 30 minutes.&lt;/P&gt;
&lt;H3&gt;Issue&lt;/H3&gt;
PSM html5 gateway, user sessions are getting closed after 30 mins everytime. the below error from html5 weblog. its affecting our production access. please help to resolve this as soon as posibble. Error: [PSMGW][19:01:36.712][[Catalina-utility-1]][ERROR][c.c.p.m.s.CAPSMGWHttpSessionListener]: Session inactivity time out expired. Open tunnels will be closed

&lt;H3&gt;Environment&lt;/H3&gt;
PSM PSM HTML5 Gateway

&lt;H3&gt;Cause&lt;/H3&gt;
&lt;P&gt;Default time out value is only 30 mins.&lt;/P&gt;
&lt;H3&gt;Resolution&lt;/H3&gt;
&lt;P&gt;Edit the following file:&lt;BR /&gt;/opt/tomcat/webapps/guac/WEB-INF/web.xml&lt;/P&gt;
&lt;P&gt;Locate the following section:&lt;BR /&gt;&amp;lt;session-config&amp;gt;&lt;BR /&gt;&amp;lt;session-timeout&amp;gt;30&amp;lt;/session-timeout&amp;gt;&lt;/P&gt;
&lt;P&gt;Default is 30 minutes. You can change to the desired value and restart tomcat service.&lt;BR /&gt;&lt;BR /&gt;Additional Note:&lt;BR /&gt;There could be issues with connections which uses proxy or other possible reasons which impacted the packet which HTML5 receives. And this will cause the session validation to always fail and hence having the same disconnection behaviour.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We can also workaround by disabling the keepalive checks:&lt;BR /&gt;==&lt;BR /&gt;1. in /opt/tomcat/conf/server.xml addon into settings of connector&lt;BR /&gt;keepAliveTimeout="-1" useKeepAliveResponseHeader="false"&lt;BR /&gt;2. in /opt/tomcat/webapps/guac/WEB-INF/web.xml change from 30 to 1440&amp;nbsp;&lt;BR /&gt;&amp;lt;session-timeout&amp;gt;1440&amp;lt;/session-timeout&amp;gt;&lt;BR /&gt;3. in /etc/opt/CARKpsmgw/webapp/psmgw.conf change from 60 to 0&lt;BR /&gt;KeepAliveInterval=0&lt;BR /&gt;==&lt;/P&gt;
&lt;P&gt;Disclaimer: This is only intended as a workaround. And only configurable with self-hosted RPM deployment of HTML5GW.&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;P&gt;Edit the following file:&lt;/P&gt;
&lt;P&gt;/opt/tomcat/webapps/guac/WEB-INF/web.xml&lt;/P&gt;
&lt;P&gt;Locate the following section:&lt;/P&gt;
&lt;P&gt;&amp;lt;session-config&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;lt;session-timeout&amp;gt;30&amp;lt;/session-timeout&amp;gt;&lt;/P&gt;
&lt;P&gt;Default is 30 minutes. You can change to the desired value and restart tomcat service.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Additional Note:&lt;/P&gt;
&lt;P&gt;There could be issues with connections which uses proxy or other possible reasons which impacted the packet which HTML5 receives. And this will cause the session validation to always fail and hence having the same disconnection behaviour.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We can also workaround by disabling the keepalive checks:&lt;/P&gt;
&lt;P&gt;==&lt;/P&gt;
&lt;P&gt;1. in /opt/tomcat/conf/server.xml addon into settings of connector&lt;/P&gt;
&lt;P&gt;keepAliveTimeout="-1" useKeepAliveResponseHeader="false"&lt;/P&gt;
&lt;P&gt;2. in /opt/tomcat/webapps/guac/WEB-INF/web.xml change from 30 to 1440&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;lt;session-timeout&amp;gt;1440&amp;lt;/session-timeout&amp;gt;&lt;/P&gt;
&lt;P&gt;3. in /etc/opt/CARKpsmgw/webapp/psmgw.conf change from 60 to 0&lt;/P&gt;
&lt;P&gt;KeepAliveInterval=0&lt;/P&gt;
&lt;P&gt;==&lt;/P&gt;
&lt;P&gt;Disclaimer: This is only intended as a workaround. And only configurable with self-hosted RPM deployment of HTML5GW.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Oct 2025 06:57:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/how-to-update-tomcat-s-inactivity-timeout-value/ta-p/1427792</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-10-13T06:57:26Z</dc:date>
    </item>
  </channel>
</rss>

