Heartbeat mechanism makes coilmq unusable with heartbeats enabled

[miyoyo]

According to this part of the STOMP specification, an ERROR must then be followed by the server closing the connection.

I am writing a client and am therefore assuming that servers follow this part of the spec, as soon as an ERROR frame is received, I disconnect and garbage collect my client.

This line should probably just send a "\n" trough the socket.

[mrjbq7]

Perhaps

diff --git a/coilmq/protocol/__init__.py b/coilmq/protocol/__init__.py
index 7bb98f6..8f85e30 100644
--- a/coilmq/protocol/__init__.py
+++ b/coilmq/protocol/__init__.py
@@ -264,8 +264,7 @@ class STOMP11(STOMP10):
         self.timer.stop()
 
     def send_heartbeat(self):
-        # screw it, just send an error frame
-        self.engine.connection.send_frame(ErrorFrame('heartbeat'))
+        self.engine.connection.request.sendall(b'\n')
 
     def receive_heartbeat(self):
         ago = datetime.datetime.now() - self.last_hb

But there appears to be another issue which is if heartbeats are enabled somehow messages stop getting received by the client.