[DISPATCH-857] Router crash when ctrl-c on router that has a libwebsockets listener connected to a console

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.0
• Component/s: Container
• Assignee: Ted Ross
• Reporter: Ernest Allen
• Created: 16/Oct/17 19:50
• Updated: 22/Jul/21 11:34
• Resolved: 18/Oct/17 15:27

Description

The router will core under the following circumstances:

• checkout the latest proton and dispatch. build and install
• start a router using qpid-dispatch/tests/config-1/A.conf (not as a daemon)
• start a console by browsing to localhost:5673
• after the console connects, ctrl-c out of the router

^C2017-10-16 14:54:36.776194 -0400 SERVER (notice) Shut Down
2017-10-16 14:54:36.776305 -0400 ROUTER_CORE (info) Router Core thread exited
2017-10-16 14:54:36.776639 -0400 SERVER (info) HTTP server thread exit
2017-10-16 14:54:36.776909 -0400 SERVER (info) Connection from 10.10.123.4 (to 0.0.0.0:5673) failed: amqp:connection:framing-error connection aborted
qdrouterd: /home/eallen/qpid-dispatch/src/posix/threading.c:57: sys_mutex_lock: Assertion `result == 0' failed.
Aborted (core dumped)

Since this only happens after a console has connected, it may be related to DISPATCH-855 which causes the 0.8.0 router to crash after the console connection unexpectedly closed.