[Matthew Rasmussen]

Hey, so we had the same issue recently.  I’m going to copy the errors that we witnessed for search indexing, as Jim had a hard time finding this post.  But first, here’s an updated response from Infor for the particular issue we were seeing:

The following solution might help to answer questions about the incident or resolve the issue associated with it: 2153485

Event Note: Matthew,
Can we please try the following?
For the hci profile please modify the profile.local.end and change the following entries
From
export IGNORE_MEMCHECK=1
export IGNORE_FSFULL=1
export MALLOC_CHECK=0

to

#export IGNORE_MEMCHECK=1
#export IGNORE_FSFULL=1
#export MALLOC_CHECK=0

Here are the errors we found in our logs:

WARNING: engine terminating due to disk space shortage
[pd :open:ERR /0:zzz_a360_ib_rte:04/06/2022 12:32:56] [0.0.354731441] Unable to complete inbound save due to full disk, engine is terminating.

[pd :open:ERR /0:zzz_ib_EpicHMS_ADT:04/06/2022 12:40:59] Initializing secondary for [THREAD].in when not present
[pd :open:ERR /0:zzz_ib_EpicHMS_ADT:04/06/2022 12:48:38] [0.0.761496171] Unable to complete inbound save due to full disk, engine is terminating.
[pd :open:ERR /0:zzz_ib_EpicHMS_ADT:04/06/2022 12:48:38] Attempting to start an invalid transaction in [SMATDB file]
[pd :open:ERR /0:zzz_ib_EpicHMS_ADT:04/06/2022 12:48:38] Unable to start transaction while wrtiting to db [SMATDB file]
[pd :open:ERR /0:zzz_ib_EpicHMS_ADT:04/06/2022 12:48:38] Initializing secondary for [SMATDB file] when not present

[dbi :dbi :ERR /0:EPIC_945504_IN:04/06/2022 12:26:32] dbiWriteLogMsg: database (/Cloverleaf/cis19.1/integrator/[siteName]/exec/databases/) disk is > 10240 kilobytes full – engine terminating! err:0
[dbi :dbi :WARN/0:EPIC_945504_IN:04/06/2022 12:26:32] [0.0.294414534] dbiWriteMsgToRecoveryDb: failed inserting a recovery db record; try again
[dbi :dbi :WARN/0:EPIC_945504_IN:04/06/2022 12:26:32] [0.0.294414534] dbiWriteMsgToRecoveryDb: failed inserting a recovery db record; try again
[dbi :dbi :ERR /0:EPIC_945504_IN:04/06/2022 12:26:32] [0.0.294414534] dbiWriteMsgToRecoveryDb: failed inserting a recovery db record; err 4

[Matthew Rasmussen]

Hi Charlie,
The message is JSON over tcp/ip to/from another integration platform.  So we have a little control over both ends of the interface, which is nice.  The start of the message has a lengthy, but finite pattern, but the end is a bit more unpredictable.  Our first approach several months ago was actually to latch onto that pattern for the start block. And we were able to make it work. But when I presented this to our director, he wanted to see a cleaner separation between the protocol and the payload.  I think I’m going to try to get them to emulate the good old MLLP start and end characters as Jim suggested. That should keep things standard on Cloverleaf.
The message is like this:

