Prev
Next
Forums Lawson S3 Supply Chain

mscm_server.log Prematuer end of file error

Sort:
You are not authorized to post a reply.
Author
Messages
Donna Wirt
Basic Member
Posts: 17
Basic Member
5/7/2013 5:23 PM
    After upgrading to 9.0.1.2 patch 10, and trying to upload counts, I received 2 errors in the mscm_server.log.  I'm wondering if these errors are related so if I resolve the first, will the second go away?  If not, does anyone know how to resolve either or both of these errors?

    1. Requester id not found for User:xxxxxxx. There are records in MSCM and RQ04. 
    2. And this:
      [05-02-2013 09:27:00,732] ERROR [com.lawson.mscm.platform.adapter.ags.OutboundSchedulable] Submitting message to Lawson failed
      [05-02-2013 09:35:11,819] INFO  [com.lawson.mscm.platform.adapter.rmi.InboundUserDeltaProcessSchedulable] About to import --> 'USER'
      [05-02-2013 09:35:12,132] ERROR [com.lawson.mscm.platform.adapter.rmi.InboundUserDeltaProcessSchedulable] org.xml.sax.SAXParseException: Premature end of file.
      org.xml.sax.SAXParseException: Premature end of file.
          at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
          at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
          at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
      I found a resolution for an error very similar to this but in the lajs.log.
    John Henley
    Senior Member
    Posts: 3348
    Senior Member
    5/7/2013 6:38 PM
      I would say they are unrelated, since one is inbound and one is outbound, and their times are several minutes apart.
      For the inbound error, I have seen those often when the dme.max is too high and the LSF server returns invalid XML.
      What setting do you have for dme.max in your mscm.filter.properties file?
      Also, what platform / websphere version are you using?
      Thanks for using the LawsonGuru.com forums!
      John
      You are not authorized to post a reply.