Allocation Batch Run via WSMRERequest.sh Fails with 'The server sent HTTP status code 503: Service Temporarily Unavailable' (Doc ID 2289426.1)

Last updated on JULY 28, 2017

Applies to:

Oracle Financial Services Profitability Management - Version 8.0.2 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Weblogic

Symptoms

In Oracle Financial Services Profitability Management (OFSAA) 8.0.2, when you execute an Allocation batch using WSMRERequest.sh from $FIC_APP_HOME/icc/bin, the following error is output to the WSMRERequest.log:

Exception occured com.sun.xml.internal.ws.client.ClientTransportException: The server sent HTTP status code 503: Service Temporarily Unavailable
[Thu Jun 01 21:02:01 EDT 2017]~[FATAL]~Exception occured com.sun.xml.internal.ws.client.ClientTransportException: The server sent HTTP status code 503: Service Temporarily Unavailable
[Thu Jun 01 21:02:01 EDT 2017]~[ERROR]~Run execution failed
com.sun.xml.internal.ws.client.ClientTransportException: The server sent HTTP status code 503: Service Temporarily Unavailable
       at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.checkStatusCode(HttpTransportPipe.java:296)
       at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.createResponsePacket(HttpTransportPipe.java:245)
       at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:203)
       at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:122)
       at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:95)
       at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:626)
       at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:585)
       at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:570)
       at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:467)
       at com.sun.xml.internal.ws.client.Stub.process(Stub.java:308)
       at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:163)
       at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98)
       at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
       at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:135)
       at com.sun.proxy.$Proxy20.invokeService(Unknown Source)
       at com.ofs.aai.pr2.cmd.WSMREClient.invokeService(WSMREClient.java:201)
       at com.ofs.aai.pr2.cmd.WSMREClient.main(WSMREClient.java:406)

In the 'httpd' log ssl_request.log, the 503 error is listed also:

xx.xx.xx.xxx - - [01/Jun/2017:20:57:01 -0400] "GET /OFSAA/manageRunExecution?wsdl HTTP/1.1" 200 2137
xx.xx.xx.xxx - - [01/Jun/2017:20:57:01 -0400] "POST /OFSAA/manageRunExecution HTTP/1.1" 503 250

Finally, the 'httpd' log error_log contains the following:

[Thu Jun 01 21:26:01 2017] [error] [client xx.xx.xx.x] <20100149636646127> weblogic: *******Exception type [READ_TIMEOUT] (no read after 300 seconds) raised at line 275 of Reader.cpp, referer: https://<servername>/OFSAA/pr2?serviceType=51&actionType=125&runName=APFT200&runDescription=PFT_RUN_ALLOCATION_BATCH
[Thu Jun 01 21:26:01 2017] [error] [client xx.xx.xx.x] <20100149636646127> weblogic: sendRequest: exception caught while parsingHeaders w/ recycled connection to xx.xx.xx.xxx:xxxx, numfailures=1, referer: https://<servername>/OFSAA/pr2?serviceType=51&actionType=125&runName=APFT200&runDescription=PFT_RUN_ALLOCATION_BATCH
[Thu Jun 01 21:26:01 2017] [error] [client xx.xx.xx.x] weblogic: ap_proxy: trying POST /OFSAA/pr2 at backend host xx.xx.xx.xxx/xxxx; got exception 'Backend Server not responding'; state: reading status line or response headers from WLS (wrote? Y read? N); not failing over because method not idempotent, referer: https://<servername>/OFSAA/pr2?serviceType=51&actionType=125&runName=APFT200&runDescription=PFT_RUN_ALLOCATION_BATCH
[Thu Jun 01 21:26:01 2017] [error] [client xx.xx.xx.x] <20100149636646127> weblogic: request [/OFSAA/pr2] did NOT process successfully.................., referer: https://<servername>/OFSAA/pr2?serviceType=51&actionType=125&runName=APFT200&runDescription=PFT_RUN_ALLOCATION_BATCH

As a result of this error, you cannot complete the Allocation batch.

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