E-IB: Timeouts on incoming messages (Doc ID 653728.1)

Last updated on DECEMBER 06, 2016

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.4 and later
Information in this document applies to any platform.
SPECIFIC TO:��PeopleTools 8.4x


This document was previously published as Customer Connection Solution 201037598



***Checked for relevance on 28-FEB-2011***
***Checked for relevance on 25-FEB-2013***
***Checked for relevance on 06-Dec-2016***

Symptoms


Incoming messages are failing with one or more of the various errors including:
- HTTPListeningConnector: GeneralFrameworkException
- bea.jolt.ServiceException and
- java.lang.OutOfMemoryError
- Timeout\nbea.jolt.SessionException: Connection recv error\nbea.jolt.JoltException: [9] NwHdlr.recv(): Timeout Error

Files to check are:
errorlog.htm on the gateway
stderr on the web server
PIA_WEBLOGIC log
appserv_mmdd.log
3rd party logs (if available)

Regarding the timout problem
1) errorlog shows the following
2007-02-27 16:15:02.264
HTTPListeningConnector: GeneralFrameworkException.
...
OnRequest for message %1 could not run to completion on node %2.


2) The STDERR file  shows the following:
- <Feb 9, 2007 5:09:11 PM CST> <Error> <HTTP> <BEA-101017> <[ServletContext(id=77968540,name=PSIGW,context-path=/PSIGW)] Root cause of ServletException.

java.lang.OutOfMemoryError: mmAllocLargeArray(jniGetVMThread(env), (ClassP)c, (ObjectP*)res, len)

            at java.lang.StringBuffer.append(Ljava.lang.String;)Ljava.lang.StringBuffer;(Optimized Method)

            at com.peoplesoft.pt.integrationgateway.common.Logger.logError(Ljava.lang.String;Ljava.lang.String;Lcom.peoplesoft.pt.integrationgateway.framework.IBRequest;Lcom.peoplesoft.pt.integrationgateway.framework.IBResponse;ILjava.lang.Throwable;)V(Logger.javANSWER:238)

            at com.peoplesoft.pt.integrationgateway.listeningconnector.HttpListeningConnector.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(HttpListeningConnector.javANSWER:328)

            at javax.servlet.http.HttpServlet.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(HttpServlet.javANSWER:853)

            at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.javANSWER:996)

            at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(ServletStubImpl.javANSWER:419)

            at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ServletStubImpl.javANSWER:315)

            at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.javANSWER:6455)

            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(AuthenticatedSubject.javANSWER:321)

            at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.javANSWER:118)

            at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic.servlet.internal.ServletRequestImpl;Lweblogic.servlet.internal.ServletResponseImpl;)V(WebAppServletContext.javANSWER:3664)

            at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel.ExecuteThread;)V(ServletRequestImpl.javANSWER:2630)

            at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.javANSWER:219)

            at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.javANSWER:178)

            at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)

and
The Web server log PIA_stderr.log has this at the same time:

[Thu Feb 08 17:05:25 CST 2007]bea.jolt.ServiceException: TPESVCERR - server error while handling request

An error occurred on the application server within Jolt while running the service.  Cancel the current operation and retry.  If the problem persists contact your system administrator. Error Code:10

Application Server last connected //lxomp07d.qintra.com_20401

bea.jolt.ServiceException: TPESVCERR - server error while handling request
- bea.jolt.ServiceException:
Feb 28, 2007 4:12:35 PM psft.pt8.auth.PSAuthenticator SetCookie
INFO: SwitchUser: Setting auth token. ip.addr.ess.80 Auth Token=FINMSGPR/2007-02-28-11.12.35.000435/<username>/ENG

<AF[923]: Allocation Failure. need 32784 bytes, 137198 ms since last AF>
<AF[923]: managing allocation failure, action=1 (82368/522310160) (11483704/14493680)>
  <GC(926): GC cycle started Wed Feb 28 16:12:41 2007
  <GC(926): freed 238840456 bytes, 46% free (250406528/536803840), in 114 ms>
  <GC(926): mark: 95 ms, sweep: 19 ms, compact: 0 ms>
  <GC(926): refs: soft 0 (age >= 32), weak 0, final 1124, phantom 0>
<AF[923]: completed in 116 ms>
Feb 28, 2007 4:14:08 PM psft.pt8.auth.PSAuthenticator SetCookie
INFO: SwitchUser: Setting auth token. 134.113.191.79 Auth Token=FINMSGPR/2007-02-28-11.14.07.999655/DPONNAMPERUMA/ENG
...
[Wed Feb 28 16:21:29 EST 2007]bea.jolt.ServiceException: bea.jolt.JoltRemoteService(ICScript)call(): Timeout\nbea.jolt.SessionException: Connection recv error\nbea.jolt.JoltException: [9] NwHdlr.recv(): Timeout Error
A Jolt error has occurred while communicating with the Application server.  Cancel the current operation and retry.  If the problem persists contact your system administrator. Error Code:100
Application Server last connected //machinename_9000

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