Jolt Calls Timing Out With "bea.jolt.pool.ServiceException: TPETIME" (Doc ID 1619170.1)

Last updated on NOVEMBER 21, 2016

Applies to:

Oracle Tuxedo Jolt - Version 11.1.1.2.0 and later
Information in this document applies to any platform.

Symptoms

Jolt service calls from Weblogic to Tuxedo are timing out with below error:

Dec 11, 2013 12:16:11 PM CST Error HTTP BEA-101017 [weblogic.servlet.internal.WebAppServletContext@f76cfd - appName: 'yourAppName', name: 'yourName', context-path: '/yourContextPath'] Root cause of ServletException. bea.jolt.pool.ServiceException: TPETIME - timeout occured
        at bea.jolt.pool.Connection.call(Connection.java:318)
        at bea.jolt.pool.SessionPool.call(SessionPool.java:528)
        at bea.jolt.pool.SessionPool.call(SessionPool.java:268)
        at com.your.own.package.tuxedo.impl.TuxedoService.call(TuxedoService.java:104)
        ...

Tuxedo logs show below error message

131036.TuxedoAppBoxName!JSH.16579.1.-2: gtrid x0 x52b41d2b x2d1af6f: JOLT_CAT:1301: "ERROR: tpacall() call for service yourServiceName12 failed, tperrno = 13"
131036.TuxedoAppBoxName!JSH.12385.1.-2: gtrid x0 x52b41d2b x2d1b4e2: JOLT_CAT:1301: "ERROR: tpacall() call for service yourServiceName2 failed, tperrno = 13"
131036.TuxedoAppBoxName!JSH.10575.1.-2: gtrid x0 x52b41d2b x2d1b313: JOLT_CAT:1301: "ERROR: tpacall() call for service yourServiceName21 failed, tperrno = 13"

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms