DXL client connection to Broker fails after a while
we have some Windows clients with a strange DXL client behaviour. After the deployment of the DXL Client 3.1 the client can establish a DXL connection with the broker. After a day or two the same client ist not able to connect to the Broker anymore. In the dxl_service log on the client we find the following entry:
If we run an uninstall Client-Task of the DXL client and install it again on, the client can establish the connection to the Broker again:
[P7][Debug] DxlConnection: attempting to connect to ssl://10.2.1.76:8883 [P7][Debug] DxlConnection: keep alive 1800 [P7][Information] DxlConnection: MQTTClient_connect succeeded for url = ssl://10.2.1.76:8883
Did somebody exerience such issues?
We have hundreds of clients that are connected to the broker and work fine. But we have about 40-50 clients that are losing the DXL connection to the Broker with the same error in the logs. Alle clients are in the same network with the same policies and settings.
Re: DXL client connection to Broker fails after a while
Do you have any 3rd party security software that may be doing DLL injection?
We have seen this before where something will inject itself into the Winsock DLLs as we are loading them - and that causes us to partially block them. The error you are reporting is the failure to create a basic socket - before it's been bound to any target.
If you can open a SR with support we can capture MERs and look at this further.