{“Status”:{“SourceSystem”:”CLOVERLEAF”,”Environment”:”TEST”…
“Data”:{“MSH”:{“MSH_1″:”|”,”MSH_2″:”^~\&”,”MSH_3″:{“HD_1″:”EPIC”}…}

From there, the Data block just reads on like a plain HL7 message in JSON clothes.  Just objects and strings, with [arrays] to represent repeating group/segment/field structures.  It’s been an interesting project.  Looking at the complexity and size of these JSON messages really makes you appreciate the simplicity and efficiency of HL7.
Thanks very much for the reply, Charlie.

• This reply was modified 3 years, 8 months ago by Matthew Rasmussen.

[Matthew Rasmussen]

MLP! that would be the standardized approach.  It seems so obvious now that you mention it.  Here I was trying to reinvent the wheel, I just needed to emulate the wheel.  Thanks so much Jim!

[Matthew Rasmussen]

Hi Jim,

Thanks so much for the reply.  No, sorry I didn’t specify – the source is a tcp/ip file stream.  I am injecting a very unique character sequence at the end of each message on the source before it gets to Cloverleaf, and I’m using that sequence as the end block in the encapsulating settings – that’s working ok.  I just didn’t know if there was a more standardized way to slice the message out.

 

[Matthew Rasmussen]

Try turning EO up all the way for the receiving thread, send the message, check the logs, and see if you’re getting the payload in non-message data.  If the data is coming in there, you might have to adjust the encoding settings on the inbound thread to accommodate your payload.  I’ve used postman to send a message into Cloverleaf before, and it seems like I had to convert the file to newline, and then reference the file in postman – rather than copy/pasting the message text straight into postman.

[Matthew Rasmussen]

Hi Jim,

Funny story – I actually rebuilt the schema yesterday exactly as you suggested, with the underscores – great minds…  I’ll have to get the vendor’s blessing, but we’re redesigning the API in question anyway, so it shouldn’t be too hard to sell.  Especially if I take your additional advise and prove that these names don’t observe JSON best practice.  You can’t blame Cloverleaf for following the rules to the letter. I appreciate you sharing your wisdom and advise!

[Matthew Rasmussen]

Hi Ab,

I had a similar issue, I was trying to pass through special characters and I saw this thread in my search for help, so I opened a support ticket  as Jim suggested.

Dean B. helped me out (that guy is a rock star) and he determined that I needed to set encoding on the inbound and outbound thread to ISO-8859-1.  It worked like a champ!  without this setting, my special characters were getting escaped in translation, like this “\xcd” instead of an I with an accent grave.  Using ASCII or UTF-8, I could send a raw JSON file through ok, and I could write a raw HL7 message to a file ok – with preserving the special characters.  But when I went to translate the HL7 message to JSON and send it out, the outbound SMAT always escaped the special characters.

Anyway, hope this works for you too.

[Matthew Rasmussen]

I had the same problem, and I think I just figured it out…

The old way was to replace the gray icons with color icons in ./integrator/clgui/lib/clgui.jar/com/hie/cloverleaf/gui/images

in 19.1 however, it appears you can simply copy the color icons to here:
/integrator/clgui/images.  You have to do this while the IDE client is not running of course.  Hope this helps!

[Matthew Rasmussen]

1. What does seq_FileOut do?
2. So you are not doing any encoding, just moving the file from one place to another?
3. To Charlie’s point, try stopping the threads, dropping the large file in place, then starting the threads.  ie, make sure the file is fully formed before CL takes a swing at it.

[Matthew Rasmussen]

Hi Scott,

Just to clarify, you’re wanting to read in a PDF file, then encode it into an HL7 message, right? If so, how many threads are you using there?  Give us a rundown of how you’ve got your threads set up, and what POC you’re using your decode proc.  Its possible the file is getting read in, there’s nothing to do.  So there are no errors, but nothing is getting done.

Also,  you mentioned, “If  remove or otherwise truncate the OBX5.4 field the file processes just fine.” – so what is the outcome when everything goes fine?

I have seen something like this when the PDF file size exceeds 65535 bytes, and there is a workaround, but that pertains to code that references an HL7 variant.  Is your code referencing a variant?

[Matthew Rasmussen]

Hey Rob,

Did you ever figure out the reason you were getting this?  I’m seeing it on an engine running 6.1.1 on an AIX platform.

[Matthew Rasmussen]

Good info on SmatDB – that appears to be the best solution, and i think we are working toward that.  But in the meantime, does anyone know of a good way to manage the size of these index files, without breaking the indexes?  I was thinking of just deleting the smatsearchindex directories nightly, but then the indexes are broken in GM.  Does anyone know of a way to automatically trigger a “re-index” on the GM side, to occur after the index directories are purged on the engine?

[Matthew Rasmussen]

WOW!  Thanks Elisha!!

[Matthew Rasmussen]

OK, so I have been successfully add bind address detection as well as several other relevant difference values.  But there are two that i really need, but cannot access becuase they are in the prologue:

There is no pre-defined section for prologue in the default DiffList, so I tried this, but with no avail:

set DiffList(prologue) {

   { who: “GUI user” }

   { date: “Config change time/date” }

}

Any ideas?  I guess I could just pipe everything before “end_prologue” to the standard diff, but would like to do it all in the hci command if possible.

[Matthew Rasmussen]

HA!

Glad you posted that!  I just realized it ignores changes to the bind address as well!

[Author]

Replies