The message “Proto Err Msg: CLIENTS: 0” is informational and not an error according to Quovadx. If this is confusing for everybody, they will consider changing the message in future releases.
We are using “multi server” to solve a problem with an application that sends a message and then closes the socket to reconnect immediately. Unfortunately, Cloverleaf was taking a second to cleanup the dropped connection and to open the socket again in a listening status. The other application was unable to reconnect in less than a second so it waited for 5 minutes before trying to send the message again. This was causing big bottlenecks (and of course the vendor was unable to change the settings on their side).
The solution was to use “multi server.” Although there is only one application sending to us, it solves the problem of the drops/reconnects.
I imagine that this would also work in special cases where there is a router/firewall and the connection is dropped by the device.
It works great although is not the real intent of this protocol.
