I was just looking for this answer. We are on 2024.1 and its time to update certificates. Unfortunately I don't remember if the certificates were required when I installed a few years ago. The legacy certificate is on the arbiter server so I went ahead and put the new certificate. I do not want to chance it not working on our environment.
Maybe if the server had wire shark installed I could see if the traffic between arbiter and failover members was encrypted or not.
one thing I kept tripping on was that when I was doing $LTS(tList), if you don't define the optional delimiter, it will default to a comma "," so I kept getting commas between each element in the list. So $LTS(tList," ") to put a space between list elements made it look readable again. Thanks for the script.
Thanks for the feedback. When I get some free time I will also try to see what can be done with the HL7 implementation.
I understand how to extend the property on a dataset class / property. Would there be a way you could use this in the Ens.DTL? So that as HL7 messages are coming in I can apply these method fake, destruct, and random on EnsLib.HL7.Message?
I moved my reply / question because I think it was in the wrong spot.
Did you ever get a resolution or root cause? We had this happen to us today in our message logs.
02/01/22-08:56:16:798 (19248) 1 [Generic.Event] Journal Daemon has been inactive with I/O pending for 10 seconds:
gjrnoff=848283888,iocomplete=845152256,filecnt=1948,fail=0
02/01/22-08:56:52:672 (34576) 2 [Utility.Event] ISCLOG: SuperServer Super Server job slave failure ns=%SYS rtn=%SYS.SERVER
02/01/22-08:56:58:152 (34576) 1 [Utility.Event] SuperServer failed to start slave server
Did you every get a resolution? We are also running VM servers and getting DBLatency errors