https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34070
--- Comment #10 from David Cook <[email protected]> --- According to the STOMP spec: "The server MAY send ERROR frames if something goes wrong. In this case, it MUST then close the connection just after sending the ERROR frame." However, RabbitMQ has acknowledged that they don't do that, and have several open discussions/issues surrounding this topic. In our case, I'd like to add a content-type to sent messages, so that we're only trying to JSON decode messages marked as "application/json". Plus, if we encounter an ERROR frame rather than a MESSAGE frame, we can kill the connection and let an auto-reconnect happen. -- Now... that idea would probably have fixed my problem with the infinite NACK error loop. But... it wouldn't solve the problem with the infinite connect error. With that one... we'd have to either nullify $conn and do a next() or exit the worker. But... that might be good for a follow-up... baby steps... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
