incorrect length with tcpip protocol using multi server

[Elisha Gould]

Has anyone seen messages sent by cloverleaf with the incorrect length in the message when using the tcpip protocol when using the Data Options Type ASCII of length 4 (ie the header has 4 bytes for the length).

This has been set up as a multi-server thread, and at the time of the issue, there was a single connection, although it is possible that it was sending and receiving data at the same time.

I have also seen times when messages being sent to cloverleaf have the correct length sent, but the wrong number of bytes read.

Our server is completly utilised when this occurs and I have only started seeing it recently.

For example we are seeing something equivalant from the below for a message:

incomming message

0011TestMessage

outgoing message

0011ThisIsATestMessage

where it should have been

0018ThisIsATestMessage

I believe for this case the length variable is being used for both the incomming and outgoing message, so that timing issue occurs in such a way that the length variable is being overwritten and uses the wrong length.

Is there any known issues with sending/receiving messages simultaneously on the same connection?

What is the best protocol to use to prevent this case?

This issue is occuring on AIX 5.3 Cloverleaf 5.8.5.3

Topic