I'm using the Stomp Client provided at Google Code from codehaus. I am using it to pass XML messages from the server to the client. This works great except for the fact that every once in a while the Stomp client doesn't get the entire message. It seems to truncate the message.
That's no big deal because I can just ignore an incomplete message. But the problem is that the next message is the continuation of the previous message and the completion of the message is placed in the command property of the message. This of course throws an UNKNOWN STOMP FRAME error. I have hacked around the problem, but I don't think that my hack is a real robust solution to the problem. Has anyone else seen this problem? I'm using ActiveMQ as the message server. The messages coming through do not have a [content-length] header. I think that that is the real problem. Stomp has no way of knowing how long the message is supposed to be without it. It makes an attempt to figure it out, but it's obviously not always correct. It claims that the body is complete when it is not.
