Hi Kevin,
240 as session-timeout value is working . Below files were updated again. I stopped apache-tomcat in both the AWI servers and then started them
1. /xxx/uc4/AWI/tomcat/conf/web.xml
<session-config>
<session-timeout>240</session-timeout>
</session-config>
2. /xxx/uc4/AWI/webapps/awi/config/uc4config.xml
<tcpip_keepalive>0</tcpip_keepalive>
3. /xxx/uc4/AWI/webapps/awi/config/configuration.properties
closeIdleSessions=true
Log:
2020-09-01 08:05:09,339 pool-2-thread-86 [WARN ] UC4 QA:123/USERID/ADPROD 0 0000000535364402 +148 [4.ecc.framework.core.inject.AEAwareScope] - entityMap size 1
2020-09-01 08:05:09,409 pool-2-thread-86 [INFO ] UC4 QA:123/USERID/ADPROD 0 0000000535364402 +148 [service.connection.RestConnectionService] - Requesting REST Endpoints from Backend
2020-09-01 08:06:03,451 pool-1-thread-1 [WARN ] UC4 QA:123/USERID/ADPROD 0 [4.ecc.framework.core.inject.AEAwareScope] - entityMap size 2
2020-09-01 08:06:03,451 pool-1-thread-1 [WARN ] UC4 QA:123/USERID/ADPROD 0 [4.ecc.framework.core.inject.AEAwareScope] - entityMap size 3
2020-09-01 12:05:18,452 pool-1-thread-1 [WARN ] UC4 QA:123/USERID/ADPROD NOUI 0000000535364402 [4.ecc.framework.core.inject.AEAwareScope] - entityMap size 3
2020-09-01 12:05:18,453 pool-1-thread-1 [WARN ] UC4 QA:123/USERID/ADPROD NOUI 0000000535364402 [4.ecc.framework.core.inject.AEAwareScope] - entityMap size 3
2020-09-01 12:05:18,454 pool-1-thread-1 [ERROR] UC4 QA:123/USERID/ADPROD NOUI 0000000535364402 [com.vaadin.server.DefaultErrorHandler] -
java.util.concurrent.ExecutionException: java.lang.RuntimeException: Push failed
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at com.vaadin.server.VaadinSession$FutureAccess.get(VaadinSession.java:124)
at com.vaadin.server.VaadinService.runPendingAccessTasks(VaadinService.java:1862)
at com.vaadin.server.VaadinSession.unlock(VaadinSession.java:996)
at com.vaadin.server.VaadinService.requestEnd(VaadinService.java:1382)
at com.uc4.ecc.framework.entrypoint.servlet.ECCServletService.requestEnd(ECCServletService.java:111)
at com.uc4.ecc.framework.entrypoint.maintenance.SessionCleanupThread.doCleanup(SessionCleanupThread.java:35)
at com.uc4.ecc.framework.entrypoint.maintenance.PeriodicFailsafeCleanupThread.run(PeriodicFailsafeCleanupThread.java:36)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.RuntimeException: Push failed
at com.vaadin.server.communication.AtmospherePushConnection.push(AtmospherePushConnection.java:171)
at com.vaadin.server.communication.AtmospherePushConnection.push(AtmospherePushConnection.java:146)
at com.vaadin.ui.UI.close(UI.java:1259)
at com.vaadin.server.VaadinService$1$1.run(VaadinService.java:481)
at com.vaadin.ui.UI.accessSynchronously(UI.java:1392)
at com.vaadin.server.VaadinService$1.run(VaadinService.java:471)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at com.vaadin.server.VaadinService.runPendingAccessTasks(VaadinService.java:1859)
... 12 common frames omitted
Caused by: java.lang.NullPointerException: null
at com.vaadin.server.communication.UidlWriter.write(UidlWriter.java:77)
at com.vaadin.server.communication.AtmospherePushConnection.push(AtmospherePushConnection.java:168)
... 20 common frames omitted
Original Message:
Sent: 09-01-2020 07:01 AM
From: Ashwin Easwaran
Subject: AWI/ ECC Session Timeout
Hi Kevin,
Today i successfully tested with below values as session-timeout in xxx/uc4/AWI/tomcat/conf/web.xml
2 minutes
5 minutes and
15 minutes
I have updated the value now to 240 and will keep you posted if the session timesout or not after it is idle for 4 hours.
We have 2 AWI servers each of which can handle the full load and load balancer has been configured for both.
Original Message:
Sent: 08-31-2020 12:37 PM
From: Kevin Dedcovich
Subject: AWI/ ECC Session Timeout
Hi Ashwin,
A couple of questions:
>> is the connection timing out at all? After how many minutes?
>> is a load balancer involved? or directly connecting to our AWI?
Kevin D.
Original Message:
Sent: 08-31-2020 11:03 AM
From: Ashwin Easwaran
Subject: AWI/ ECC Session Timeout
Dear Community,
Last week in UC4 QA we had implemented AWI session timeout successfully . Initially session-timeout value was set to 15 minutes in web.xml file and session was expiring after 15 minutes if idle.
Yesterday i updated the session-timeout value to 240 (4 hours) as a policy . But session was not expiring after 4 hours if idle. Could you please tell me what is the maximum session-timeout value that can be set here ?.
I had already raised a case with Broadcom on this and they had told me to check with Broadcom communities on this !
Also we have web.xml file in apache-tomcat at below path where session-timeout is 30 minutes which is default. This is Just FYI.
ucqaawixxxxd:/opt/apache-tomcat/8.5.55.0/conf $ grep -i session-timeout web.xml
<session-timeout>30</session-timeout>
As per Broadcom Knowledge base article only below files were updated.
Broadcom Article: https://knowledge.broadcom.com/external/article/188506/how-do-you-implement-session-timeout-in.html
This is how it looks now.
AWA version 12.3.3
1.
ucqaawixxxxd:/cme/uc4/AWI/tomcat/conf $ less web.xml
<session-config>
<session-timeout>240</session-timeout>
</session-config>
2.
ucqaawixxxxd:/xxx/uc4/AWI/webapps/awi/config $ less uc4config.xml
<?xml version="1.0" encoding="ISO-8859-15"?>
<configuration>
<!-- 0: off, 1: send, 2: receive, >=3: all -->
<trace count="10" xml="0"></trace>
<connections>
<connection name="UC4 QA" system="UC4_QA">
<tcpip_keepalive>0</tcpip_keepalive>
<cp ip="ucqaxxxxxxd.xxxxxx.xxx.com" port="2217"/>
<cp ip="ucqaxxxxxxd.xxxxxx.xxx.com" port="2218"/>
<cp ip="ucqaxxxxxxd.xxxxxx.xxx.com" port="2219"/>
<cp ip="ucqaxxxxxxd.xxxxxx.xxx.com" port="2220"/>
<cp ip="ucqaxxxxxxd.xxxxxx.xxx.com" port="2221"/>
<cp ip="ucqaxxxxxxd.xxxxxx.xxx.com" port="2222"/>
</connection>
</connections>
</configuration>
3.
ucqaawixxxxd:/xxx/uc4/AWI/webapps/awi/config $ less configuration.properties
# This is the configuration file for ECC. Here you can customize the configuration according to the installation guide if needed.
parameter_login.enabled = true
sso.saml.enabled = false
closeIdleSessions=true
Regards,
Ashwin Easwaran
Original Message:
Sent: 08-14-2020 10:18 PM
From: Ashwin Easwaran
Subject: AWI/ ECC Session Timeout
Hi Pete,
I was able to test this successfully. Thankyou.
Earlier i had updated the session-timeout value in /opt/apache-tomcat/8.5.55.0/conf/web.xml instead of updating it in /xxx/uc4/AWI/tomcat/conf/web.xml