Hi,
I'm stuck with the following problem.
I have a channel with as destination a connector type TCP sender.
This TCP sender will connect with a local running stunnel to be able to have a secure connection with a remote system. In an open TCP connection, only messages from the local system to the remote system will be send (so Mirth Connect will not receive any response messages on application level).
This works under "normal" conditions. However when the internet connect is broken (alias when I remove the UTP cable) stunnel reports the broken internet connection in its logging. However Mirth Connect thinks that sending of a message was successful (because it has actually been received by the local stunnel process), deletes the associated xml file and continues sending messages and deleting xml files.
Is there some way to solve this in Mirth Connect and/or stunnel?
Or should the flow of messages be changed?
With kind regards,
Marco Kemper
Environment:
- Linux
- Mirth Connect Server 3.0.1.7051
- stunnel4
I'm stuck with the following problem.
I have a channel with as destination a connector type TCP sender.
This TCP sender will connect with a local running stunnel to be able to have a secure connection with a remote system. In an open TCP connection, only messages from the local system to the remote system will be send (so Mirth Connect will not receive any response messages on application level).
This works under "normal" conditions. However when the internet connect is broken (alias when I remove the UTP cable) stunnel reports the broken internet connection in its logging. However Mirth Connect thinks that sending of a message was successful (because it has actually been received by the local stunnel process), deletes the associated xml file and continues sending messages and deleting xml files.
Is there some way to solve this in Mirth Connect and/or stunnel?
Or should the flow of messages be changed?
With kind regards,
Marco Kemper
Environment:
- Linux
- Mirth Connect Server 3.0.1.7051
- stunnel4
Messages disappear with Mirth Connect and stunnel in combination with network problem
0 commentaires:
Enregistrer un commentaire