After server upgrade SOAP call fails saying parameter missing

PSK_JP

After server upgrade from SP1 to SP6 suddenly report started working strange.

we calling ROX file from SOAP call from java, after SP6 upgrade parameter value passed as mandate DB parameter showring error saying missing parameter.

[main 2021-12-23 15:36:32,020]ERROR - Soap Server error.
AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
 faultSubcode:
 faultString: Soap Server error.
 faultActor:
 faultNode:
 faultDetail:
    {}RequestName:SubmitJob
    {}ErrorCode:3224
    {}Description:<Message>The value of a required parameter is missing.</Message><Parameter1>商品コード</Parameter1>

Soap Server error.
    at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
    at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
    at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
    at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
    at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
    at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
    at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
    at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
    at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
    at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
    at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
    at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
    at org.apache.axis.client.Call.invoke(Call.java:2767)
    at org.apache.axis.client.Call.invoke(Call.java:2443)
    at org.apache.axis.client.Call.invoke(Call.java:2366)
    at org.apache.axis.client.Call.invoke(Call.java:1812)
    at com.actuate.schemas.actuate11.wsdl.ActuateSoapBindingStub.submitJob(ActuateSoapBindingStub.java:6279)
    at com.manulife.actuate.api.control.MLJActuateControl.generateReport(MLJActuateControl.java:224)
    at com.manulife.actuate.batch.logic.MLJReportSubmitLogic.doLogic(MLJReportSubmitLogic.java:109)
    at com.manulife.actuate.batch.executor.MLJReportSubmitExecutor.execute(MLJReportSubmitExecutor.java:48)
    at com.manulife.actuate.batch.common.MLJSyncExecutor.process(MLJSyncExecutor.java:66)
    at com.manulife.actuate.batch.main.MLJBatchReportMain.main(MLJBatchReportMain.java:53)

Joel Anderegg

I would suggest opening a support ticket for this issue so we can have a detailed look at it.