both threads UP

[Bob Schmid]

Start thread_one from box1 for ip 1 and port 1 – goes to UP…downstream systems recieving messages.  🙂

start thread_two from box2 for ip1 and port1 goes to UP….messages queueing….. 😕

running 5.8 on box1 and 5.6 box2 mlp_tcp.pdl…..

any ideas out there..? why did thread two go to up?

have tried this several times for different downstream/servers from different clients at the same time………..consistent?  ❓

Topic

[Richard Hart]

Hi Robert.

Cloverleaf has the ability to allow or not multiple connections (protocol properties multi-server) to a TCP server socket.

If you attempt a connection to a Cloverleaf site, both threads display ‘connect’ information ONLY if the socket is set to multi-server.

I have seen Vendor and ‘home grown’ server sockets created that use the classic ‘multi-server’ socket code available in books, BUT they only work on the first connection.

This is likely what you see, where the socket has accepted the first connection and communicated with this and the second connection has been accepted and ignored.

Note that the Cloverleaf multi-server communication requires knowledge of the connection if you are ACKing.

[Author]

Replies