AnsweredAssumed Answered

JDEdwards RA random failures

Question asked by admin on Feb 26, 2018
Latest reply on Feb 26, 2018 by admin

Like • Show 0 Likes0
Comment • 2

Good Afternoon,
I currently have a ticket open already for this, but if anyone else has had this issue, please let me know.
We just updated our Production environment from 11.2.1 to 11.2.6HF1 and also our Agents/ServiceManagers and RAs (including Informatica and JDEdwards).
We are now having random JDE job failures with this error:

+++++++++++++++++++++++++++++++++++++ Start of Runtime Exception ++++++++++++++++++++++++++++++++++++

org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 52; XML document structures must start and end within the same entity.

at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)

at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)

at groovy.util.XmlParser.parse(XmlParser.java:175)

at groovy.util.XmlParser.parseText(XmlParser.java:208)

at groovy.util.XmlParser$parseText.call(Unknown Source)

at JDEdwardsAgentImpl.checkResultXML(JDEdwardsAgent.groovy:393)

at JDEdwardsAgentImpl$checkResultXML.callCurrent(Unknown Source)

at JDEdwardsAgentImpl.generateRequestXML(JDEdwardsAgent.groovy:740)

at JDEdwardsAgentImpl$generateRequestXML.call(Unknown Source)

at JDEJob.runJob(JDEdwardsAgent.groovy:3420)

at com.uc4.extensibility.types.CITAgent.dispatchJob(CITAgent.java:258)

at com.uc4.ex.cit.CITJob.execute(CITJob.java:196)

at com.uc4.ex.Job.run(Job.java:469)

at com.uc4.ex.ThreadPool$RunnableDecorator.run(ThreadPool.java:53)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

++++++++++++++++++++++++++++++++++++++ End of Runtime Exception ++++++++++++++++++++++++++++++++++++++

Though I'm waiting for support, if someone has come across this before, please let me know what you have found to work. I will also post what support finds out for us to see if it helps anyone in the future.
Thanks!!

No one else has this question

Outcomes

2 Replies

Carsten_Schmitz Feb 26, 2018 8:46 AM
Mark Correct
Correct Answer
Hey,

We don't have JDEdwards, but these xml documents that the parser complains about, it appears they are generated as part of the job. They should be somewhere on the disk, probably on the same server the agent is on, and are probably named base.xml, request.xml and (if it even gets this far) result.xml.

Have you had a look for (and at) those files? Looking at them e.g. with xmllint, or by visual inspection might hold a clue to what's wrong.

Hth,
Carsten
Like • Show 0 Likes0
Actions
admin Feb 26, 2018 3:13 PM
Mark Correct
Correct Answer
Hello,

So, as usual, fantastic support experience on our end!

Even though this was the RA, the xml's that helped find the issue were actually in the base agents temp folder and not the RA temp folder. We were able to get even more details with support when we ran a trace on the RA that had the few failing jobs.

There is a new feature in the JDE RA that appears to be encrypting the XML file and creating 2 files. In a few of the job cases, the XML files were incomplete and causing a job failure. These jobs were also not executing in JDE as a result. Working with support, they were able to provide us with an amendment to the ini file for the RA. He had us add encrypt=false at the bottom of the [RA] section, bounce the RA Agents in question, and our jobs then ran successfully.

We are going to keep working with support to try reproducing this in our DEV environment so that they can find a possible root cause. But changing that setting in our environment had no adverse effects.

I hope this can help someone in the future!
Like • Show 0 Likes0
Actions

JDEdwards RA random failures

Outcomes

Related Content

Recommended Content