My Oracle Support Banner

AIS Errors With Unknown Number: Object Does Not Exist When Large Number of Items Are Exported (Doc ID 1961535.1)

Last updated on FEBRUARY 13, 2019

Applies to:

Oracle Agile PLM Framework - Version 9.3.1.1 and later
Information in this document applies to any platform.

Symptoms

Running Agile Integration Services (AIS) export to retrieve large number of items errors out.

Error

Exception in thread "main" AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.rmi.RemoteException: An error was encountered while exporting
data: com.agile.util.exception.CMAppException: Unknown Number: Object does not exist.
faultActor:
faultNode:
faultDetail:
       {http://xml.apache.org/axis/}hostname:agileserver

java.rmi.RemoteException: An error was encountered while exporting data: com.agile.util.exception.CMAppException: Unknown Number: Object does not exist.
       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(AbstractSAXParser.java:559)
       at org.apache.xerces.impl.XMLNamespaceBinder.handleEndElement(XMLNamespaceBinder.java:853)
       at org.apache.xerces.impl.XMLNamespaceBinder.endElement(XMLNamespaceBinder.java:643)
       at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:2978)
       at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:918)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDocumentFragmentScannerImpl.java:1145)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:988)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1446)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:333)
       at org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConfiguration.java:529)
       at org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConfiguration.java:585)
       at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:147)
       at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1148)
       at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
       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:2803)
       at org.apache.axis.client.Call.invoke(Call.java:2786)
       at org.apache.axis.client.Call.invoke(Call.java:2462)
       at org.apache.axis.client.Call.invoke(Call.java:2385)
       at org.apache.axis.client.Call.invoke(Call.java:1812)
       at export.ExportSoapBindingStub.exportData(ExportSoapBindingStub.java:462)
       at export.ExportData.run(ExportData.java:350)
       at export.ExportData.main(ExportData.java:192)


Steps

The issue can be reproduced at will with the following steps:
1. Run a command that exports large number of items.

  

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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