Portal Hangs after some Time of Inactivity (Doc ID 433149.1)

Last updated on AUGUST 03, 2016

Applies to:

Portal - Version 10.1.2.0.0 to 10.1.4.2 [Release 10gR2]
Information in this document applies to any platform.
Checked for relevance on 09-Oct-2013

Symptoms

Portal hangs intermittently. The problem mostly occurs after some time of inactivity.

In the time of the problem the following exception is written into the Portal's application.log while the Portal's Parallel Page Engine (PPE) is in debug mode:

portal: DEBUG: active=26 id=90991558055,1 Muffling exception
java.io.IOException: Request aborted by user
    at HTTPClient.Response.getHeaders(Response.java:703)
    at HTTPClient.Response.getStatusCode(Response.java:262)
    at HTTPClient.HTTPResponse.handleResponse(HTTPResponse.java:805)
    at HTTPClient.HTTPResponse.getInputStream(HTTPResponse.java:577)
    at oracle.webdb.dispatcher.HTTPDispatcher$HTTPDispatcherResponse.
getInputStream(Unknown Source)
    at oracle.webdb.dispatcher.HTTPDispatcher$HTTPDispatcherResponse.close(Unknown Source)
    at oracle.webdb.page.ContentFetcher.run(Unknown Source)
portal: DEBUG: active=26 id=90991558055,1 Content Fetcher
Caught:
java.io.IOException: Request aborted by user
    at HTTPClient.Response.getHeaders(Response.java:703)
    at HTTPClient.Response.getStatusCode(Response.java:262)
    at HTTPClient.HTTPResponse.handleResponse(HTTPResponse.java:805)
    at HTTPClient.HTTPResponse.getInputStream(HTTPResponse.java:577)
    at oracle.webdb.dispatcher.HTTPDispatcher$HTTPDispatcherResponse.
getInputStream(Unknown Source)
    at oracle.webdb.dispatcher.HTTPDispatcher$HTTPDispatcherResponse.close(Unknown Source)
    at oracle.webdb.page.ContentFetcher.run(Unknown Source)
portal: DEBUG: active=26 id=90991558055,1 Muffling exception oracle.webdb.page.StateNotSetException
    at oracle.webdb.page.BaseContentRequest.setState(Unknown Source)
    at oracle.webdb.page.BaseContentRequest.doFailed(Unknown Source)
    at oracle.webdb.page.ContentFetcher.run(Unknown Source)
portal: DEBUG: active=26 id=90991558055,1 ContentFetcher
Unexpected Exception Request Failed:java.io.IOException: Request aborted by
user name=content-fetcher1 label=dbPortlet url=http://<host>:<port>/portal/pls/portal/!PORTAL.wwpro_app_provider.execute_portlet/8354675
42/51 time=27732ms timeout=20000ms process=GotResponse


Other symptoms may include errors like these in the Portal's application.log:

09/09/15 15:34:37 portal: [module=RepositoryServlet, ecid=72057687396693740,1] ERROR: Repository
Gateway error: Request Processing Error: Bad name in the request: not a legal PLSQL identifer
09/09/15 15:40:28 portal: id=72057687396989735,1 Stall Timeout reached. Interrupting Fetcher
name=content-fetcher25 label=pageMeta
url=http://<host>/portal/pls/portal/!PORTAL.wwpob_page.show/TOPLEVELSITE time=61748ms
timeout=61000ms process=GotResponse
09/09/15 15:40:28 portal: id=72057687396989735,1 Connection Timeout reached. Timing out Fetcher:
java.net.SocketTimeoutException: Read timed out name=content-fetcher25 label=pageMeta
url=http://<host>/portal/pls/portal/!PORTAL.wwpob_page.show/TOPLEVELSITE time=61749ms
timeout=60000ms process=GotResponse
09/09/15 15:40:28 portal: FetchGroup caught uncaughtException=java.lang.NullPointerException in
thread name=content-fetcher25, starting a new fetcher. 27 total threads in this group. Parent
Groups : ApplicationServerThreadGroup=46, main=58, system=64, end.
09/09/15 15:54:53 portal: Broken pipe
09/09/15 15:54:53 portal: Broken pipe


or errors like these in the Apache error_log:

[Tue Sep 15 14:04:55 2009] [warn] long lost child came home! (pid 26317)
[Tue Sep 15 15:44:28 2009] [warn] [client <ip>] oc4j_socket_recvfull timed out
[Tue Sep 15 15:44:28 2009] [error] [client <ip>] [ecid: 72057687396989735,3]
(4)Interrupted system call: MOD_OC4J_0038: Receiving data from oc4j exceeded the configured
"Timeout" value and the error code is 4.
[Tue Sep 15 15:44:28 2009] [error] [client <ip>] [ecid: 72057687396989735,3]
MOD_OC4J_0054: Failed to call network routine to receive an ajp13 message from oc4j.
[Tue Sep 15 15:44:28 2009] [error] [client <ip>] [ecid: 72057687396989735,3]
MOD_OC4J_0033: Failed to receive an ajp13 message from oc4j.
[Tue Sep 15 15:44:28 2009] [warn] [client <ip>] [ecid: 72057687396989735,3] MOD_OC4J_0078:
Network connection errors happened to host: opasprd1.usq.edu.au and port: 12502 while receiving
the first response from oc4j.  This request is recoverable.
[Tue Sep 15 15:44:28 2009] [error] [client <ip>] [ecid: 72057687396989735,3]
MOD_OC4J_0121: Failed to service request with network worker: OC4J_Portal_15 and it is not
recoverable.
[Tue Sep 15 15:44:28 2009] [error] [client <ip>] [ecid: 72057687396989735,3]
MOD_OC4J_0013: Failed to call destination: OC4J_Portal's service() to service the request.

 

After the hang, Portal needs to be restarted to get it working again.

Steps To Reproduce:

1. Navigate in Portal
2. Sometimes leave Portal inactive for more than 1 hour
3. Notice that Portal hangs after the inactivity

Changes

 

 

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