An error occurred when activemq used the stomp Protocol: Unexpected ack received ed for message-ID

When using the stomp package (such as PHP Python Ruby) in some language environments, the following problems may occur:

Unexpected ack received ed for message-ID

This may be caused by two reasons.

1. No Ack is sent in order, which leads activemq to think you are sending an error.

Solution

1) issue ack in order

2) set it to the independent confirmation mode of the client (Client-individual ACK)

See :(Http://issues.apache.org/activemq/browse/AMQ-1874)

2. Incorrect frame Header Format.

Generally, they are redundant spaces, \ r, and so on.
The stomp 1.0 specification is not required, so it is legal.
Stomp 1.1 becomes more strict. This write is illegal, so an error occurred while parsing the frame header.

Solution:

1) Update the driver package to see if the compatibility problem has been solved.

2) modify the source code to regulate the validity of the characters when the key-value of the header is spliced.

Python's Stomper has fixed this compatibility issue in 2.5 +:

Https://github.com/oisinmulvihill/stomper/commit/da64b9d76e39dfe899ded7ab504af26f2842cb77