My Oracle Support Banner

Tomcat Not Able to Serve New Valid Request if the Previous Request Failed or Encountered An Error (Doc ID 1483209.1)

Last updated on OCTOBER 15, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.0]
Information in this document applies to any platform.


It was observed that tomcat was not able to serve new valid request if the previous request failed or encountered an error, and it needed to be restarted to validate the new requests.

Reproduction steps:

1. Deploy the 7.3.1 version of the Infranet webservices with the apache tomcat server.
2. Use SOAP UI to successfully invoke a simple opcode like READ OBJ.
3. Now, invoke the PCM_OP_CUST_UPDATE_CUSTOMER opcode;

<PROFILES elem="1">
<TM_FLD_INV_PROFILE elem="1"/>

4. The opcode invocation will result in an error due to null POID value, which is expected.
5. Try to invoke this opcode 7-8 times; the older error will go away and NAP_CONNECT_FAILED will be thrown.

<soapenv:Envelope xmlns:soapenv="" xmlns:xsd=""
<opcodeReturn xsi:type="xsd:string"><![CDATA[ERROR: <?xml
version="1.0" encoding="UTF-8"?>
<LOCATION>ConnectionPool Timeout</LOCATION>




To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.