Comment 0 for bug 1455880

For some cases, when rabbit app cannot be stopped gracefully, the kill -9 command invoked. And there is a situation possible when messages like

2015-05-15T14:21:35.898497+00:00 warning: WARNING: p_rabbitmq-server: stop_server_process(): RMQ-server process (PID=1506
2) stopped by 'kill -9', sorry...
2015-05-15T14:21:35.901624+00:00 err: ERROR: kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

would be recorded. It looks like an empty pid argument is given to the kill command, thus must be fixed