Replies: 2 comments
-
|
You can see that the second connection times out instead of getting refused, that's why it takes quite long. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thank you very much for the reply. Thanks ! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
ReconnectInterval=5
SocketConnectHost=127.0.0.1
SocketConnectPort=11502
SocketConnectHost1=192.168.14.55
SocketConnectPort1=11502
HeartBtInt=50
When the above configurations are configured for a session, and if the session is not connected for the first host it tries to connect to the second host. It takes more than 20s to try connecting to the first host again. I would like to know if this is the default behaviour or whether I can control this by changing some other configurations. This is the event log for the scenario. Kindly share if you have any solution on this.
Thanks !
2023-06-02 16:55:45,715 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Session FIX.4.2:SLGM0->TDWL:TDWL-CL schedule is daily, 18:31:00-UTC - 18:25:00-UTC (daily, 00:01:00-IST - 23:55:00-IST)
2023-06-02 16:55:45,716 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Created session: FIX.4.2:SLGM0->TDWL:TDWL-CL
2023-06-02 16:55:45,764 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Configured socket addresses for session: [/127.0.0.1:11502, /192.168.14.55:11502]
2023-06-02 16:55:47,772 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Pending connection not established after 2005 ms.
2023-06-02 16:55:48,772 errorEvent FIX.4.2:SLGM0->TDWL:TDWL-CL: java.net.ConnectException during connection to /127.0.0.1:11502: java.net.ConnectException: Connection refused: no further information (Next retry in 5000 milliseconds)
2023-06-02 16:55:52,781 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Pending connection not established after 2001 ms.
2023-06-02 16:55:55,783 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Pending connection not established after 5003 ms.
2023-06-02 16:55:58,784 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Pending connection not established after 8004 ms.
2023-06-02 16:56:01,785 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Pending connection not established after 11005 ms.
2023-06-02 16:56:04,786 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Pending connection not established after 14006 ms.
2023-06-02 16:56:09,787 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Pending connection not established after 19007 ms.
2023-06-02 16:56:11,790 errorEvent FIX.4.2:SLGM0->TDWL:TDWL-CL: java.net.ConnectException during connection to /192.168.14.55:11502: java.net.ConnectException: Connection timed out: no further information (Next retry in 5000 milliseconds)
2023-06-02 16:56:14,799 errorEvent FIX.4.2:SLGM0->TDWL:TDWL-CL: java.net.ConnectException during connection to /127.0.0.1:11502: java.net.ConnectException: Connection refused: no further information (Next retry in 5000 milliseconds)
2023-06-02 16:56:19,802 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Pending connection not established after 2001 ms.
2023-06-02 16:56:24,803 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Pending connection not established after 7002 ms.
2023-06-02 16:56:29,804 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Pending connection not established after 12003 ms.
2023-06-02 16:56:32,805 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Pending connection not established after 15004 ms.
2023-06-02 16:56:35,806 event FIX.4.2:SLGM0->TDWL:TDWL-CL: Pending connection not established after 18005 ms.
2023-06-02 16:56:38,803 errorEvent FIX.4.2:SLGM0->TDWL:TDWL-CL: java.net.ConnectException during connection to /192.168.14.55:11502: java.net.ConnectException: Connection timed out: no further information (Next retry in 5000 milliseconds)
2023-06-02 16:56:41,815 errorEvent FIX.4.2:SLGM0->TDWL:TDWL-CL: java.net.ConnectException during connection to /127.0.0.1:11502: java.net.ConnectException: Connection refused: no further information (Next retry in 5000 milliseconds)
Beta Was this translation helpful? Give feedback.
All reactions