[rabbitmq-discuss] rabbitmq 2.3 and SERVER_START_ARGS

Fri Mar 11 10:29:26 GMT 2011

On 10/03/11 20:22, Brian Thomason wrote:
> Has the SERVER_START_ARGS env var been changed to something else or as
> of 2.3, is there simply no way to change stomp ports without using the
> new config file format?

Hi Brian. No, the SERVER_START_ARGS variable has not changed.

However, this variable basically allows you to add fragments of the 
*new* config format, so the contents of SERVER_START_ARGS will need to 
change - from something like:

SERVER_START_ARGS='-rabbit_stomp listeners [{"a.b.c.d",61613}]'

in 2.2.0 to

SERVER_START_ARGS='-rabbit_stomp tcp_listeners [{"a.b.c.d",61613}]'

in 2.3.1.

(We made this change to make it consistent with the main rabbit AMQP 
configuration.)

Other changes in 2.3.1 in this area:

* The stomp adapter defaults to listening on all interfaces, rather than 
just 127.0.0.1

* You can specify just a port number (e.g. [61613]) to specify all 
interfaces with a different port

Finally, can I ask what benefit you're getting from using the old 
configuration file? We'd like to do away with it at some point, and it 
would be nice to be sure we weren't breaking anything :)

Cheers, Simon

-- 
Simon MacMullen
Staff Engineer, RabbitMQ
SpringSource, a division of VMware