<div dir="ltr">Hi�Matthew<div><br></div><div>There are few already. a message every hour! Please advise</div><div><br></div><div>Thank you</div><div>Mutaz</div><div><br><br><div class="gmail_quote">On Sat, Nov 13, 2010 at 4:00 PM, <span dir="ltr"><<a href="mailto:rabbitmq-discuss-request@lists.rabbitmq.com">rabbitmq-discuss-request@lists.rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Send rabbitmq-discuss mailing list submissions to<br>
� � � �<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
� � � �<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
or, via email, send a message with subject or body 'help' to<br>
� � � �<a href="mailto:rabbitmq-discuss-request@lists.rabbitmq.com">rabbitmq-discuss-request@lists.rabbitmq.com</a><br>
<br>
You can reach the person managing the list at<br>
� � � �<a href="mailto:rabbitmq-discuss-owner@lists.rabbitmq.com">rabbitmq-discuss-owner@lists.rabbitmq.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of rabbitmq-discuss digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
� 1. jsonrpc-channel not showing up under � � �localhost:55672<br>
� � �(???? ?????? / Emil Ivanov)<br>
� 2. Re: jsonrpc-channel not showing up � � � �under � localhost:55672<br>
� � �(Simon MacMullen)<br>
� 3. beam.smp takes a lot of CPU adn memory (Mutaz Qasem)<br>
� 4. Re: beam.smp takes a lot of CPU adn memory (Matthew Sackman)<br>
� 5. Re: Passing null for 'arguments' to queueBind() (Michael Bridgen)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 12 Nov 2010 14:08:55 +0200<br>
From: ???? ?????? / Emil Ivanov � � � � <<a href="mailto:emil.vladev@gmail.com">emil.vladev@gmail.com</a>><br>
Subject: [rabbitmq-discuss] jsonrpc-channel not showing up under<br>
� � � �localhost:55672<br>
To: <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
Message-ID:<br>
� � � �<<a href="mailto:AANLkTinjd6sxv%2BNSFoOehZXDFS_Am1rx_ZTBiB%2BRgFnE@mail.gmail.com">AANLkTinjd6sxv+NSFoOehZXDFS_Am1rx_ZTBiB+RgFnE@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Good day,<br>
<br>
I just installed rabbitmq 2.1.1 via .deb package on Ubuntu 10.10 and<br>
got the .ez files for the jsonrpc-channel and management plugins. When<br>
I visit <a href="http://localhost:55672/" target="_blank">http://localhost:55672/</a> I see Management Console, HTTP API,<br>
Command Line Tool entries. However - there is no entry for<br>
jsonrpc-channel (for the examples). I've managed to get it running<br>
with rabbitmq 1.7, but no luck with 2.1.1. Attaching the logs.<br>
<br>
Regards,<br>
Emil<br>
<br>
--<br>
My place to share my ideas:<br>
<a href="http://bolddream.com" target="_blank">http://bolddream.com</a> (now live :)<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: rabbit.log<br>
Type: text/x-log<br>
Size: 813 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101112/8f19e546/attachment-0001.bin" target="_blank">http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101112/8f19e546/attachment-0001.bin</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: startup_log<br>
Type: application/octet-stream<br>
Size: 3232 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101112/8f19e546/attachment-0001.obj" target="_blank">http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101112/8f19e546/attachment-0001.obj</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 12 Nov 2010 12:18:46 +0000<br>
From: Simon MacMullen <<a href="mailto:simon@rabbitmq.com">simon@rabbitmq.com</a>><br>
Subject: Re: [rabbitmq-discuss] jsonrpc-channel not showing up �under<br>
� � � �localhost:55672<br>
To: <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
Message-ID: <<a href="mailto:4CDD30A6.2050901@rabbitmq.com">4CDD30A6.2050901@rabbitmq.com</a>><br>
Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>
On 12/11/10 12:08, ???? ?????? / Emil Ivanov wrote:<br>
> I just installed rabbitmq 2.1.1 via .deb package on Ubuntu 10.10 and<br>
> got the .ez files for the jsonrpc-channel and management plugins. When<br>
> I visithttp://localhost:55672/ �I see Management Console, HTTP API,<br>
> Command Line Tool entries. However - there is no entry for<br>
> jsonrpc-channel (for the examples). I've managed to get it running<br>
> with rabbitmq 1.7, but no luck with 2.1.1. Attaching the logs.<br>
<br>
Hi Emil. The .ez file for jsonrpc-channel does not install the examples,<br>
since there would be no obvious way to remove them for production use.<br>
And the rpc and js_root contexts don't appear in the list since there's<br>
no point directly clicking on them.<br>
<br>
Unfortunately this does mean it's not exactly obvious that anything is<br>
happening! If you go into the management plugin overview page and expand<br>
"Applications" you should find rabbit_jsonrpc, rabbit_jsonrpc_channel<br>
and rfc4627_jsonrpc applications running.<br>
<br>
I'll have a think about how we can make this clearer.<br>
<br>
Cheers, Simon<br>
<br>
--<br>
Simon MacMullen<br>
Staff Engineer, RabbitMQ<br>
SpringSource, a division of VMware<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 12 Nov 2010 18:56:28 +0400<br>
From: Mutaz Qasem <<a href="mailto:mutazmq@gmail.com">mutazmq@gmail.com</a>><br>
Subject: [rabbitmq-discuss] beam.smp takes a lot of CPU adn memory<br>
To: <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
Message-ID:<br>
� � � �<AANLkTin9_d=<a href="mailto:PNu6HNet_yGv6yU3z%2BLnDJR_zZDNsWboj@mail.gmail.com">PNu6HNet_yGv6yU3z+LnDJR_zZDNsWboj@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hi<br>
<br>
beam.smp is taking ebtween 70% - 90% of my CPU and around 780M RES and 980<br>
VIRT.<br>
<br>
I'm running rabbitmq-server 1.8.1<br>
and Erlang R14A (erts-5.8) [source] [64-bit] [smp:2:2] [rq:2]<br>
[async-threads:0] [hipe] [kernel-poll:false]<br>
<br>
Any ideas please?<br>
<br>
Thank you in advance<br>
Mutaz<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101112/5745b5c9/attachment-0001.htm" target="_blank">http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101112/5745b5c9/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Fri, 12 Nov 2010 15:28:00 +0000<br>
From: Matthew Sackman <<a href="mailto:matthew@rabbitmq.com">matthew@rabbitmq.com</a>><br>
Subject: Re: [rabbitmq-discuss] beam.smp takes a lot of CPU adn memory<br>
To: <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
Message-ID: <<a href="mailto:20101112152800.GV22102@rabbitmq.com">20101112152800.GV22102@rabbitmq.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
On Fri, Nov 12, 2010 at 06:56:28PM +0400, Mutaz Qasem wrote:<br>
> beam.smp is taking ebtween 70% - 90% of my CPU and around 780M RES and 980<br>
> VIRT.<br>
><br>
> I'm running rabbitmq-server 1.8.1<br>
> and Erlang R14A (erts-5.8) [source] [64-bit] [smp:2:2] [rq:2]<br>
> [async-threads:0] [hipe] [kernel-poll:false]<br>
><br>
> Any ideas please?<br>
<br>
Send fewer messages?<br>
<br>
Matthew<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Fri, 12 Nov 2010 17:43:38 +0000<br>
From: Michael Bridgen <<a href="mailto:mikeb@rabbitmq.com">mikeb@rabbitmq.com</a>><br>
Subject: Re: [rabbitmq-discuss] Passing null for 'arguments' to<br>
� � � �queueBind()<br>
To: <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
Message-ID: <<a href="mailto:4CDD7CCA.30509@rabbitmq.com">4CDD7CCA.30509@rabbitmq.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
>> It *is* a problem though when the groups are formed dynamically on<br>
>> a per message basis, i.e. when each consumer has a unique secret<br>
>> token, known to the producer, and the producer constructs the<br>
>> recipient group of the message on the fly by including all the<br>
>> intended recipient's tokens in the message headers.<br>
><br>
> I understand you now, and above is exactly the situation I have. �I<br>
> wonder if a custom exchange type can remove headers from a message<br>
> prior to delivery.<br>
<br>
Here is a design:<br>
<br>
Allow CC and BCC fields* when publishing. �These are given to exchange<br>
types** when routing (i.e., they are part of the envelope); and, the<br>
routing code removes Bcc before actually delivering to queues.<br>
<br>
Full semantics left as an exercise*** for the reader.<br>
<br>
* They would probably have to be put in message headers, but possibly<br>
they could be given specific support in our clients.<br>
<br>
** We'd update direct and topic to take account of them; fanout and<br>
headers don't need to, and other types given be given the fields and do<br>
what they like.<br>
<br>
*** For example, "" is a valid routing key, so how do you send to<br>
multiple recipients just with BCC field?<br>
<br>
<br>
Michael<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br>
<br>
End of rabbitmq-discuss Digest, Vol 42, Issue 40<br>
************************************************<br>
</blockquote></div><br></div></div>