“XLATE ICL server open failed, iclErr=1” is one of the errors we check for after restarting a process.  If we find that error in the log, we recycle the process.  We’ve had that in place for several years and has worked for us 100% of the time.

When you stopped/started the process then all worked as expected.

Could you send a portion of the process log from when process was started to the point where you started getting the error?

If not found, we kill the message.          return “{KILL $mh}”

<li style=”text-align: left;”>first parameter will be everything in the URL up to “/mdweb”
<li style=”text-align: left;”>second parameter “=&”
<li style=”text-align: left;”>third parameter will be everything after”PatientID”

I see if thread has

• Connection is “up” for over 5 minutes
• and O/B Queue depth >=1 for over 5 minutes
• and Last Receive is >= 300 seconds (5 minutes)

If all those are true, I prestart the thread.   Resolves the issue 99% of the time.

The mode can be ClientAuth,

SSl Protocol — TLS 1.3.   

Cipher list — TLS_AES_128_GCM_SHA256.

Not sure what to enter in the fields in the “CA Path  CA File” attachment.

Received the following from the vendor if that makes anything clearer.

All existing customers are being transferred to the Azure Cloud and converted to TLS connectivity. The standard connection protocol in…Read more

Infor – Is there any documentation?

Are there any other entries in your log other than the Broken Pipe entry?  You may need to increase the logging lev…Read more

I’ve never used “in” before and don’t know anything about it.  I’ll test that and see how it goes.

Thanks.

<tbody class=”tbody”>

<td class=”entry nocellnorowborder” headers=”d339569e54 “>Source Count
<td class=”entry nocellnorowborder” headers=”d339569e57 “>This specifies how many of the selected entities must satisfy the condition for the alert to trigger.

Has anyone had any success using Source Count?

The Source Count field, if I have that set to “any” or “at least 1“, shouldn’t that trigger the “and” alert?

I’m unable to find any good documentation on the Source Count field.

I’ve attached a document with screenshots of…Read more

We had a system malfunction recently.  It normally sends several hundred msgs to Cloverleaf per day.  The malfunction caused the system to send thousands of msgs in a very short period of time.

I can’t use the O…Read more

How can I find out what the ephemeral range for ports is?

OS is Redhat 8

It doesn’t happen often, and it is not just one thread that has the issue.  It doesn’t happen very often, maybe once every couple of months.

I have “Last Receive” and “Outbound Queue Depth” alerts set up that work for our high volume threads, but can’t really rely on those for our low volume threads.

Is there an alert that can be set up notify us when “Unable…Read more

If PLASTWRITE equals “Never”, the alert won’t trigger as there isn’t a start date/time that can be used to calculate the time since last send.  (At least that’s how it is here).

Is data being received by “from” thread but nothing is being sent outbound?

Is anything in hcimonitord.err or hcomonitord.log for that alert?

{ VALUE lastr }

Does alerts.log show that the alert was triggered?

Not sure if this helps as I’ve never dealt with msgs of that size, but we do huge backloads from our TEST server that has a site/process dedicated just for b…Read more

Thanks,  Jerry

I restart threads with an ‘and’ alert if

• connection is up
• X or more msgs waiting to be sent
• no acknowledgement received in X number of minutes.

<p class=”post-title”>Details are in Clovertech under this topic – Alert for…Read more

This makes me nervous as I’m not sure what issues (if any) Cloverleaf may experience.  Disk space, SMAT DB size, Recovery DB size, processing time, etc.

Has anyone dealt with any systems th…Read more

One thing though, I’m surprised that the log didn’t show anything.  I would think that you would find something in the log stating “Timed out while awaiting replies on thread. Resending reserved OB Message“.

I’ve experienced this issue with outbound threads for several systems.  The receiving system is not sending ack/nak msg so timeout occurs.  Cloverleaf will attempt to resend the message until an ack/nak is received.

Sometimes we have to stop/restart the interface on the receiving system.  So…Read more