Skip to Content
avatar image
Former Member

Agentry Session Timeout

I have an issue with loading the agentry application on a mobile device. The work manager 6.3 application is large and is taking the device a long time to load. Before the load can complete the server disconnects the client. The server disconnects the mobile connection after 5 minutes. In the log I can find the session timer and the disconnect. Where can this 5 minute session timeout be changed?

2016 03 01 16:34:15#0-500#INFO#System.out###Thread-18076#########SessionTimer::run::Reset timer. |

2016 03 01 16:34:15#0-500#DEBUG#com.syclo.agentry.User.TESTTECH1###Thread-18076#########SessionTimer::run::Session timer sleeping for 60 seconds. |

2016 03 01 16:35:15#0-500#DEBUG#com.syclo.agentry.User.TESTTECH1###Thread-18076#########SessionTimer::run::Session timer for user: TESTTECH1 ending. |

2016 03 01 16:40:13#0-500#DEBUG#com.sap.mobile.platform.server.agentry.console###Agentry SAPWM6.3 Worker Thread#########Received Rule Definition Request(209), 21, 15, testtech1, 380869/1886, 4:38:34PM/4:38:34PM |

2016 03 01 16:40:13#0-500#DEBUG#org.apache.coyote.http11.Http11Protocol###http-bio-8081-exec-8#########IOExceptions are normal, ignored javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Connection reset

at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1529)

at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1541)

at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:71)

at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:138)

at org.apache.coyote.http11.upgrade.UpgradeBioProcessor.write(UpgradeBioProcessor.java:61)

at org.apache.coyote.http11.upgrade.UpgradeOutbound.write(UpgradeOutbound.java:44)

at org.apache.catalina.websocket.WsOutbound.close(WsOutbound.java:354)

at org.apache.catalina.websocket.StreamInbound.closeOutboundConnection(StreamInbound.java:200)

at org.apache.catalina.websocket.StreamInbound.onData(StreamInbound.java:166)

at org.apache.coyote.http11.upgrade.UpgradeProcessor.upgradeDispatch(UpgradeProcessor.java:88)

at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)

at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

at java.lang.Thread.run(Thread.java:812)

Caused by: javax.net.ssl.SSLException: java.net.SocketException: Connection reset

at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)

at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1937)

at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1894)

at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1858)

at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1803)

at sun.security.ssl.AppInputStream.read(AppInputStream.java:116)

at org.apache.coyote.http11.upgrade.UpgradeBioProcessor.read(UpgradeBioProcessor.java:85)

at org.apache.catalina.websocket.WsFrame.blockingRead(WsFrame.java:170)

at org.apache.catalina.websocket.WsFrame.<init>(WsFrame.java:97)

at org.apache.catalina.websocket.WsFrame.nextFrame(WsFrame.java:220)

at org.apache.catalina.websocket.WsInputStream.nextFrame(WsInputStream.java:72)

at org.apache.catalina.websocket.StreamInbound.onData(StreamInbound.java:153)

... 7 common frames omitted

Caused by: java.net.SocketException: Connection reset

at java.net.SocketInputStream.read(SocketInputStream.java:209)

at java.net.SocketInputStream.read(SocketInputStream.java:141)

at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)

at sun.security.ssl.InputRecord.read(InputRecord.java:503)

at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:961)

at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:918)

at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)

... 13 common frames omitted

|

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Mar 02, 2016 at 10:36 PM

    Work Manager 6.3 is based on SMP 3.0. Most of the application configuration is now in the SMP 3.0 Cockpit. If you take the old Agentry.ini data which you used to configure the time out, most of the time out now are in the Backend Section of the SMP 3.0 Cockpit or the App Configuration settings.

    Also if you have transmit configuration setup specified in your Eclipse Agentry editor, the stay connected to system has an option to be enabled. If you do not have this enabled, the hard coded time out parameter is 5 minutes. 

    Hope this helps.

    Mark Pe
    SAP Platinum Support Engineer

    Add comment
    10|10000 characters needed characters exceeded

    • Nirali,

      I will put the link in the incident inside SAP. Expect it in there. After this, we can push this to the SMP 3.0 runtime server dev team.

      Best Regards,

      Mark Pe
      SAP Platinum Support Engineer