Notifications
Clear all
Topic starter
Does anyone have any information on socket errors on DTS. We seem to get a lot of them. Below is the error. Any direction would be appreciated.
Socket Communication Information: Channel: Localhost 33070 name: Connection abnormally terminated.
Thanks
Posted : April 21, 2016 3:16 am
Most (I think all) of our inbound DTS interfaces are file based.
I've found DTS TCP connections to be rather finicky. Since DTS is so "reliable," we have a scheduled task to restart the DTS service once per hour. It's a standard service stop & start. When that runs, I found DTS has no problem shutting down in the middle of a TCP session and losing the inbound HL7 message.
If that's what you're seeing, it's nice that it at least generates an error message now.
One guess is that the other end of your interface probably does a service start/stop periodically, and you're seeing DTS complain that the TCP session closed unexpectedly.
Posted : April 21, 2016 4:27 am
I have seen this also if you have a monitoring server (Nagios/nVision/etc...) checking the port.
Not all of the monitors terminate the session properly.
Posted : April 21, 2016 5:38 am
Topic starter
Thanks for your experiences and we will see what happens.
Posted : April 21, 2016 11:23 am
Look at your connection type under the LLogic stations. You will get Socket Channel errors if your lose connection to your interface. If you set the Connection Type to Create connection per transfer, this should cut down on the socket errors.
Posted : April 22, 2016 8:14 am
Topic starter
Appreciate that, I will give it a try.
Posted : April 22, 2016 10:45 am
Once upon a time GE told me that they had a known memory leak and some customers experience and some didn't. We find we have to reboot monthly or it will definitely hit socket error and even restarting service at that point doesn't help. We do shut down the service each night before our snapshot and restart after (on scheduled task) but it will happen monthly regardless if we don't reboot. We have lots of inbound traffic and some out also. Only time we had trouble outside of that was when it was hitting a chaining issue with a chart it was trying to export for HIE and then it would crash each hour when exporting. Good luck!
Posted : May 4, 2016 11:51 am
I know this is a little late in a reply but I saw this looking for another issue...
What I came up with is a set of SQL queries to monitor the DTS status and if its in an error state to take action via powershell. Its all based on SQL jobs and I run it once every 15 minutes to monitor the status based on the SQL tables.
Posted : December 21, 2016 5:25 pm
