The python client still uses the content length as the primary means of determining the boundaries for message framesets. As the JMS client does not always populate the content length, this results in interop problems between java and python clients.
It isn't clear for me how can I reproduce this bug. Could you write me any instructions?
This is so old I think we should just close it. To verify I think it would be sufficient to run a JMS->python example.