|Subject:||Messages after the first fail to be received properly|
I'm connecting to Apache ActiveMQ 5.5.0 with AnyEvent::STOMP. I've already applied the patch for correct content-length on undef bodies, as per my previous bug report. The first MESSAGE to be received will work correctly. All subsequent ones will fail. This appears to be because AE::STOMP is inserting an extra \n in the $raw_headers in _receive_frame(). So instead of them looking like "MESSAGE\n" it looks like "\nMESSAGE\n". Thus, the event is dispatched to the event of type "" rather than MESSAGE.