- This topic has 3 replies, 2 voices, and was last updated 16 years, 3 months ago by
.
-
Topic
-
Hi, Does anyone have experience with a Meditech (Magic) based tcp/ip port crashing while sending data to Quovadx? I am dealing with an HL7 Scheduling interface here, it’s a copy of many other scheduling interfaces currently in production and it’s the only interface to keep crashing. I’ve tried many ports, tried sending to different IP’s (Direct to vendor instead of through QDX), attempted traps, tested to see if it was a threshold issue with either Meditech or QDX, created a seperate site for this one thread, and have basically run out of ideas at this point. I don’t know where else to look really. Any advice is welcome..
Thanks everyone!
J.
-
Replies
-
-
-
Hi, I am running version 5.4 on windows server 2003. It’s deffinitely the Meditech side crashing. Part of my problem is that Quovadx isn’t recognizing that. It stays up and eventually locks the port when the Meditech job automatically restarts after the crash. That’s making it hard to troubleshoot this. I’d like to use QDX to troubleshooot, I know there are a lot of TCL tools available to trace this kind of stuff, but I’ve never had to use them.. -
John, It sounds like the Meditech system is crashing and not closing and releasing the port.
There is not much the partner system (Cloverleaf(R)) can do about that. As you indicated, it does not even know the partner has gone away – because it hasn’t. There is still a connection active.
About all you could do on the Cloverleaf(R) side is to set an alert to tell you that you have not received any messages for some time (if you are the server) or that the queue depth is growing (if you are the client).
This really should be diagnosed on the Meditech side in my opinion.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
