Error while parsing data returned org.xml.sax.SAXParseException; Premature end of file.

unknown

Hello, has anyone else seen this error? We started getting it about a month ago, and now it is happening more often (3 times in 3 different flows today). So far we have only seen it on the File Access node (read) and the Lawson Txn node (PR45). When we rerun the flow, it always runs clean. I looked at the system logs on the Lawson server and did not find any errors there.

Lawson support suggested that put in error handling on all of our nodes to wait and retry if this error occurs. This is not an option as we have a small staff and hundreds of flows.

We are on landmark v11.

russel-cornelson

org.xml.sax.SAXParseException; Premature end of file.
This error is saying:   I am trying to parse an XML file;  but I read all the way through the contents and did not find an opening <XML> tag.


A File Access Node (Read)
--  this MUST be a "Remote File Access" to your LSF system otherwise none of the calls would return XML that IPA would need to process.
--  A Remote File Access call:
...  calls  lsfserver/bpm/daservlet  which returns XML
...  calls lsfserver/ssoconfig/SSOCfgInfoServlet which returns XML
... calls lsfserver/sso/SSOServlet 
... makes RMI call to LSF RMIServer
... gets access to the LSF file system, reads file

A Lawson Txn Node
...  calls /ssoconfig/SSOCfgInfoServlet which returns XML
...  calls /sso/SSOServlet to authenticate
...  calls /servlet/Router/Transaction/Erp which returns XML


The only call that exists in both of those that return XML is /ssoconfig/SSOCfgInfoServlet;   if that is intermittently failing it could generate this error on the IPA side.   In that case you would likely need to work with Infor Security support staff to find out what is happening and why.



From an IPA Standpoint:
1.  Enable lawson-httpclient-trace.log on the Landmark server by adding C:Userslawsonlawson-httpclient-trace.log on the server.
** This is the home directory of the user that runs the Landmark Grid Java Processes.  Adjust directory accordingly if you are on UNIX.

2.  Duplicate Issue

3.  Copy the lawson-httpclient-trace.log into a different directory so it stops logging.   And analyze the output;  you should be able to determine if you are failing on /bpm/daservlet;   ssoconfig/SSOCfgInfoServlet;  or /servlet/Router/Transaction/Erp