[rabbitmq-discuss] rabbitmqctl status terminates all Web-STOMP client connections
Adam Ashley
aashley at adamashley.name
Tue Dec 18 05:34:13 GMT 2012
We're using RabbitMQ 3.0.1 from the RabbitMQ supplied Debian packages to
provide a link to a HTML based application. This takes advantage of the
Web-STOMP plugin. Currently the client is making use of the iframe-xhr
capabilities of the SockJS library when connecting.
Connections work successfully and will stay up for days at a time until
"rabbitmqctl status" is run on the rabbitmq server. At that point all
connections are terminated and due to the iframe-xhr in sockjs the client
doesn't always see this disconnect.
When rabbitmqctl status is run the following appears within the log files:
=ERROR REPORT==== 18-Dec-2012::13:16:52 ===
** Generic server <0.1627.0> terminating
** Last message in was which_children
** When Server state == {state,
{sockjs_session,
{<0.1624.0>,
[{peername,{{10,253,16,101},57724}},
{sockname,{{10,253,14,30},15674}},
{path,"/stomp/062/bv649208/xhr"},
{headers,
[{'Referer',
"http://mq:15674/stomp/iframe.html?t=1355807743929"}]}]}},
<0.1626.0>,
{resume,#Fun<rabbit_stomp_frame.0.132048132>}}
** Reason for termination ==
** {{case_clause,{odd_request,which_children}},
[{rabbit_ws_client,terminate,2},
{gen_server,terminate,6},
{proc_lib,init_p_do_apply,3}]}
And this is output at the console where the command was run:
root at mq01:~# rabbitmqctl status
Status of node rabbit at mq01 ...
Error: {{{case_clause,{odd_request,which_children}},
[{rabbit_ws_client,terminate,2},
{gen_server,terminate,6},
{proc_lib,init_p_do_apply,3}]},
{gen_server,call,[<4974.1627.0>,which_children,infinity]}}
This only occurs when a Web-STOMP client is connected. Normal STOMP clients
do not have an issue.
Adam Ashley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121217/ee7cda73/attachment.htm>
More information about the rabbitmq-discuss
mailing list