"javax.xml.ws.soap.SOAPFaultException Your session has timed-out." during constant stream of request

Kris Boutilier

Hi all.

I'm having a problem with calls to CWS suddenly throwing a timeout exception along the lines of: 

Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Your session has timed-out. at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:189) at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118) {etc.}

The timeout appears to occur regardless that there is a constant and ongoing stream of requests - it seems to be related to the time elapsed since either the Authentication Service or the DocumentManagement Service was instantiated. That's to say if I set the Content Server system parameter:

Configure Security Parameters -> Cookie Authentication Information -> Expire {nnn} minutes after last request

to a value of 300 minutes, then exactly 5 hours after my process starts (and some ~48,000 requests later) it throws a timeout.

Has anyone else observed this behaviour, or have I missed something obvious?

Appu_Nair1

Check if you need to "renew" the token in your client code.I beleive new OT code supports querying the authentication token and renewing it.If we look at a step back and see this in more simple terms I use the GUI and Livelink issued a Cookie,If I do not refresh the browser by doing nothing then no more requests has gone to livelink to start over,so afater 5 hours I will be re-issued a cookie or shown the login screen.I am saying this form just looing at the authentication part of livelink I do not know if the auth token in your example came form OTDS or not. also it is not unusual for companies doing a lot of wsapi/lapi work to make dedicated instances and making the cookie not to expire.