Reports Server Crashes Several Times Per Day (Doc ID 473577.1)

Last updated on NOVEMBER 23, 2011

Applies to:

Oracle Clinical - Version: 4.5.2 and later   [Release: 4.5 and later ]
Information in this document applies to any platform.
***Checked for relevance on 16-APR-2010***
***Checked for relevance on 23-Nov-2011***

Symptoms

On OC 4.5.2, when attempting to run reports, the Reports Server instance would timeout and require a restart perhaps once a week. 

As system usage has increased, we are now restarting approximately 6 - 8
times per day.


The following messages in the server's error log are continually repeated:

[Tue Aug 28 07:24:05 2007] [error] [client 137.187.67.159] [ecid:
1188300245:137.187.67.63:2380:2572:368,0] MOD_OC4J_0080:
After calling Apache's ap_bwrite(),  got an return value: -1 and the client could have aborted in the middle of receiving the chunk data.
[Tue Aug 28 07:24:05 2007] [error] [client 137.187.67.159] [ecid:
1188300245:137.187.67.63:2380:2572:368,0] MOD_OC4J_0058: Failed to handle response chunk data
passed in from oc4j via ajp13.
[Tue Aug 28 07:24:05 2007] [error] [client 137.187.67.159] [ecid:
1188300245:137.187.67.63:2380:2572:368,0] MOD_OC4J_0035: After handling ajp13 response message,
got an invalid value: -2.
[Tue Aug 28 07:24:05 2007] [error] [client 137.187.67.159] [ecid:
1188300245:137.187.67.63:2380:2572:368,0] MOD_OC4J_0121: Failed to service request with network
worker: OC4J_BI_Forms_15 and it is not recoverable.
[Tue Aug 28 07:24:05 2007] [error] [client 137.187.67.159] [ecid:
1188300245:137.187.67.63:2380:2572:368,0] MOD_OC4J_0013: Failed to call destination:
OC4J_BI_Forms's service() to service the request.


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