Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute

Question

This is a Bursting problem under EBS 5.6.3. In production we have 5.6.2 and since our development system to 5.6.3 has been upgraded, the following error occurs on every single Burst being done using the Concurrent Manager only:
Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:205)
     at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1502)
     at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1408)
     at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1350)
     at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1180)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:201)
     at oracle.apps.xdo.batch.BurstingProcessorEngine.burstingConfigParser(BurstingProcessorEngine.java:1340)
     at oracle.apps.xdo.batch.BurstingProcessorEngine.process(BurstingProcessorEngine.java:1297)
     at oracle.apps.xdo.batch.DocumentProcessor.process(DocumentProcessor.java:213)
     at xxwel.ebs.xmlp.XXWELBurster.processDocuments(XXWELBurster.java:143)
I can run the same file through 5.6.3 ($JAVA_TOP) libraries mounted on my JDev with no problems. Also the same XML file runs fine on Production under 5.6.2 - no problems. I have also checked the XML file using a syntax checker. I know this is not a syntax issue even though it looks like it.
Could someone point me in the right direction - explain what this means. Getting desperate as 5.6.3 will be going into production soon and all Bursting will fail with this error. I can't get the simplest XML File to Burst - NOTE this is only occurring on the EBS system (even running without the CM ie. a standalone java main it fails). I think this has something to do with the XML parser version and the EBS environment.
Please help...

Answer 1

Hi Tim, good thinking - wouldn't have thought to check this file. Anyway can confirm that the problem is happening with multiple burst control files so I haven't checked the files themselves as the problem seems systemic. anyway here is an example.
<?xml version="1.0" encoding="UTF-8"?>
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi">
<xapi:request select="/XXWEL_BIP_UNI_INVOICES/LIST_G_CUSTOMER_NUMBER/G_CUSTOMER_NUMBER">
<xapi:delivery>
<xapi:email server="mailwa01" port="25"
from="${ADMIN_EMAIL}" reply-to ="${ADMIN_EMAIL}">
<xapi:message id="111" to="${ADMIN_EMAIL}" attachment="true" subject="Unigas Inv
oice No: ${TRX_NUMBER}">
</xapi:message>
</xapi:email>
</xapi:delivery>
<xapi:document output-type="pdf" delivery="111">
<xapi:template type="rtf" location="/u02/prod/prodappl/wel/11.5.0/interface/bip/templates/uni_invoice_template.rtf">
</xapi:template>
</xapi:document>
</xapi:request>
</xapi:requestset>
I will start stripping the control files to make sure they are not the problem in the meantime.