DocumentGenerator SOAP FaultException (Doc ID 2125928.1)

Last updated on JUNE 27, 2017

Applies to:

Oracle Insurance Policy Administration J2EE - Version 10.1.2.1 and later
Information in this document applies to any platform.

Symptoms

On : 10.1.2.1 version, General

ACTUAL BEHAVIOR
---------------
DocumentGenerator SOAP FaultException

The recursive DocumentGenerator call from OIPA back to the WebService is generating a SOAPFaultException. The server logs are unable to display any further information to identify to problem other what is displayed in the stack trace.

Using WebSphere 8.5.5

Caused by: com.adminserver.utl.exception.AsExceptionUtl: An error occurred processing extension com.adminserver.ext.DocumentGeneratorExt.
at com.adminserver.ext.DocumentGeneratorExt.process(DocumentGeneratorExt.java:102)
at com.adminserver.ape.ExternalProcessApe.processRule(ExternalProcessApe.java:65)
... 97 more
Caused by: javax.xml.ws.soap.SOAPFaultException: Internal Error
at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1353)
at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(MethodMarshallerUtils.java:1079)
at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMethodMarshaller.demarshalFaultResponse(DocLitWrappedMethodMarshaller.java:680)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:626)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:566)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:432)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:213)
at com.sun.proxy.$Proxy60.generateDocument(Unknown Source)
at com.adminserver.ext.DocumentGeneratorExt.generateDocument(DocumentGeneratorExt.java:125)
at com.adminserver.ext.DocumentGeneratorExt.process(DocumentGeneratorExt.java:90)
... 98 more

EXPECTED BEHAVIOR
-----------------------
The callback should complete successfully.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Setup DocumentGenerator extension (part of OIPA documentation), use attached report definition, setup relevant server paths in debug environment
After restoring database schema
1. Navigate to plan activity screen
2. Drill-down to products - income promise select
3. Process one of the pending "PremiumReport" activities
4. Stack trace above is generated


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot determine the issue due to the server logs.

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