JackHillman

java.util.concurrent.TimeoutException

0 votes
I receive eSignLive Callback failed emails sparingly, even though I receive the callback successfully. The email body resembles the following: URL: https://wwwmywebsite.com/listener/ Payload: {"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_COMPLETE","sessionUser":"Signer","packageId":"mypackageID","message":null,"documentId":null,"createdDate":"2019-04-16T21:11:56.807Z"} Reason(s): java.util.concurrent.TimeoutException Any idea how I can prevent these all together? Sometimes a week goes by without receiving one, and sometimes I'll get 2 in a row.

Reply to: java.util.concurrent.TimeoutException

0 votes
Hi JackHillman, From the callback failure reason: java.util.concurrent.TimeoutException(this error was happened at OneSpan Sign side, so even if you were not using Java application, you would still see this java exception), it seems like your application consumes the call longer than 20 seconds , so even if you returned 200 status, it still exceeded the timeout. Is that the case for you that you have a heavy business logic and took long to consume the call? Also check ourCreate a Callback Event Notification Listener guide where I've updated examples by using asynchronous functions. Hope this could help! Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off