Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

DTS Socket Errors

Bugs, Known Issues, Open Cases

Last Post by Anonymous 1 second ago

8 Posts

6 Users

0 Reactions

72 Views

RSS

cecild

(@cecild)

Posts: 314

Reputable Member

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

SLHV

(@slhv)

Posts: 478

Honorable Member

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

jkratzer

(@jkratzer)

Posts: 138

Estimable Member

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

cecild

(@cecild)

Posts: 314

Reputable Member

Topic starter

Thanks for your experiences and we will see what happens.

Posted : April 21, 2016 11:23 am

Jennb

(@jennb)

Posts: 2

New Member

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

cecild

(@cecild)

Posts: 314

Reputable Member

Topic starter

Appreciate that, I will give it a try.

Posted : April 22, 2016 10:45 am

jryan

(@jryan)

Posts: 119

Estimable Member

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

vandeber

(@vandeber)

Posts: 19

Eminent Member

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

Share:

24 Forums
9,940 Topics
39.9 K Posts
0 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0