is it closing on the EPIC side? We have a few connections where the vendor will open port, send a message and close the port to where it’s in an opening state.
Is the thread on your side going “down” or “opening”? Is EPIC set up to have a persistant connection? It may be that EPIC has it set on their side to open the connection when there are messages to send and then close the connection when they are through sending.
All of our inbound Epic threads do not connect until a message is sent, i.e., on startup they remain in opening state until first message after starting. That said, once it connects, it stays in an up status until either side is dropped, i.e., Epic Comm daemon or Cloverleaf thread, then the above behaviour is repeated.
.
.