Notifications

57 views

Description

Symptoms


Windows MID Server service is running

MID shows down in the instance

agent log shows the following:

01/18/19 09:39:23 (542) LogStatusMonitor.60 stats threads: 41, memory max: 990.0mb, allocated: 173.0mb, used: 52.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes
01/18/19 09:40:23 (557) LogStatusMonitor.60 stats threads: 41, memory max: 990.0mb, allocated: 173.0mb, used: 50.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes
01/18/19 09:41:23 (574) LogStatusMonitor.60 stats threads: 41, memory max: 990.0mb, allocated: 173.0mb, used: 51.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes
01/18/19 09:42:23 (587) LogStatusMonitor.60 stats threads: 41, memory max: 990.0mb, allocated: 173.0mb, used: 52.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes
01/18/19 09:42:24 (044) ECCQueueMonitor.40 SEVERE *** ERROR *** Exception during SOAPStreamReader initialization
com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:677)
at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2104)
at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2010)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1102)
at com.glide.communications.AbstractXMLStreamReader.scanToNextElement(AbstractXMLStreamReader.java:127)
at com.glide.communications.AbstractXMLStreamReader.nextElementIsNamed(AbstractXMLStreamReader.java:136)
at com.glide.communications.SOAPStreamReader.scanForSOAPEnvelope(SOAPStreamReader.java:89)
at com.glide.communications.SOAPStreamReader.init(SOAPStreamReader.java:70)
at com.glide.communications.SOAPStreamReader.<init>(SOAPStreamReader.java:27)
at com.glide.communications.RecordsStreamReader.<init>(RecordsStreamReader.java:40)
at com.glide.communications.RemoteGlideRecord.getRecordsReader(RemoteGlideRecord.java:914)
at com.glide.communications.RemoteGlideRecord.queryGetRecordsDirectly(RemoteGlideRecord.java:416)
at com.glide.communications.RemoteGlideRecord.query(RemoteGlideRecord.java:311)
at com.service_now.mid.MIDRemoteGlideRecord.query(MIDRemoteGlideRecord.java:57)
at com.glideapp.ecc.ECCMessage.query(ECCMessage.java:176)
at com.service_now.monitor.ECCQueueMonitor.getOutputMessages(ECCQueueMonitor.java:379)
at com.service_now.monitor.ECCQueueMonitor.getOutputMessages(ECCQueueMonitor.java:385)
at com.service_now.monitor.ECCQueueMonitor.run(ECCQueueMonitor.java:160)
at com.service_now.monitor.AMonitor.runit(AMonitor.java:145)
at com.service_now.monitor.AMonitor.access$200(AMonitor.java:39)
at com.service_now.monitor.AMonitor$MonitorTask.runMonitor(AMonitor.java:135)
at com.service_now.monitor.AMonitor$MonitorTask.run(AMonitor.java:115)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)

 

wrapper.log will show:

2019/01/18 09:44:59 | [Fatal Error] :-1:-1: Premature end of file.
2019/01/18 09:45:07 | [Fatal Error] :-1:-1: Premature end of file.
2019/01/18 09:46:38 | [Fatal Error] :-1:-1: Premature end of file.
2019/01/18 09:48:09 | [Fatal Error] :-1:-1: Premature end of file.

 

Cause


MID Server user account is locked out. 

Resolution


Unlock the sys_user that's being used in the config.xml and restart the MID Server Windows service.

Article Information

Last Updated:2019-11-20 13:35:50
Published:2019-01-23