|
|
| Author |
Message |
|
| Guest |
 Posted: Thu Oct 15, 2009 7:49 pm |
 |
|
|
Guest
|
|
| Back to top |
|
| 0x6e6562 |
| Posted: Thu Oct 15, 2009 10:23 pm |
|
|
|
User
Joined: 12 Jul 2007
Posts: 250
|
Sonicsnes,
On Thu, Oct 15, 2009 at 8:48 PM, sonicsnes <nabble@sonicsnes.net> wrote:
>
> I'm relatively new to rabbitmq, but I've recently managed to set up an
> instance of rabbitmq. We're planning on having a couple thousand clients
> connected to the rabbitmq-stomp adapter, but need to have a way to count the
> number (and ip addresses of) the current connections. Running "rabbitmqctl
> list_connections" doesn't seem to pick up on anyone connecting through
> stomp. Any suggestions?
rabbitmqctl addresses the core Rabbit API, of which the AMQP TCP
listeners are a part. The STOMP adapter OTOH sets up its own TCP
listener hierarchy on the STOMP port and delegates decoded STOMP
commands to the corresponding AMQP *channels* within the same VM as
the AMQP broker. The core Rabbit broker has no awareness of any
applications running in the same process space as itself and hence
cannot report on these processes (without any notion of a listener
plugin mechanism). If you really need this management information I
suggest that you either use AMQP instead of STOMP as a wire protocol
or port the TCP supervision functionality to the STOMP adapter.
Ben
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
 
|
| Guest |
| Posted: Thu Oct 15, 2009 10:27 pm |
|
|
|
Guest
|
|
| Back to top |
|
| Guest |
| Posted: Mon Oct 19, 2009 12:53 pm |
|
|
|
Guest
|
Ben Hood wrote:
> rabbitmqctl addresses the core Rabbit API, of which the AMQP TCP
> listeners are a part. The STOMP adapter OTOH sets up its own TCP
> listener hierarchy on the STOMP port and delegates decoded STOMP
> commands to the corresponding AMQP *channels* within the same VM as
> the AMQP broker. The core Rabbit broker has no awareness of any
> applications running in the same process space as itself and hence
> cannot report on these processes (without any notion of a listener
> plugin mechanism).
It shouldn't be too hard to make stomp connections, and connections
created by other plugins, show up in rabbitmqctl, so I have created a
bug to look into that.
Matthias.
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
