If replay() throws while a client reconnects, the session stays registered for good, and its keep-alive timer keeps running. With maxSessions set, every later client gets a 503. On 1.1.0 the same throw crashes the process with ERR_HTTP_HEADERS_SENT.
publish() can trigger this by itself. It records an event whose id contains a null character, even though session.push() rejects that id. So every reconnect that replays the event throws.
If
replay()throws while a client reconnects, the session stays registered for good, and its keep-alive timer keeps running. WithmaxSessionsset, every later client gets a 503. On 1.1.0 the same throw crashes the process withERR_HTTP_HEADERS_SENT.publish()can trigger this by itself. It records an event whose id contains a null character, even thoughsession.push()rejects that id. So every reconnect that replays the event throws.