[Mike Strout]

Thanks to all for your thoughts. Ab got me on the right track thinking about CaSe. I looked at the list of allowable commands and saw that all the commands were UPPER case. I made the change and tested. Error again!

Then I saw Peter’s replay where he mentioned “list vs nlist vs nlst”. I wondered what is the difference between the list to and realized that in all the threads fileset-ftp threads that we currently use, the list command is nlist, so that was stuck in my mind. I looked more carefully at the output from help and the resolution was clear…

help
< 214-The following commands are recognized:
…
< NLST

So much angst for one letter. We’ve all done things like this before and it just takes someone with a little perspective to see the glaring error.

Thanks all for your quick support!
Mike Strout

[Mike Strout]

I managed to back-arrow through my browser history and find it. I resent it and it still didn’t post. Maybe I have been banned because my messages are too long. LOL

Mike

[Mike Strout]

I am seeing strange things too. I just spent 20 minutes crafting a masterpiece of a post about a fileset-FTP issue. I posted it and it is no where to be found.

Mike Strout

[Mike Strout]

Has anyone managed to get this to work? At my last job, we used symbolic links instead of a master site. At my new gig, they use a master site and I hate not being able to see and edit various user-created resources like tclprocs and such. However, we don’t want to move to the symlink option because it isn’t allowed in the new Infor-hosted Cloverleaf option.

Mike Strout

[Mike Strout]

Like Peter, I have been having a hard time wrapping my mind around how FHIR would be implemented in Cloverleaf. If a developer is looking at a simple request/response interface, no problemo. But from what I have heard from my son who is making extensive use of FHIR to read data out of Epic, querying with FHIR is like querying a DB without using joins. You query to get a key and then you use that key to make another query, and another, and another…until you have all the data you need to respond to the original request. I can’t picture how that would work in Cloverleaf unless you handle everything after the first query in Tcl or you have a bunch of chained threads (which I kinda like the idea of.

I am going to unpack the FHIR box referenced in the documentation to see if that clears things up.

 

Mike

[Mike Strout]

Have you tried adding the color portions of 6.1.2.0 to the 6.1.2.1 JAR file? If you can get me the newer JAR, I will do it for you.

[Mike Strout]

Thanks James. I thought 40 messages per second looked too good to be true. I didn’t realize Cloverleaf would behave so async’ly. I guess I need to throttle back a bit.

[Mike Strout]

Yes, I did open a ticket that has been escalated to development. During my discussions with them, they said that the GUI and the resend process use different regex libraries, which accounts for the differences what is displayed vs what is resent.

[Mike Strout]

We just updated to 6.1.2.4 and also lost the colors. I fixed the jar by opening it and an older colorized file in BeyondCompare, our file comparison utility. Then I browsed into the comhiecloverleafguiimages path in the jar and copied the image files from the colorized jar to the new jar. I was up an running in color in about 3 minutes.

[Mike Strout]

Thanks Charlie. I am pretty disappointed with my 6.1 upgrade. I had such high hopes for the SMATDB, but it seems every time I turn around, I find another bug that makes searching it untrustworthy. Something as simple as…

A|B|C|D|E|F|G|H|I|J|K

…will fail because it has more than 10 options. If it can’t handle something as simple as this, I have a hard time believing it can handle more complex regular expressions like a negative lookahead.

[Mike Strout]

Thanks all for the great answers. I don’t know why I didn’t think about only having one write thread. I will definitely be implementing that soon. The WAL sounds interesting too, but may be overkill for this relatively low volume DB.

Also, thanks Charlie about the same process idea. I do have a question about that though. We are on 6.1.2 and found that I will get a validation error if I have two db connections in the same process (not Tcl connections). I have another data flow that requires a long-term cache to pend result messages until the ordering provider is added to the order retrospectively (ER workflow). If the result doesn’t have a real ordering provider, I throw it into the DB kill the message. Then each day for three days I query the DB to get the message, CURL over to Epic to see if the ordering provider has been updated yet. If so, I update the message, send it on its way, and archive the record in the DB.

Cloverleaf won’t let me have the OB Database Protocol and the IB Database Protocol in the same process. Anyone know why?

[Mike Strout]

First off, let me say that I find the outbound database protocol extremely frustrating and a pain to troubleshoot. That said, here are a few tips I have learned…

1. Open your database schema and then for each table, select it and then  change the delimiter in Options>Table Schema Options to something other than a “,” as it isn’t uncommon to have a comma in an HL7 message. I usually use a # or %.

2. If you use the Cloverleaf “Configure” option to have Cloverleaf build the SQL insert statement, it adds the table name to the each of the fields in the field list. I have found that this breaks SQLite inserts. Here is an example…

Insert into table(table.field1, table.field2) values(1,2)

Sqlite needs the following…

Insert into table(field1, field2) values(1,2)

3. If you are having issues with the Testing Tool working, but the insert failing when you run messages through the tread, pop out to the command line and do an hciss -k h and then hciss -s h. Apparently some database configurations are held in the host server memory.

4. Disallowed Gateway almost always means there is an error in your SQL statement. Sadly, the only way I have found to see what SQL statement is being executed is trial and error. When you fix it, then and only then will it display in the testing tool. This is super frustrating.

[Mike Strout]

Yes, I am using the standard processing and the check_ack script. It is just strange to me that I would be seeing multiple copies of the message sent outbound in the OB SMAT.

[Mike Strout]

Yes, it is pretty clear that I am reaching the timeout. Shouldn’t the previous version of the message be removed from the recovery database as part of the resend process?

[Mike Strout]

I am still wrestling with this lack of ack issue and haven’t had a chance to dig in with a protocol analyzer yet. As this is an AIX box, things are a bit more complicated than they would be on a Windows box.

I do have a fundamental question about the ack process. My expectation is that the following should happen.

1. Message sent, Cloverleaf puts message into Recovery DB and waits for reply.

2. No ack is received in timeout period so, resend message, restart timer, delete original message from recovery db and wait for reply.

3. Continue in this loop until ack is received or thread is restarted.

4. If ack is received, expire timer, write message to SMAT, and remove message from recovery db

5. If thread is restarted, all timers are expired. Upon restart, all messages in the recovery DB are sent using the same ack processing above.

Assuming this is close to right, what I don’t understand is why I am getting multiple copies of messages written to the OB SMAT. My impression was that only messages that are successfully ack’ed are written to SMAT. If this is correct, then the problem must be in step 2 above where the previous copy of the now resent message is deleted from the recovery db.

I heard a while back that the standard check_ack proc had some issues and that there was a new version that works better with Cloverleaf 6+. Can anyone confirm that and point me to it?

[Author]

Replies