<![CDATA[Hexagon Safety & Infrastructure - Post to topic PurgeMSMQSysJournal system replacement]]> http://support.hexagonsafetyinfrastructure.com/infocenter/index?page=home Post to topic PurgeMSMQSysJournal system replacement en Copyright © 2002, 2012, Oracle and/or its affiliates. All rights reserved. Oracle Knowledge Information Manager http://blogs.law.harvard.edu/tech/rss <![CDATA[PurgeMSMQSysJournal system replacement]]> Our initial delivery included an EdgeFrontier system called PurgeMSMQSysJournal. It was necessary in order to make sure that the MSMQ system journal is cleaned out. IFCADDirect and EdgeFrontier use MSMQ for communication so when any of the queues become backed up or if the journal limit is reached then all EdgeFrontier systems can be impacted.

Sometime toward the end of 2015 we were told to turn off the PurgeMSMQSysJournal because something else replaced it. Unfortunately, we didn't recieve written documentation of what replaced it that I'm aware of so now I can't find whatever replaced it.

Our MSMQ journal just reached it's limit so I manually purged it. But I need to know what was supposed to be purging it so that I can go see why that isn't working.

Thanks,

Beth

]]> 2016-04-21 19:43:06 Etc/GMT <![CDATA[SOLUTION: RE: PurgeMSMQSysJournal system replacement]]> One answer I have received was checking the values of two specific locations:

  1. In the IFCADDirect.exe.config file, ensure the value for the key 'UseQJournaling' is set to False.

<add key="UseQJournaling" value="false"/>

  1. In the IFCAD930 (or whatever version you are on) EdgeFrontier system, ensure the Data Output named 'WriteToMSMQ' has a FALSE value set for the "Use Journal Queue:" option.

-Brien Foss

]]> 2016-04-29 15:44:57 Etc/GMT