Connection cannot be established using ODWEK

[bfarrajmtl]

Hello, we have an application that connects to CMOD using ODWEK, connection is lost for a few seconds, CMOD logs have no errors and application logs show the following entries:

[2018-07-23 08:03:10,441] [ERROR] [hread.pool : 10] Connection cannot be established for the sthaxxxxx server, com.ibm.edms.od.ODException: Connection cannot be established for the sthaxxxxx server--NL--   at com.ibm.edms.od.ODServer.getFolders(ODServer.java:1258)--NL-- at com.ibm.edms.od.ODServer.openFolder(ODServer.java:749)--NL-- at com.example.cmod.DatastoreOD.getSortedDocumentList(DatastoreOD.java:178)

com.ing.canada.ss.base.ServiceException [traceId=JXxhuc2yxADC] com.example.base.ServiceException: com.ibm.edms.od.ODException: Connection cannot be established for the sthaxxxxx server in service : getDocumentHitList2x00 at com.example.cmod.service.impl.GetDocumentHitListImpl.getDocumentHitList2x00(GetDocumentHitListImpl.java:257)

[7/23/18 8:02:48:403 EDT] 00000009 TimeoutManage I   WTRN0006W: Transaction 00000164C7036F00000000017E649C1870DC345E3545D661AE4C29A09F0D67899CB33D6200000164C7036F00000000017E649C1870DC345E3545D661AE4C29A09F0D67899CB33D6200000001 has timed out after 120 seconds.
[7/23/18 8:02:48:404 EDT] 00000009 TimeoutManage I   WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[ORB.thread.pool : 0,5,main].

CMOD version is 10.1.0.1 and ODWEK is 9.0.0.8.

Has anyone encountered a similar behavior?

Thanks.

[jsquizz]

Saw this EXACT issue a few years ago, when we were using different versions of CMOD and ODWEK.

We were on 8.5.0.6 CMOD, and 8.5.0.4.. might be worth looking into.

[Justin Derrick]

Edited the original post to remove identifying information.  :)

[Ed_Arnold]

This is a long shot but I saw this a couple years ago with ODWEK and ARSSOCKD both at 9.0.0.6.

...the root cause of the WAS timeout
issues is related to shortages in the native JVM heap storage, running
31-bit Java.
The solution will be to first upgrade the afp2pdf program to the 64-bit
version and then to switch the WAS Java, which is currently still
running 31-bit due to dependencies on the afp2pdf program, from 31- to
64-bit.

Ed