<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=GB2312" http-equiv=Content-Type>
<STYLE>
BLOCKQUOTE {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
LINE-HEIGHT: 1.5; FONT-FAMILY: ËÎÌå; COLOR: #000080; FONT-SIZE: 10.5pt
}
</STYLE>
<META name=GENERATOR content="MSHTML 8.00.7601.17940"></HEAD>
<BODY style="MARGIN: 10px">
<DIV>Hi all,</DIV>
<DIV> </DIV>
<DIV>Today I tried to use RabbitMQ Management HTTP API. I just
followed the example.</DIV>
<DIV> </DIV>
<DIV>
<DIV>curl -i -u guest:guest -H "content-type:application/json" -XPUT -d'{"type":"direct"}' <A
href="http://198.216.26.95:55672/api/exchanges/%2f/my-new-exchange">http://198.216.26.95:55672/api/exchanges/%2f/my-new-exchange</A></DIV>
<DIV> </DIV>
<DIV>HTTP/1.1 204 No Content</DIV>
<DIV>Server: MochiWeb/1.1 WebMachine/1.7 (participate in the frantic)</DIV>
<DIV>Date: Tue, 23 Oct 2012 13:23:32 GMT</DIV>
<DIV>Content-Type: application/json</DIV>
<DIV>Content-Length: 0</DIV>
<DIV> </DIV>
<DIV>It works fine. </DIV>
<DIV> </DIV>
<DIV>However, when I write the JAVA program to do the same thing. My Java code
is:</DIV>
<DIV>
<DIV> </DIV>
<DIV>
<DIV>DefaultHttpClient httpclient = new DefaultHttpClient(); </DIV>
<DIV>httpclient.getCredentialsProvider().setCredentials(new AuthScope("198.216.26.95", 55672),new UsernamePasswordCredentials("guest", "guest"));</DIV>
<DIV>
<DIV>HttpPut httpput = new HttpPut(<A
href="http://198.216.26.95:55672/api/exchanges/%2f/my-new-exchange">http://198.216.26.95:55672/api/exchanges/%2f/my-new-exchange</A>);</DIV>
<DIV>httpput.addHeader("content-type", "application/json");</DIV>
<DIV>JSONObject param = new JSONObject();</DIV>
<DIV>param.put("type", "direct");</DIV>
<DIV>StringEntity entity = new StringEntity(param.toString());</DIV></DIV></DIV>
<DIV>httpput.setEntity(entity);</DIV>
<DIV>HttpResponse response = httpclient.execute(httpput); </DIV>
<DIV> </DIV>
<DIV>It always returned the following exception.
<DIV>org.apache.http.NoHttpResponseException: The target server failed to respond</DIV>
<DIV>
<DIV>at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:95)</DIV>
<DIV>at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:62)</DIV>
<DIV>at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:254)</DIV>
<DIV>at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:289)</DIV>
<DIV>at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:252)</DIV>
<DIV>at org.apache.http.impl.conn.ManagedClientConnectionImpl.receiveResponseHeader(ManagedClientConnectionImpl.java:191)</DIV>
<DIV>at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:300)</DIV>
<DIV>at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:127)</DIV>
<DIV>at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:712)</DIV>
<DIV>at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:517)</DIV>
<DIV>at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)</DIV>
<DIV>at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1066)</DIV>
<DIV>at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044)</DIV>
<DIV>at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035)</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Could anyone help me about this issue?</DIV>
<DIV> </DIV></DIV></DIV></DIV></DIV>
<HR style="WIDTH: 210px; HEIGHT: 1px" align=left color=#b5c4df SIZE=1>
<DIV><SPAN>johnson</SPAN></DIV>
<DIV> </DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV
style="PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKGROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B> <A
href="mailto:rabbitmq-discuss-request@lists.rabbitmq.com">rabbitmq-discuss-request</A></DIV>
<DIV><B>Date:</B> 2012-10-23 19:00</DIV>
<DIV><B>To:</B> <A
href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss</A></DIV>
<DIV><B>Subject:</B> rabbitmq-discuss Digest, Vol 65, Issue
23</DIV></DIV></DIV>
<DIV>
<DIV>Send rabbitmq-discuss mailing list submissions to</DIV>
<DIV>rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV> </DIV>
<DIV>To subscribe or unsubscribe via the World Wide Web, visit</DIV>
<DIV>https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>or, via email, send a message with subject or body 'help' to</DIV>
<DIV>rabbitmq-discuss-request@lists.rabbitmq.com</DIV>
<DIV> </DIV>
<DIV>You can reach the person managing the list at</DIV>
<DIV>rabbitmq-discuss-owner@lists.rabbitmq.com</DIV>
<DIV> </DIV>
<DIV>When replying, please edit your Subject line so it is more specific</DIV>
<DIV>than "Re: Contents of rabbitmq-discuss digest..."</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Today's Topics:</DIV>
<DIV> </DIV>
<DIV> 1. Re: intenal error when connecting from rabbitmq-c</DIV>
<DIV> (Matthias Radestock)</DIV>
<DIV> 2. Re: Upgrading RabbitMQ2.8.6 (Matthias Radestock)</DIV>
<DIV> 3. Re: Rabbit Management HTTP API issue - deleted queues linger</DIV>
<DIV> in API responses (Simon MacMullen)</DIV>
<DIV> 4. Re: PHP Client Library (Matthias Radestock)</DIV>
<DIV> 5. Clustering (chetan dev)</DIV>
<DIV> 6. Re: Clustering (Tim Watson)</DIV>
<DIV> 7. Re: Clustering (chetan dev)</DIV>
<DIV> 8. Adding slave for mirrored queue (Artsiom)</DIV>
<DIV> 9. Re: Clustering (Tim Watson)</DIV>
<DIV> 10. Re: Adding slave for mirrored queue (Tim Watson)</DIV>
<DIV> 11. Re: Adding slave for mirrored queue (Artsiom)</DIV>
<DIV> 12. Re: Adding slave for mirrored queue (Tim Watson)</DIV>
<DIV> 13. Re: Upgrading RabbitMQ2.8.6 (Matt Long)</DIV>
<DIV> 14. Re: Adding slave for mirrored queue (Simon MacMullen)</DIV>
<DIV> 15. Channel thread-safety (Laurent Vauthrin)</DIV>
<DIV> 16. Re: Clustering (chetan dev)</DIV>
<DIV> 17. Re: Channel thread-safety (Michael Klishin)</DIV>
<DIV> 18. Re: RabbitMQ + Messages between virtual machines and physical</DIV>
<DIV> hosts on a cloud (Desta Haileselassie Hagos)</DIV>
<DIV> 19. Re: RabbitMQ + Messages between virtual machines and physical</DIV>
<DIV> hosts on a cloud (Brett Cameron)</DIV>
<DIV> 20. Re: Clustering (Matthias Radestock)</DIV>
<DIV> 21. Re: {SSL upgrade error, timeout} (Dharshan Rangegowda)</DIV>
<DIV> 22. Re: nodename variable and mnesia directory (Elizabeth Liao)</DIV>
<DIV> 23. Memory leak caused by error_logger in 2.8.6? (Travis)</DIV>
<DIV> 24. How to structure Master with many slaves? RPC?? (theBuckWheat)</DIV>
<DIV> 25. Re: Channel thread-safety (Laurent Vauthrin)</DIV>
<DIV> 26. Re: Clustering (Tim Watson)</DIV>
<DIV> 27. Re: RabbitMQ + Messages between virtual machines
and physical</DIV>
<DIV> hosts on a cloud (Tim Watson)</DIV>
<DIV> 28. Re: Clustering (Tim Watson)</DIV>
<DIV> 29. Re: STOMP plugin - durable subscription
limitation</DIV>
<DIV> (Michael Justin)</DIV>
<DIV> 30. Re: nodename variable and mnesia directory (Tim Watson)</DIV>
<DIV> 31. Re: Memory leak caused by error_logger in 2.8.6? (Tim Watson)</DIV>
<DIV> 32. Re: RabbitMQ + Messages between virtual machines
and physical</DIV>
<DIV> hosts on a cloud (Tim Watson)</DIV>
<DIV> 33. Re: Memory leak caused by error_logger in 2.8.6? (Tim Watson)</DIV>
<DIV> 34. Re: Clustering (chetan dev)</DIV>
<DIV> 35. STOMP 1.0 adapter escapes colon as \c (STOMP 1.1
style)</DIV>
<DIV> (Michael Justin)</DIV>
<DIV> 36. Re: How to structure Master with many slaves? RPC??</DIV>
<DIV> (Emile Joubert)</DIV>
<DIV> 37. Re: Clustering (Tim Watson)</DIV>
<DIV> 38. Re: Memory leak caused by error_logger in 2.8.6? (Simon MacMullen)</DIV>
<DIV> 39. Re: Clustering (chetan dev)</DIV>
<DIV> 40. Re: Upgrading RabbitMQ2.8.6 (Simon MacMullen)</DIV>
<DIV> 41. Re: Clustering (Tim Watson)</DIV>
<DIV> 42. Re: STOMP 1.0 adapter escapes colon as \c (STOMP 1.1 style)</DIV>
<DIV> (Emile Joubert)</DIV>
<DIV> 43. Re: STOMP plugin - durable subscription
limitation (Emile Joubert)</DIV>
<DIV> 44. Re: Channel thread-safety (Tim Watson)</DIV>
<DIV> 45. Re: Channel thread-safety (Tim Watson)</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>----------------------------------------------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 1</DIV>
<DIV>Date: Mon, 22 Oct 2012 12:13:31 +0100</DIV>
<DIV>From: Matthias Radestock <matthias@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] intenal error when connecting from</DIV>
<DIV>rabbitmq-c</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: "Gotthard, Petr" <Petr.Gotthard@Honeywell.com></DIV>
<DIV>Message-ID: <50852A5B.2070606@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=windows-1252; format=flowed</DIV>
<DIV> </DIV>
<DIV>Petr,</DIV>
<DIV> </DIV>
<DIV>On 22/10/12 11:52, Gotthard, Petr wrote:</DIV>
<DIV>> While the rabbitmq-c on one machine is fine, on another machine I?m</DIV>
<DIV>> getting ?server connection error 541, message: INTERNAL_ERROR? and the</DIV>
<DIV>> rabbitmq log contains the following entries:</DIV>
<DIV>></DIV>
<DIV>> =ERROR REPORT==== 22-Oct-2012::12:38:17 ===</DIV>
<DIV>></DIV>
<DIV>> AMQP connection <0.2315.0>, channel 1 - error:</DIV>
<DIV>></DIV>
<DIV>> {{badmatch,{undefined,<<40,17,97,112,112,108,105,99,97,116,105,111,110,47,</DIV>
<DIV>></DIV>
<DIV>> 110,111,116,97,109>>}},</DIV>
<DIV>></DIV>
<DIV>> [{rabbit_framing_amqp_0_9_1,decode_properties,2},</DIV>
<DIV> </DIV>
<DIV>Looks like the basic.publish headers/properties are invalid. I suggest </DIV>
<DIV>you try sending a message without any headers/properties. If that works </DIV>
<DIV>then carefully check your code that is constructing the </DIV>
<DIV>amqp_basic_properties_t. In particularly, make sure that you are setting </DIV>
<DIV>the flags correctly. See e.g. </DIV>
<DIV>http://comments.gmane.org/gmane.comp.networking.rabbitmq.general/2717</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV> </DIV>
<DIV>Matthias.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 2</DIV>
<DIV>Date: Mon, 22 Oct 2012 12:21:29 +0100</DIV>
<DIV>From: Matthias Radestock <matthias@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Upgrading RabbitMQ2.8.6</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <50852C39.8040704@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=ISO-8859-1; format=flowed</DIV>
<DIV> </DIV>
<DIV>On 19/10/12 10:24, PSL 88506 wrote:</DIV>
<DIV>> When i try to understand about installation procedure for 2.8.6</DIV>
<DIV>></DIV>
<DIV>> All links are getting redirected to same page with following URL:</DIV>
<DIV>> http://www.rabbitmq.com/download.html</DIV>
<DIV> </DIV>
<DIV>Links will always point to the latest version, which is 2.8.7. I </DIV>
<DIV>recommend you install that rather than 2.8.6. If you really must install </DIV>
<DIV>2.8.6, follow the "Older Versions / Download" link on the download.html </DIV>
<DIV>page.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV> </DIV>
<DIV>Matthias.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 3</DIV>
<DIV>Date: Mon, 22 Oct 2012 12:35:10 +0100</DIV>
<DIV>From: Simon MacMullen <simon@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Rabbit Management HTTP API issue -</DIV>
<DIV>deleted queues linger in API responses</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: Matt Campbell <matt@soupmatt.com></DIV>
<DIV>Message-ID: <50852F6E.5010407@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=ISO-8859-1; format=flowed</DIV>
<DIV> </DIV>
<DIV>No - this certainly should not be happening.</DIV>
<DIV> </DIV>
<DIV>When this is happening, do you see the queues in "rabbitmqctl list_queues"?</DIV>
<DIV> </DIV>
<DIV>Also, can you post logs (including the sasl log) somewhere?</DIV>
<DIV> </DIV>
<DIV>Cheers, Simon</DIV>
<DIV> </DIV>
<DIV>On 18/10/12 19:13, Matt Campbell wrote:</DIV>
<DIV>> On Thursday, October 18, 2012 12:20:54 PM UTC-5, Matt Campbell wrote:</DIV>
<DIV>></DIV>
<DIV>> RabbitMQ version: 2.8.7</DIV>
<DIV>> Erlang version: R14B04</DIV>
<DIV>></DIV>
<DIV>> We are seeing an issue where queues that have been deleted using the</DIV>
<DIV>> amqp basic.delete command tend to linger in the Management console</DIV>
<DIV>> and in calls to the HTTP API. This is an issue for us as we are</DIV>
<DIV>> using that API to discover dynamically created and deleted queues.</DIV>
<DIV>> Can anyone confirm this behavior or offer a suggestion as to how we</DIV>
<DIV>> can mitigate it?</DIV>
<DIV>></DIV>
<DIV>> Thanks,</DIV>
<DIV>></DIV>
<DIV>> Matt</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> I learned some more about what is going on. If I try to redeclare the</DIV>
<DIV>> queue, rabbit returns an error unless I match the queue arguments, as I</DIV>
<DIV>> would expect, but then if I go to delete the queue, I get an error</DIV>
<DIV>> saying it doesn't exist.</DIV>
<DIV>></DIV>
<DIV>> Our setup for this environment is a single node running in cluster mode</DIV>
<DIV>> (we are planning on adding a second node in the near future) and all our</DIV>
<DIV>> queues are declared with x-ha-policy set to all.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Simon MacMullen</DIV>
<DIV>RabbitMQ, VMware</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 4</DIV>
<DIV>Date: Mon, 22 Oct 2012 12:44:47 +0100</DIV>
<DIV>From: Matthias Radestock <matthias@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] PHP Client Library</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <508531AF.4020509@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=ISO-8859-1; format=flowed</DIV>
<DIV> </DIV>
<DIV>Andre,</DIV>
<DIV> </DIV>
<DIV>On 22/10/12 08:23, Andre Torgal wrote:</DIV>
<DIV>> will RabbitMQ list the PECL library in the Get Started page if a repo</DIV>
<DIV>> with examples exists for it.</DIV>
<DIV> </DIV>
<DIV>Yes.</DIV>
<DIV> </DIV>
<DIV>Matthias.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 5</DIV>
<DIV>Date: Mon, 22 Oct 2012 18:34:33 +0530</DIV>
<DIV>From: chetan dev <dev440@gmail.com></DIV>
<DIV>Subject: [rabbitmq-discuss] Clustering</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID:</DIV>
<DIV><CAB0ZxM5P5GDa0j3KbgG14SQqU+Sj8pkppfUp_1q_TgSeX5oEgg@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV> </DIV>
<DIV>Hi,</DIV>
<DIV>I have two nodes clustered together , but when i stop a node using</DIV>
<DIV>rabbbitmqctl stop command and start the broker with rabbitmq-server</DIV>
<DIV>detached commnad</DIV>
<DIV>now when i see the cluster status it shows only one broker running while</DIV>
<DIV>both of the brokers are running fine.</DIV>
<DIV>can anybody explain this or tell me what mistake i am making?</DIV>
<DIV> </DIV>
<DIV>Thanks</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Cheten Dev</DIV>
<DIV> </DIV>
<DIV>B.Tech Final Year</DIV>
<DIV>Dept. of Electrical Engg.</DIV>
<DIV>IIT Delhi, New Delhi</DIV>
<DIV>ph 8527333215</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/5fd4d601/attachment.html></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 6</DIV>
<DIV>Date: Mon, 22 Oct 2012 14:09:38 +0100</DIV>
<DIV>From: Tim Watson <tim@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Clustering</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <578609C0-3747-4EA0-9105-A1F954D27660@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=iso-8859-1</DIV>
<DIV> </DIV>
<DIV>Works for me! ;)</DIV>
<DIV> </DIV>
<DIV>What version(s) of rabbit are you running and can you please post the exact commands you're using to start each node, to stop one of the applications (not the node) and cluster it with the other one and then finally the command you're using to start again.</DIV>
<DIV> </DIV>
<DIV>Cheers</DIV>
<DIV>Tim</DIV>
<DIV> </DIV>
<DIV>On 22 Oct 2012, at 14:04, chetan dev wrote:</DIV>
<DIV> </DIV>
<DIV>> Hi,</DIV>
<DIV>> I have two nodes clustered together , but when i stop a node using rabbbitmqctl stop command and start the broker with rabbitmq-server detached commnad</DIV>
<DIV>> now when i see the cluster status it shows only one broker running while both of the brokers are running fine.</DIV>
<DIV>> can anybody explain this or tell me what mistake i am making?</DIV>
<DIV>> </DIV>
<DIV>> Thanks</DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> -- </DIV>
<DIV>> Cheten Dev </DIV>
<DIV>> </DIV>
<DIV>> B.Tech Final Year</DIV>
<DIV>> Dept. of Electrical Engg.</DIV>
<DIV>> IIT Delhi, New Delhi</DIV>
<DIV>> ph 8527333215</DIV>
<DIV>> </DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 7</DIV>
<DIV>Date: Mon, 22 Oct 2012 18:47:02 +0530</DIV>
<DIV>From: chetan dev <dev440@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Clustering</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID:</DIV>
<DIV><CAB0ZxM6iN1av-2AdBgWVdZB-bF3hrDER8651s90JoQrr5tRCaQ@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV> </DIV>
<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV>Thanks for your reply i am using 2.8.6</DIV>
<DIV>here is what i am doing</DIV>
<DIV>1. two nodes rabbit@SHIKHARM and rabbit@CHETANDEV are clustered</DIV>
<DIV>2. now i stop node rabbit@SHIKHARM using rabbitmqctl stop commnad</DIV>
<DIV>3. now i start the node rabbit@SHIKHARM using rabbitmq-server start commnad</DIV>
<DIV>4. and then i check cluster status it shows only one running node</DIV>
<DIV>Cluster status of node rabbit@CHETANDEV ...</DIV>
<DIV>[{nodes,[{disc,[rabbit@SHIKHARM]},{ram,[rabbit@CHETANDEV]}]},</DIV>
<DIV> {running_nodes,[rabbit@CHETANDEV]}]</DIV>
<DIV>...done.</DIV>
<DIV> </DIV>
<DIV>On Mon, Oct 22, 2012 at 6:39 PM, Tim Watson <tim@rabbitmq.com> wrote:</DIV>
<DIV> </DIV>
<DIV>> Works for me! ;)</DIV>
<DIV>></DIV>
<DIV>> What version(s) of rabbit are you running and can you please post the</DIV>
<DIV>> exact commands you're using to start each node, to stop one of the</DIV>
<DIV>> applications (not the node) and cluster it with the other one and then</DIV>
<DIV>> finally the command you're using to start again.</DIV>
<DIV>></DIV>
<DIV>> Cheers</DIV>
<DIV>> Tim</DIV>
<DIV>></DIV>
<DIV>> On 22 Oct 2012, at 14:04, chetan dev wrote:</DIV>
<DIV>></DIV>
<DIV>> > Hi,</DIV>
<DIV>> > I have two nodes clustered together , but when i stop a node using</DIV>
<DIV>> rabbbitmqctl stop command and start the broker with rabbitmq-server</DIV>
<DIV>> detached commnad</DIV>
<DIV>> > now when i see the cluster status it shows only one broker running</DIV>
<DIV>> while both of the brokers are running fine.</DIV>
<DIV>> > can anybody explain this or tell me what mistake i am making?</DIV>
<DIV>> ></DIV>
<DIV>> > Thanks</DIV>
<DIV>> ></DIV>
<DIV>> ></DIV>
<DIV>> ></DIV>
<DIV>> > --</DIV>
<DIV>> > Cheten Dev</DIV>
<DIV>> ></DIV>
<DIV>> > B.Tech Final Year</DIV>
<DIV>> > Dept. of Electrical Engg.</DIV>
<DIV>> > IIT Delhi, New Delhi</DIV>
<DIV>> > ph 8527333215</DIV>
<DIV>> ></DIV>
<DIV>> > _______________________________________________</DIV>
<DIV>> > rabbitmq-discuss mailing list</DIV>
<DIV>> > rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Cheten Dev</DIV>
<DIV> </DIV>
<DIV>B.Tech Final Year</DIV>
<DIV>Dept. of Electrical Engg.</DIV>
<DIV>IIT Delhi, New Delhi</DIV>
<DIV>ph 8527333215</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/6d857aaa/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 8</DIV>
<DIV>Date: Mon, 22 Oct 2012 16:47:04 +0300</DIV>
<DIV>From: Artsiom <u2.storm@gmail.com></DIV>
<DIV>Subject: [rabbitmq-discuss] Adding slave for mirrored queue</DIV>
<DIV>To: rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>Message-ID: <50854E58.50807@gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="windows-1251"; Format="flowed"</DIV>
<DIV> </DIV>
<DIV>Hi all.</DIV>
<DIV> </DIV>
<DIV>Let me ask question regarding mirrored queues.</DIV>
<DIV>I have a cluster of 8 nodes(node01, node02, node03 ... and etc.).The </DIV>
<DIV>queue is declared as HA withfollowing params:</DIV>
<DIV>x-ha-policy: nodes</DIV>
<DIV>x-ha-policy: rabbit@node01, rabbit@node02, rabbit@node03</DIV>
<DIV> </DIV>
<DIV>Is it possible to add more slavesfor that queuew\o deleting and </DIV>
<DIV>redeclaring. If possible, what side-effects are expected?</DIV>
<DIV>Will other consumers be able to continue receive messages from that </DIV>
<DIV>queue or they'll get cancellation consumer notification?</DIV>
<DIV>I don't want all nodes to be mirrors of that queue (it generates too </DIV>
<DIV>much network traffic).</DIV>
<DIV> </DIV>
<DIV>P.S. Does rabbitmq-c support consumer cancellation notification feature?</DIV>
<DIV> </DIV>
<DIV>--</DIV>
<DIV>Best regards,</DIV>
<DIV>Artsiom</DIV>
<DIV> </DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/1d289091/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 9</DIV>
<DIV>Date: Mon, 22 Oct 2012 15:21:42 +0100</DIV>
<DIV>From: Tim Watson <watson.timothy@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Clustering</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <F0BE6B42-22CA-4517-8858-C402166ADF37@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset="us-ascii"</DIV>
<DIV> </DIV>
<DIV>Yes but how did you cluster them on the first place? You do realise that rabbit nodes are not clustered automatically?</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>On 22 Oct 2012, at 14:17, chetan dev <dev440@gmail.com> wrote:</DIV>
<DIV> </DIV>
<DIV>> Hi,</DIV>
<DIV>> </DIV>
<DIV>> Thanks for your reply i am using 2.8.6</DIV>
<DIV>> here is what i am doing </DIV>
<DIV>> 1. two nodes rabbit@SHIKHARM and rabbit@CHETANDEV are clustered </DIV>
<DIV>> 2. now i stop node rabbit@SHIKHARM using rabbitmqctl stop commnad</DIV>
<DIV>> 3. now i start the node rabbit@SHIKHARM using rabbitmq-server start commnad</DIV>
<DIV>> 4. and then i check cluster status it shows only one running node </DIV>
<DIV>> Cluster status of node rabbit@CHETANDEV ...</DIV>
<DIV>> [{nodes,[{disc,[rabbit@SHIKHARM]},{ram,[rabbit@CHETANDEV]}]},</DIV>
<DIV>> {running_nodes,[rabbit@CHETANDEV]}]</DIV>
<DIV>> ...done.</DIV>
<DIV>> </DIV>
<DIV>> On Mon, Oct 22, 2012 at 6:39 PM, Tim Watson <tim@rabbitmq.com> wrote:</DIV>
<DIV>> Works for me! ;)</DIV>
<DIV>> </DIV>
<DIV>> What version(s) of rabbit are you running and can you please post the exact commands you're using to start each node, to stop one of the applications (not the node) and cluster it with the other one and then finally the command you're using to start again.</DIV>
<DIV>> </DIV>
<DIV>> Cheers</DIV>
<DIV>> Tim</DIV>
<DIV>> </DIV>
<DIV>> On 22 Oct 2012, at 14:04, chetan dev wrote:</DIV>
<DIV>> </DIV>
<DIV>> > Hi,</DIV>
<DIV>> > I have two nodes clustered together , but when i stop a node using rabbbitmqctl stop command and start the broker with rabbitmq-server detached commnad</DIV>
<DIV>> > now when i see the cluster status it shows only one broker running while both of the brokers are running fine.</DIV>
<DIV>> > can anybody explain this or tell me what mistake i am making?</DIV>
<DIV>> ></DIV>
<DIV>> > Thanks</DIV>
<DIV>> ></DIV>
<DIV>> ></DIV>
<DIV>> ></DIV>
<DIV>> > --</DIV>
<DIV>> > Cheten Dev</DIV>
<DIV>> ></DIV>
<DIV>> > B.Tech Final Year</DIV>
<DIV>> > Dept. of Electrical Engg.</DIV>
<DIV>> > IIT Delhi, New Delhi</DIV>
<DIV>> > ph 8527333215</DIV>
<DIV>> ></DIV>
<DIV>> > _______________________________________________</DIV>
<DIV>> > rabbitmq-discuss mailing list</DIV>
<DIV>> > rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>> </DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> -- </DIV>
<DIV>> Cheten Dev </DIV>
<DIV>> </DIV>
<DIV>> B.Tech Final Year</DIV>
<DIV>> Dept. of Electrical Engg.</DIV>
<DIV>> IIT Delhi, New Delhi</DIV>
<DIV>> ph 8527333215</DIV>
<DIV>> </DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/f2244317/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 10</DIV>
<DIV>Date: Mon, 22 Oct 2012 15:24:12 +0100</DIV>
<DIV>From: Tim Watson <watson.timothy@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Adding slave for mirrored queue</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: "rabbitmq-discuss@lists.rabbitmq.com"</DIV>
<DIV><rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <81DBF17F-B324-485B-82DB-151415D01FDA@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset="us-ascii"</DIV>
<DIV> </DIV>
<DIV>Hi</DIV>
<DIV> </DIV>
<DIV>On 22 Oct 2012, at 14:47, Artsiom <u2.storm@gmail.com> wrote:</DIV>
<DIV> </DIV>
<DIV>> Hi all.</DIV>
<DIV>> </DIV>
<DIV>> Let me ask question regarding mirrored queues.</DIV>
<DIV>> I have a cluster of 8 nodes(node01, node02, node03 ... and etc.). The queue is declared as HA with following params:</DIV>
<DIV>> x-ha-policy: nodes</DIV>
<DIV>> x-ha-policy: rabbit@node01, rabbit@node02, rabbit@node03</DIV>
<DIV>> </DIV>
<DIV>> Is it possible to add more slaves for that queue w\o deleting and redeclaring.</DIV>
<DIV> </DIV>
<DIV>In the current version of rabbit no. In the next feature release 3.0 yes, because ha is controlled by policy rather than at queue declaration time and can be changed at runtime. Check out next.rabbitmq.com for more info.</DIV>
<DIV> </DIV>
<DIV>> If possible, what side-effects are expected?</DIV>
<DIV>> Will other consumers be able to continue receive messages from that queue or they'll get cancellation consumer notification?</DIV>
<DIV>> I don't want all nodes to be mirrors of that queue (it generates too much network traffic).</DIV>
<DIV>> </DIV>
<DIV>> P.S. Does rabbitmq-c support consumer cancellation notification feature?</DIV>
<DIV>> </DIV>
<DIV>> --</DIV>
<DIV>> Best regards,</DIV>
<DIV>> Artsiom</DIV>
<DIV>> </DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/7b1050fe/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 11</DIV>
<DIV>Date: Mon, 22 Oct 2012 17:52:16 +0300</DIV>
<DIV>From: Artsiom <u2.storm@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Adding slave for mirrored queue</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: Tim Watson <watson.timothy@gmail.com></DIV>
<DIV>Message-ID: <50855DA0.20008@gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="windows-1251"; Format="flowed"</DIV>
<DIV> </DIV>
<DIV>Tim, thanks for response.</DIV>
<DIV> </DIV>
<DIV>Does this feature available in nightly builds?</DIV>
<DIV>Could you uncover the mystery, when rabbitmq 3.0 release is expected? :)</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>On 10/22/2012 05:24 PM, Tim Watson wrote:</DIV>
<DIV>> Hi</DIV>
<DIV>></DIV>
<DIV>> On 22 Oct 2012, at 14:47, Artsiom <u2.storm@gmail.com </DIV>
<DIV>> <mailto:u2.storm@gmail.com>> wrote:</DIV>
<DIV>></DIV>
<DIV>>> Hi all.</DIV>
<DIV>>></DIV>
<DIV>>> Let me ask question regarding mirrored queues.</DIV>
<DIV>>> I have a cluster of 8 nodes(node01, node02, node03 ... and etc.).The </DIV>
<DIV>>> queue is declared as HA withfollowing params:</DIV>
<DIV>>> x-ha-policy: nodes</DIV>
<DIV>>> x-ha-policy: rabbit@node01, rabbit@node02, rabbit@node03</DIV>
<DIV>>></DIV>
<DIV>>> Is it possible to add more slavesfor that queuew\o deleting and </DIV>
<DIV>>> redeclaring.</DIV>
<DIV>></DIV>
<DIV>> In the current version of rabbit no. In the next feature release 3.0 </DIV>
<DIV>> yes, because ha is controlled by policy rather than at queue </DIV>
<DIV>> declaration time and can be changed at runtime. Check out </DIV>
<DIV>> next.rabbitmq.com <http://next.rabbitmq.com> for more info.</DIV>
<DIV>></DIV>
<DIV>>> If possible, what side-effects are expected?</DIV>
<DIV>>> Will other consumers be able to continue receive messages from that </DIV>
<DIV>>> queue or they'll get cancellation consumer notification?</DIV>
<DIV>>> I don't want all nodes to be mirrors of that queue (it generates too </DIV>
<DIV>>> much network traffic).</DIV>
<DIV>>></DIV>
<DIV>>> P.S. Does rabbitmq-c support consumer cancellation notification feature?</DIV>
<DIV>>></DIV>
<DIV>>> --</DIV>
<DIV>>> Best regards,</DIV>
<DIV>>> Artsiom</DIV>
<DIV>>></DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com </DIV>
<DIV>>> <mailto:rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV> </DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/2dd0a326/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 12</DIV>
<DIV>Date: Mon, 22 Oct 2012 16:30:54 +0100</DIV>
<DIV>From: Tim Watson <watson.timothy@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Adding slave for mirrored queue</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com>,</DIV>
<DIV>Tim Watson <watson.timothy@gmail.com></DIV>
<DIV>Message-ID: <86B6A351-B208-4F74-955F-6897271F6445@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset="us-ascii"</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Artisom,</DIV>
<DIV> </DIV>
<DIV>On 22 Oct 2012, at 15:52, Artsiom <u2.storm@gmail.com> wrote:</DIV>
<DIV> </DIV>
<DIV>> Tim, thanks for response.</DIV>
<DIV>> </DIV>
<DIV>> Does this feature available in nightly builds?</DIV>
<DIV> </DIV>
<DIV>Yes it is!</DIV>
<DIV> </DIV>
<DIV>> Could you uncover the mystery, when rabbitmq 3.0 release is expected? :)</DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV> </DIV>
<DIV>LOL not really, but most of the tickets associated with it are complete so it should be coming soon!</DIV>
<DIV> </DIV>
<DIV>> On 10/22/2012 05:24 PM, Tim Watson wrote:</DIV>
<DIV>>> Hi</DIV>
<DIV>>> </DIV>
<DIV>>> On 22 Oct 2012, at 14:47, Artsiom <u2.storm@gmail.com> wrote:</DIV>
<DIV>>> </DIV>
<DIV>>>> Hi all.</DIV>
<DIV>>>> </DIV>
<DIV>>>> Let me ask question regarding mirrored queues.</DIV>
<DIV>>>> I have a cluster of 8 nodes(node01, node02, node03 ... and etc.). The queue is declared as HA with following params:</DIV>
<DIV>>>> x-ha-policy: nodes</DIV>
<DIV>>>> x-ha-policy: rabbit@node01, rabbit@node02, rabbit@node03</DIV>
<DIV>>>> </DIV>
<DIV>>>> Is it possible to add more slaves for that queue w\o deleting and redeclaring.</DIV>
<DIV>>> </DIV>
<DIV>>> In the current version of rabbit no. In the next feature release 3.0 yes, because ha is controlled by policy rather than at queue declaration time and can be changed at runtime. Check out next.rabbitmq.com for more info.</DIV>
<DIV>>> </DIV>
<DIV>>>> If possible, what side-effects are expected?</DIV>
<DIV>>>> Will other consumers be able to continue receive messages from that queue or they'll get cancellation consumer notification?</DIV>
<DIV>>>> I don't want all nodes to be mirrors of that queue (it generates too much network traffic).</DIV>
<DIV>>>> </DIV>
<DIV>>>> P.S. Does rabbitmq-c support consumer cancellation notification feature?</DIV>
<DIV>>>> </DIV>
<DIV>>>> --</DIV>
<DIV>>>> Best regards,</DIV>
<DIV>>>> Artsiom</DIV>
<DIV>>>> </DIV>
<DIV>>>> _______________________________________________</DIV>
<DIV>>>> rabbitmq-discuss mailing list</DIV>
<DIV>>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>>> </DIV>
<DIV>>> </DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>> </DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/1b7d75e5/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 13</DIV>
<DIV>Date: Mon, 22 Oct 2012 09:07:36 -0700</DIV>
<DIV>From: Matt Long <matt@crocodoc.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Upgrading RabbitMQ2.8.6</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID:</DIV>
<DIV><CAFX3A=1HJW68iyzJNE15QxwUyP-HG=QcC711ueWV68-JahxwsQ@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV> </DIV>
<DIV>While we're on the topic of older versions, it appears they are removed</DIV>
<DIV>from the RabbitMQ APT repository; only the newest version is ever</DIV>
<DIV>available. Is this done on purpose? It has led to some issues for us since</DIV>
<DIV>we specify explicit package versions in our provisioning system and</DIV>
<DIV>occasionally they'll no longer be there!</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Matt</DIV>
<DIV> </DIV>
<DIV>On Mon, Oct 22, 2012 at 4:21 AM, Matthias Radestock</DIV>
<DIV><matthias@rabbitmq.com>wrote:</DIV>
<DIV> </DIV>
<DIV>> On 19/10/12 10:24, PSL 88506 wrote:</DIV>
<DIV>></DIV>
<DIV>>> When i try to understand about installation procedure for 2.8.6</DIV>
<DIV>>></DIV>
<DIV>>> All links are getting redirected to same page with following URL:</DIV>
<DIV>>> http://www.rabbitmq.com/**download.html<http://www.rabbitmq.com/download.html></DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>> Links will always point to the latest version, which is 2.8.7. I recommend</DIV>
<DIV>> you install that rather than 2.8.6. If you really must install 2.8.6,</DIV>
<DIV>> follow the "Older Versions / Download" link on the download.html page.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> Regards,</DIV>
<DIV>></DIV>
<DIV>> Matthias.</DIV>
<DIV>> ______________________________**_________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.**rabbitmq.com<rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss></DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Matt Long</DIV>
<DIV>Cofounder and Lead Developer</DIV>
<DIV>crocodoc.com</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/b9f3889b/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 14</DIV>
<DIV>Date: Mon, 22 Oct 2012 17:13:41 +0100</DIV>
<DIV>From: Simon MacMullen <simon@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Adding slave for mirrored queue</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <508570B5.5000501@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=ISO-8859-1; format=flowed</DIV>
<DIV> </DIV>
<DIV>On 22/10/12 14:47, Artsiom wrote:</DIV>
<DIV>> Is it possible to add more slavesfor that queuew\o deleting and</DIV>
<DIV>> redeclaring.</DIV>
<DIV> </DIV>
<DIV>As Tim notes, not until 3.0.</DIV>
<DIV> </DIV>
<DIV>> If possible, what side-effects are expected?</DIV>
<DIV> </DIV>
<DIV>The same as with adding a new cluster node with x-ha-policy:all in 2.8.x </DIV>
<DIV>- the new mirror will be initially unsynchronised and will become </DIV>
<DIV>synchronised when all old messages have been consumed. Producers and </DIV>
<DIV>consumers won't see any side effects when the new mirror comes on line.</DIV>
<DIV> </DIV>
<DIV>> Will other consumers be able to continue receive messages from that</DIV>
<DIV>> queue or they'll get cancellation consumer notification?</DIV>
<DIV> </DIV>
<DIV>They will continue to receive messages.</DIV>
<DIV> </DIV>
<DIV>Cheers, Simon</DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Simon MacMullen</DIV>
<DIV>RabbitMQ, VMware</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 15</DIV>
<DIV>Date: Mon, 22 Oct 2012 15:05:42 -0400</DIV>
<DIV>From: Laurent Vauthrin <lvauthrin@gmail.com></DIV>
<DIV>Subject: [rabbitmq-discuss] Channel thread-safety</DIV>
<DIV>To: rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>Message-ID:</DIV>
<DIV><CAM8Y7yBqrHE8kvF38htNLnqZ3CSCGqkUQLJoaTwDK0p0qfWpoQ@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV> </DIV>
<DIV>Hello,</DIV>
<DIV> </DIV>
<DIV>I've done some searching but can't seem to answer a couple of questions.</DIV>
<DIV> In the API guide, I saw:</DIV>
<DIV> </DIV>
<DIV>"Channel instances are safe for use by multiple threads. Requests into a</DIV>
<DIV>Channel are serialized, with only one thread being able to run a command on</DIV>
<DIV>the Channel at a time. Even so, applications should prefer using a Channel</DIV>
<DIV>per thread instead of sharing the same Channel across multiple threads."</DIV>
<DIV> </DIV>
<DIV>And in the Javadocs for Channel, I saw:</DIV>
<DIV> </DIV>
<DIV>"While a Channel can be used by multiple threads, it's important to ensure</DIV>
<DIV>that only one thread executes a command at once. Concurrent execution of</DIV>
<DIV>commands will likely cause an UnexpectedFrameError to be thrown."</DIV>
<DIV> </DIV>
<DIV>Currently, our service shares the same channel across each request thread</DIV>
<DIV>and we synchronize the call to 'basicPublish'. Looking at the basicPublish</DIV>
<DIV>code, it looks like the sequence number member variable is not thread safe</DIV>
<DIV>but it doesn't affect us since we're not ack'ing our messages.</DIV>
<DIV> </DIV>
<DIV>My questions are:</DIV>
<DIV>1. Should we be using a channel per thread considering that we're</DIV>
<DIV>synchronizing the basicPublish call anyway?</DIV>
<DIV>2. Can we just share one channel across all threads and not synchronize the</DIV>
<DIV>call to basicPublish?</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Laurent</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/ab4de8ca/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 16</DIV>
<DIV>Date: Tue, 23 Oct 2012 00:58:33 +0530</DIV>
<DIV>From: chetan dev <dev440@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Clustering</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID:</DIV>
<DIV><CAB0ZxM7=S7ZnhkrAYhjzZURJO07KyMmfqap+gV67eTUEQvJDuA@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV> </DIV>
<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV>Yes i clustered them as given on rabbitmq clustering documentation for e.g</DIV>
<DIV>on the first place both nodes are running</DIV>
<DIV>now i stopped app using rabbitmqctl stop_app then i reset that node than i</DIV>
<DIV>clusterd that node with another using rabbitmqctl cluster rabbit@SHIKHARM</DIV>
<DIV>then i started the node using rabbitmqctl start_app</DIV>
<DIV>when i checked the cluster status it was showing fine then i did as i</DIV>
<DIV>mentioned earlier</DIV>
<DIV> </DIV>
<DIV>Thanks</DIV>
<DIV> </DIV>
<DIV>On Mon, Oct 22, 2012 at 7:51 PM, Tim Watson <watson.timothy@gmail.com>wrote:</DIV>
<DIV> </DIV>
<DIV>> Yes but how did you cluster them on the first place? You do realise that</DIV>
<DIV>> rabbit nodes are not clustered automatically?</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> On 22 Oct 2012, at 14:17, chetan dev <dev440@gmail.com> wrote:</DIV>
<DIV>></DIV>
<DIV>> Hi,</DIV>
<DIV>></DIV>
<DIV>> Thanks for your reply i am using 2.8.6</DIV>
<DIV>> here is what i am doing</DIV>
<DIV>> 1. two nodes rabbit@SHIKHARM and rabbit@CHETANDEV are clustered</DIV>
<DIV>> 2. now i stop node rabbit@SHIKHARM using rabbitmqctl stop commnad</DIV>
<DIV>> 3. now i start the node rabbit@SHIKHARM using rabbitmq-server start</DIV>
<DIV>> commnad</DIV>
<DIV>> 4. and then i check cluster status it shows only one running node</DIV>
<DIV>> Cluster status of node rabbit@CHETANDEV ...</DIV>
<DIV>> [{nodes,[{disc,[rabbit@SHIKHARM]},{ram,[rabbit@CHETANDEV]}]},</DIV>
<DIV>> {running_nodes,[rabbit@CHETANDEV]}]</DIV>
<DIV>> ...done.</DIV>
<DIV>></DIV>
<DIV>> On Mon, Oct 22, 2012 at 6:39 PM, Tim Watson <tim@rabbitmq.com> wrote:</DIV>
<DIV>></DIV>
<DIV>>> Works for me! ;)</DIV>
<DIV>>></DIV>
<DIV>>> What version(s) of rabbit are you running and can you please post the</DIV>
<DIV>>> exact commands you're using to start each node, to stop one of the</DIV>
<DIV>>> applications (not the node) and cluster it with the other one and then</DIV>
<DIV>>> finally the command you're using to start again.</DIV>
<DIV>>></DIV>
<DIV>>> Cheers</DIV>
<DIV>>> Tim</DIV>
<DIV>>></DIV>
<DIV>>> On 22 Oct 2012, at 14:04, chetan dev wrote:</DIV>
<DIV>>></DIV>
<DIV>>> > Hi,</DIV>
<DIV>>> > I have two nodes clustered together , but when i stop a node using</DIV>
<DIV>>> rabbbitmqctl stop command and start the broker with rabbitmq-server</DIV>
<DIV>>> detached commnad</DIV>
<DIV>>> > now when i see the cluster status it shows only one broker running</DIV>
<DIV>>> while both of the brokers are running fine.</DIV>
<DIV>>> > can anybody explain this or tell me what mistake i am making?</DIV>
<DIV>>> ></DIV>
<DIV>>> > Thanks</DIV>
<DIV>>> ></DIV>
<DIV>>> ></DIV>
<DIV>>> ></DIV>
<DIV>>> > --</DIV>
<DIV>>> > Cheten Dev</DIV>
<DIV>>> ></DIV>
<DIV>>> > B.Tech Final Year</DIV>
<DIV>>> > Dept. of Electrical Engg.</DIV>
<DIV>>> > IIT Delhi, New Delhi</DIV>
<DIV>>> > ph 8527333215</DIV>
<DIV>>> ></DIV>
<DIV>>> > _______________________________________________</DIV>
<DIV>>> > rabbitmq-discuss mailing list</DIV>
<DIV>>> > rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>>></DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> --</DIV>
<DIV>> Cheten Dev</DIV>
<DIV>></DIV>
<DIV>> B.Tech Final Year</DIV>
<DIV>> Dept. of Electrical Engg.</DIV>
<DIV>> IIT Delhi, New Delhi</DIV>
<DIV>> ph 8527333215</DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Cheten Dev</DIV>
<DIV> </DIV>
<DIV>B.Tech Final Year</DIV>
<DIV>Dept. of Electrical Engg.</DIV>
<DIV>IIT Delhi, New Delhi</DIV>
<DIV>ph 8527333215</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121023/025d40da/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 17</DIV>
<DIV>Date: Mon, 22 Oct 2012 23:46:23 +0400</DIV>
<DIV>From: Michael Klishin <michael.s.klishin@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Channel thread-safety</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID:</DIV>
<DIV><CAE3HoVTr6esOVC4A6PkKBiZm__PO5=uB-7Hj=oXyKN_5eDtdbg@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="utf-8"</DIV>
<DIV> </DIV>
<DIV>2012/10/22 Laurent Vauthrin <lvauthrin@gmail.com></DIV>
<DIV> </DIV>
<DIV>> My questions are:</DIV>
<DIV>> 1. Should we be using a channel per thread considering that we're</DIV>
<DIV>> synchronizing the basicPublish call anyway?</DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV>Yes. Channels are just integer on the wire and a little bit of memory</DIV>
<DIV>allocated on the JVM heap. They are very cheap</DIV>
<DIV>for all intents and purposes and you are much more likely to max out your</DIV>
<DIV>OS and hardware resources (assuming 1 channel per JVM thread) before</DIV>
<DIV>you run into issues with channel objects.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>> 2. Can we just share one channel across all threads and not synchronize</DIV>
<DIV>> the call to basicPublish?</DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>No. The real issue with shared channels is that large messages will result</DIV>
<DIV>in multiple protocol frames being sent</DIV>
<DIV>for a single basicPublish operation. When publishing on the same channel</DIV>
<DIV>from multiple threads, this may result</DIV>
<DIV>in frames being delivered out of order:</DIV>
<DIV> </DIV>
<DIV>T1 => basicPublish => [Frame11] [Frame12] [Frame13]</DIV>
<DIV>T2 => basicPublish => [Frame21] [Frame22] [Frame23]</DIV>
<DIV> </DIV>
<DIV>may result in the following delivery order, all on the same channel:</DIV>
<DIV> </DIV>
<DIV>[Frame11][Frame21][Frame12][Frame13][Frame22][Frame23]</DIV>
<DIV> </DIV>
<DIV>and because all frames are on the same channel, RabbitMQ won't be able to</DIV>
<DIV>tell how to reconstruct your messages.</DIV>
<DIV>-- </DIV>
<DIV>MK</DIV>
<DIV> </DIV>
<DIV>http://github.com/michaelklishin</DIV>
<DIV>http://twitter.com/michaelklishin</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/9625fb67/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 18</DIV>
<DIV>Date: Mon, 22 Oct 2012 21:50:04 +0200</DIV>
<DIV>From: Desta Haileselassie Hagos <deshai-0@student.ltu.se></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] RabbitMQ + Messages between virtual</DIV>
<DIV>machines and physical hosts on a cloud</DIV>
<DIV>To: rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>Message-ID:</DIV>
<DIV><CAKiRAqUZZyg4bqvsGEeH8a-+wwS0m=8sC9tJJ6JUMB1T1V1eQg@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV> </DIV>
<DIV>Dear Sir/Madam,</DIV>
<DIV> </DIV>
<DIV>The problem is that I am not able to send and receive messages between the</DIV>
<DIV>Virtual machines and the physical hosts on my cloud. I want to receive full</DIV>
<DIV>information by manipulating the VMs APIs if it is possible.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>></DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/c8eb2876/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 19</DIV>
<DIV>Date: Tue, 23 Oct 2012 09:10:05 +1300</DIV>
<DIV>From: Brett Cameron <brett.r.cameron@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] RabbitMQ + Messages between virtual</DIV>
<DIV>machines and physical hosts on a cloud</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID:</DIV>
<DIV><CALPqkipaNufyui=8F522qDrX1A4P66FwtQ_Z4jWrgz+3Lv9ToA@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV> </DIV>
<DIV>Desta,</DIV>
<DIV> </DIV>
<DIV>Have you looked at the security profile associated with your VM's? Is it</DIV>
<DIV>possible that port 5672 is blocked?</DIV>
<DIV> </DIV>
<DIV>Brett</DIV>
<DIV> </DIV>
<DIV>On Tue, Oct 23, 2012 at 8:50 AM, Desta Haileselassie Hagos <</DIV>
<DIV>deshai-0@student.ltu.se> wrote:</DIV>
<DIV> </DIV>
<DIV>> Dear Sir/Madam,</DIV>
<DIV>></DIV>
<DIV>> The problem is that I am not able to send and receive messages between the</DIV>
<DIV>> Virtual machines and the physical hosts on my cloud. I want to receive full</DIV>
<DIV>> information by manipulating the VMs APIs if it is possible.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121023/1f36fb06/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 20</DIV>
<DIV>Date: Mon, 22 Oct 2012 21:26:58 +0100</DIV>
<DIV>From: Matthias Radestock <matthias@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Clustering</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <5085AC12.5060409@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=ISO-8859-1; format=flowed</DIV>
<DIV> </DIV>
<DIV>On 22/10/12 20:28, chetan dev wrote:</DIV>
<DIV>>> here is what i am doing</DIV>
<DIV>>> 1. two nodes rabbit@SHIKHARM and rabbit@CHETANDEV are clustered</DIV>
<DIV> </DIV>
<DIV>yes, but...</DIV>
<DIV> </DIV>
<DIV>>> i clustered them as given on rabbitmq clustering documentation for e.g</DIV>
<DIV>>> on the first place both nodes are running</DIV>
<DIV>>> now i stopped app using rabbitmqctl stop_app then i reset that node than</DIV>
<DIV>>> i clusterd that node with another using rabbitmqctl cluster rabbit@SHIKHARM</DIV>
<DIV>>> then i started the node using rabbitmqctl start_app</DIV>
<DIV>>> when i checked the cluster status it was showing fine then i did as i</DIV>
<DIV>>> mentioned earlier</DIV>
<DIV> </DIV>
<DIV>That will make rabbit@CHETANDEV a *ram* node. To make both nodes disk </DIV>
<DIV>nodes the node itself would have to be mentioned in the cluster command </DIV>
<DIV>too, i.e. 'rabbitmqctl cluster rabbit@SHIKHAR rabbit@CHETANDEV'.</DIV>
<DIV> </DIV>
<DIV>>> 2. now i stop node rabbit@SHIKHARM using rabbitmqctl stop commnad</DIV>
<DIV>>> 3. now i start the node rabbit@SHIKHARM using rabbitmq-server</DIV>
<DIV>>> start commnad</DIV>
<DIV> </DIV>
<DIV>You have just stopped and restarted the clusters' only disk node. Rabbit </DIV>
<DIV>clusters won't function properly if they have only ram nodes.</DIV>
<DIV> </DIV>
<DIV>>> 4. and then i check cluster status it shows only one running node</DIV>
<DIV>>> Cluster status of node rabbit@CHETANDEV ...</DIV>
<DIV>>> [{nodes,[{disc,[rabbit@SHIKHARM]},{ram,[rabbit@CHETANDEV]}]},</DIV>
<DIV>>> {running_nodes,[rabbit@CHETANDEV]}]</DIV>
<DIV>>> ...done.</DIV>
<DIV> </DIV>
<DIV>Try running that command against rabbit@SHIKHARM. I suspect it will tell </DIV>
<DIV>you that it only knows about itself.</DIV>
<DIV> </DIV>
<DIV>Anyway, I suggest you change your cluster configuration s.t. both nodes </DIV>
<DIV>are disk nodes.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV> </DIV>
<DIV>Matthias.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 21</DIV>
<DIV>Date: Mon, 22 Oct 2012 13:48:36 -0700</DIV>
<DIV>From: Dharshan Rangegowda <dharshanr@scalegrid.net></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] {SSL upgrade error, timeout}</DIV>
<DIV>To: Emile Joubert <emile@rabbitmq.com></DIV>
<DIV>Cc: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID:</DIV>
<DIV><CAC3-Q1RBiLnjMCtuACu-L4_ZM3H7P6+B=LPOyvzHOWQ6yaVsgQ@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="utf-8"</DIV>
<DIV> </DIV>
<DIV>Hi Emile,</DIV>
<DIV> </DIV>
<DIV>I ran through the troubleshooting wizard and the openssl connection test</DIV>
<DIV>passes - so that makes me think it is not a network issue. However my java</DIV>
<DIV>client still fails with the "Remote host closed connection during</DIV>
<DIV>handshake" error. I have included the results of the connection test below.</DIV>
<DIV>Any other thoughts on how I can debug this?</DIV>
<DIV> </DIV>
<DIV>C:\temp>openssl s_client -connect 199.71.180.59:5671 -CAfile ssltest.pem</DIV>
<DIV>CONNECTED(00000003)</DIV>
<DIV>depth=1 /CN=ScaleGridCA</DIV>
<DIV>verify return:1</DIV>
<DIV>depth=0 /CN=i-19-483-VM/O=server</DIV>
<DIV>verify return:1</DIV>
<DIV>---</DIV>
<DIV>Certificate chain</DIV>
<DIV> 0 s:/CN=i-19-483-VM/O=server</DIV>
<DIV> i:/CN=ScaleGridCA</DIV>
<DIV> 1 s:/CN=ScaleGridCA</DIV>
<DIV> i:/CN=ScaleGridCA</DIV>
<DIV>---</DIV>
<DIV>Server certificate</DIV>
<DIV>-----BEGIN CERTIFICATE-----</DIV>
<DIV>MIIC5zCCAc+gAwIBAgIBNDANBgkqhkiG9w0BAQUFADAWMRQwEgYDVQQDEwtTY2Fs</DIV>
<DIV>ZUdyaWRDQTAeFw0xMjEwMjIxNjIxNTJaFw0xMzEwMjIxNjIxNTJaMCcxFDASBgNV</DIV>
<DIV>BAMTC2ktMTktNDgzLVZNMQ8wDQYDVQQKEwZzZXJ2ZXIwggEiMA0GCSqGSIb3DQEB</DIV>
<DIV>AQUAA4IBDwAwggEKAoIBAQDX7e0Jql/WTD7OUDTIQmg+igwhiVO+17QBuDkgSsQ/</DIV>
<DIV>9nRJSCZzEKC9guH7V+Veq8UG9G2brqwF10jzuZSOq3CGaBWH+F5KE/U+q2yuR3kt</DIV>
<DIV>sOLz6wgMgYnobI1SWjvlkbwYKhgnv689m58Ub5lTISB3aKwT4C0ilnWBbF0v61mq</DIV>
<DIV>TFtjwDRAbCPXl9HwbBFoeLpTsiRu76VXWkA6pv9Ndl4hhcg2YLGwWAOdZO2/NUCB</DIV>
<DIV>QjqrHOir9ekjmpjWMQmWakN61/ckFuuFtGLOqrcujbRuVpAFFWGd53/quCZ+WKNw</DIV>
<DIV>81ZdafFnUSI8ioK2sHGQFxsQKNkpaRuE2/YbrLam+4HPAgMBAAGjLzAtMAkGA1Ud</DIV>
<DIV>EwQCMAAwCwYDVR0PBAQDAgUgMBMGA1UdJQQMMAoGCCsGAQUFBwMBMA0GCSqGSIb3</DIV>
<DIV>DQEBBQUAA4IBAQBqBdvs5eHfVbh8jtp3KF/Q/UG/RtMBrkBnlFWLdBKbhYbWCC1K</DIV>
<DIV>5VncFIpQQ2K44G+RWaqMpPgwj4AZso83/JXn11b52ZxGdR8iogrAX4vWw41CNKfr</DIV>
<DIV>VX0jj4/TPlwFvdS9Jzd3w/NAvLgQ1JXZdBaWxAagfXl8++5nVdC94sj4GNkrCwyN</DIV>
<DIV>r4zBiA6BOsmznVLBLjpoj3WLlrJDGZCTv+PSHDplZtuquDyl37PLOG6F2WUFAxaL</DIV>
<DIV>vhj7zKVTGIj7ESXuNYKnTSyLEkxvrlWdKooJKmH+v5xxEM6H2PqFcS/LGwIaUuxc</DIV>
<DIV>26AKWBnVcK+Pd86765KirNUwf7Fm2ChKwj9M</DIV>
<DIV>-----END CERTIFICATE-----</DIV>
<DIV>subject=/CN=i-19-483-VM/O=server</DIV>
<DIV>issuer=/CN=ScaleGridCA</DIV>
<DIV>---</DIV>
<DIV>No client certificate CA names sent</DIV>
<DIV>---</DIV>
<DIV>SSL handshake has read 1632 bytes and written 444 bytes</DIV>
<DIV>---</DIV>
<DIV>New, TLSv1/SSLv3, Cipher is AES256-SHA</DIV>
<DIV>Server public key is 2048 bit</DIV>
<DIV>Compression: NONE</DIV>
<DIV>Expansion: NONE</DIV>
<DIV>SSL-Session:</DIV>
<DIV> Protocol : TLSv1</DIV>
<DIV> Cipher : AES256-SHA</DIV>
<DIV> Session-ID:</DIV>
<DIV>A0F1A911ED174A49B8AACDD54C3F21C1FD332949D892EEDABF84479DC21BB22D</DIV>
<DIV> Session-ID-ctx:</DIV>
<DIV> Master-Key:</DIV>
<DIV>8FCF38B3652F0A2E6BA8EEBACF2F7387C84416DDCC365A4FF8A4A4FA4B06343DEE463499007DDD03E1155A4A4D8317EE</DIV>
<DIV> Key-Arg : None</DIV>
<DIV> Start Time: 1350938613</DIV>
<DIV> Timeout : 300 (sec)</DIV>
<DIV> Verify return code: 0 (ok)</DIV>
<DIV>---</DIV>
<DIV>12345678</DIV>
<DIV>AMQP ?closed</DIV>
<DIV> </DIV>
<DIV>On Mon, Oct 22, 2012 at 2:24 AM, Emile Joubert <emile@rabbitmq.com> wrote:</DIV>
<DIV> </DIV>
<DIV>> Hi,</DIV>
<DIV>></DIV>
<DIV>> On 21/10/12 21:23, dharshanr wrote:</DIV>
<DIV>> > =ERROR REPORT==== 21-Oct-2012::09:12:49 ===</DIV>
<DIV>> > error on AMQP connection <0.7614.0>: {ssl_upgrade_error,timeout}</DIV>
<DIV>></DIV>
<DIV>> Are you sure the problem is not network-related?</DIV>
<DIV>></DIV>
<DIV>> > The certs are self signed certs and not trusted. Any thoughts on how I</DIV>
<DIV>> > can debug this error?</DIV>
<DIV>></DIV>
<DIV>> It is strange that a working setup stops working suddenly. The tips in</DIV>
<DIV>> the SSL troubleshooting guide might provide more debugging information:</DIV>
<DIV>></DIV>
<DIV>> http://www.rabbitmq.com/troubleshooting-ssl.html</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> -Emile</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>regards,</DIV>
<DIV>Dharshan.</DIV>
<DIV>www.scalegrid.net</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/75aee49f/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 22</DIV>
<DIV>Date: Mon, 22 Oct 2012 22:14:40 +0000</DIV>
<DIV>From: Elizabeth Liao <eliao@seegrid.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] nodename variable and mnesia directory</DIV>
<DIV>To: Tim Watson <tim@rabbitmq.com>, Discussions about RabbitMQ</DIV>
<DIV><rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID:</DIV>
<DIV><E94F626F5C43D14F8B8479C5EBD79038A85DDCE1@vmexchange02.seegrid.local></DIV>
<DIV>Content-Type: text/plain; charset="us-ascii"</DIV>
<DIV> </DIV>
<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV>This is what I tried</DIV>
<DIV> * I start running rabbit with no NODENAME set and entered the following commands</DIV>
<DIV> * rabbitmqctl stop</DIV>
<DIV> * /etc/init.d/rabbitmq-server stop</DIV>
<DIV> * epmd -kill ( Is this correct? I didn't see a restart in the documentation )</DIV>
<DIV> * In /etc/hosts changed line from 127.0.1.1 <oldhostname> <oldhostname>.localdomain -> 127.0.1.1 <newhostname> <newhostname>.localdomain</DIV>
<DIV> * in /etc/sysconfig/network changed HOSTNAME=<oldhostname> -> HOSTNAME=<newhostname></DIV>
<DIV> * /bin/hostname <newhostname></DIV>
<DIV> * /etc/init.d/rabbitmq-server start</DIV>
<DIV> </DIV>
<DIV>The error I get is this:</DIV>
<DIV>Activating RabbitMQ plugins ...</DIV>
<DIV>3 plugins activated:</DIV>
<DIV>* amqp_client-2.8.6</DIV>
<DIV>* erlando-2.8.6</DIV>
<DIV>* rabbitmq_shovel-2.8.6</DIV>
<DIV> </DIV>
<DIV>ERROR: epmd error for host "<oldhostname>": nxdomain (non-existing domain)</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>________________________________________</DIV>
<DIV>From: Tim Watson [tim@rabbitmq.com]</DIV>
<DIV>Sent: Monday, October 22, 2012 6:41 AM</DIV>
<DIV>To: Discussions about RabbitMQ</DIV>
<DIV>Cc: Elizabeth Liao</DIV>
<DIV>Subject: Re: [rabbitmq-discuss] nodename variable and mnesia directory</DIV>
<DIV> </DIV>
<DIV>Hi again,</DIV>
<DIV> </DIV>
<DIV>On 20 Oct 2012, at 10:52, Tim Watson wrote:</DIV>
<DIV> </DIV>
<DIV>> Hi Liz,</DIV>
<DIV>></DIV>
<DIV>> Sorry i wasn't aware of the context. What Ian recommended should not be necessary, though I'll follow up with him on Monday to try and figure out why he needed to do that.</DIV>
<DIV>></DIV>
<DIV>> Once you change the hostname you,ll possibly need to restart epmd and restart your rabbit, but you shouldn't need to change the node name from say rabbit to hare.</DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV>Were you able to try this again (changing only the host name but not the node name) and did it work for you? If not I'd like to know so we can investigate.</DIV>
<DIV> </DIV>
<DIV>Cheers</DIV>
<DIV>Tim</DIV>
<DIV> </DIV>
<DIV>> Cheers</DIV>
<DIV>> Tim</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> On 19 Oct 2012, at 19:44, Elizabeth Liao <eliao@seegrid.com> wrote:</DIV>
<DIV>></DIV>
<DIV>>> Hi Tim,</DIV>
<DIV>>></DIV>
<DIV>>> I'm going to back up a bit because it seems that I've misunderstood something previously.</DIV>
<DIV>>></DIV>
<DIV>>>> The first thing I'm going to say is that this isn't really a desirable</DIV>
<DIV>>> state of affairs. Why do you need to change NODENAME at all, just</DIV>
<DIV>>> because the host name has changed? This seems like an odd step to me -</DIV>
<DIV>>> can you explain the rationale behind it?</DIV>
<DIV>>></DIV>
<DIV>>> I had an earlier problem changing the hostname and restarting the rabbitmq-server. The proposed fix was to add the NODENAME variable which I'm guessing was not right? :</DIV>
<DIV>>> http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2012-July/021435.html</DIV>
<DIV>>></DIV>
<DIV>>>> Can you explain a bit more about this 'bug' please? What exactly is</DIV>
<DIV>>> going wrong?</DIV>
<DIV>>></DIV>
<DIV>>> The bug is on our end where the NODENAME is set to an empty string. Of course this is moot if NODENAME doesn't even have to be set in the first place.</DIV>
<DIV>>></DIV>
<DIV>>> Liz</DIV>
<DIV>>> ________________________________________</DIV>
<DIV>>> From: Tim Watson [tim@rabbitmq.com]</DIV>
<DIV>>> Sent: Friday, October 19, 2012 12:48 PM</DIV>
<DIV>>> To: Discussions about RabbitMQ</DIV>
<DIV>>> Cc: Elizabeth Liao</DIV>
<DIV>>> Subject: Re: [rabbitmq-discuss] nodename variable and mnesia directory</DIV>
<DIV>>></DIV>
<DIV>>> Hi</DIV>
<DIV>>></DIV>
<DIV>>> On 10/19/2012 03:41 PM, Elizabeth Liao wrote:</DIV>
<DIV>>>> Hi,</DIV>
<DIV>>>></DIV>
<DIV>>>> We are currently running rabbitmq on a system where there is a need to change the hostname occasionally. Right now, when the hostname is changed, we also update the NODENAME variable in the rabbitmq-env.conf file.</DIV>
<DIV>>></DIV>
<DIV>>> The first thing I'm going to say is that this isn't really a desirable</DIV>
<DIV>>> state of affairs. Why do you need to change NODENAME at all, just</DIV>
<DIV>>> because the host name has changed? This seems like an odd step to me -</DIV>
<DIV>>> can you explain the rationale behind it?</DIV>
<DIV>>></DIV>
<DIV>>>> The problem we're having right now is that due to a bug when setting up the rabbitmq-env.conf file, sometimes the NODENAME variable exists but is not set to anything ( NODENAME=) so rabbit never successfully starts up. Even after setting the NODENAME variable to the hostname, rabbit still doesn't start up properly.</DIV>
<DIV>>></DIV>
<DIV>>> Can you explain a bit more about this 'bug' please? What exactly is</DIV>
<DIV>>> going wrong?</DIV>
<DIV>>></DIV>
<DIV>>>> The only way that I could find to recover from this situation without killing the erlang process, was to also set a MNESIA_DIR variable. After I did that, once the NODENAME was set to the correct hostname, rabbit started up properly.</DIV>
<DIV>>></DIV>
<DIV>>> Now this makes no sense at all to me. If you are trying to recover</DIV>
<DIV>>> 'without killing the erlang process' then how are you planning on</DIV>
<DIV>>> changing the NODENAME? Once an erlang node has become part of a</DIV>
<DIV>>> distributed system, you cannot arbitrarily change the node's name</DIV>
<DIV>>> without restarting the net_kernel AFAIK so I can't see how this is even</DIV>
<DIV>>> possible. Also, because you're stating that 'rabbit started up properly'</DIV>
<DIV>>> I'm assuming that you have in fact taken the node offline (using</DIV>
<DIV>>> `rabbitmqctl stop` or one of the various service scripts that invokes</DIV>
<DIV>>> it) and that you are now starting the node again. The rabbit startup</DIV>
<DIV>>> scripts (and associated infrastructure) is not set up to handle changing</DIV>
<DIV>>> the name of a node post-installation in this manner, so I would not</DIV>
<DIV>>> expect this to work smoothly.</DIV>
<DIV>>></DIV>
<DIV>>>> A couple of questions:</DIV>
<DIV>>>> Is this the proper way to fix the situation?</DIV>
<DIV>>></DIV>
<DIV>>> No. As I said a moment ago, rabbit is not set up for this kind of</DIV>
<DIV>>> scenario so I'd be very cautious about doing this and would really</DIV>
<DIV>>> recommend against it.</DIV>
<DIV>>></DIV>
<DIV>>>> Will this have unintended consequences?</DIV>
<DIV>>></DIV>
<DIV>>> I have no idea, but it is entirely possible that various things could</DIV>
<DIV>>> break in obscure and alarming ways. I really would not do this if I were</DIV>
<DIV>>> you.</DIV>
<DIV>>></DIV>
<DIV>>>> We are running rabbitmq-server-2.8.6 and erlang-R15B.</DIV>
<DIV>>>></DIV>
<DIV>>>> Thanks!</DIV>
<DIV>>></DIV>
<DIV>>> Liz. I would like to help you find a safe work-around so that you can</DIV>
<DIV>>> use rabbit in your environment. I would really like to understand why</DIV>
<DIV>>> the changing of a machine's host-name is causing problems for you. I</DIV>
<DIV>>> fully realise that after changing the hostname, it is possible that a</DIV>
<DIV>>> restart may be required (although I'd have to do some research to verify</DIV>
<DIV>>> whether or not this is a hard requirement). But I cannot understand why</DIV>
<DIV>>> a change to the machine's host name requires changing the rabbit</DIV>
<DIV>>> NODENAME at all, unless you've altered the rabbit start scripts to use</DIV>
<DIV>>> 'longnames' configuration (i.e., including the complete host name in the</DIV>
<DIV>>> node name) in which case, a simple solution to your problem might be to</DIV>
<DIV>>> switch back to using 'shortnames'. If erlang is started using -sname</DIV>
<DIV>>> rabbit@`hostname -s` and your /etc/hosts configuration supports</DIV>
<DIV>>> resolving the machine's IP to the short version of the name, then</DIV>
<DIV>>> changing the hostname shouldn't cause all of these headaches.</DIV>
<DIV>>></DIV>
<DIV>>> For example, if I launch rabbit with something like this:</DIV>
<DIV>>></DIV>
<DIV>>> env RABBITMQ_NODENAME=rabbit RABBITMQ_NODE_PORT=5672</DIV>
<DIV>>> RABBITMQ_LOG_BASE="/tmp"</DIV>
<DIV>>> RABBITMQ_MNESIA_DIR="/tmp/rabbitmq-rabbit-mnesia"</DIV>
<DIV>>> RABBITMQ_PID_FILE="/tmp/rabbitmq-rabbit.pid"</DIV>
<DIV>>> RABBITMQ_PLUGINS_EXPAND_DIR="/tmp/rabbitmq-rabbit-plugins-scratch"</DIV>
<DIV>>> RABBITMQ_ENABLED_PLUGINS_FILE="/tmp/enabled-plugins"</DIV>
<DIV>>> RABBITMQ_CONFIG_FILE="/tmp/etc/rabbit" ./scripts/rabbitmq-server</DIV>
<DIV>>></DIV>
<DIV>>> Then change the hostname, then stop rabbit and start it again,</DIV>
<DIV>>> everything is fine.</DIV>
<DIV>>></DIV>
<DIV>>> Cheers,</DIV>
<DIV>>> Tim</DIV>
<DIV>>></DIV>
<DIV>>>> Liz</DIV>
<DIV>>>> Email Confidentiality Notice</DIV>
<DIV>>>></DIV>
<DIV>>>> The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. This message is intended for the sole use of the individual or entity to whom it's addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer.</DIV>
<DIV>>>> _______________________________________________</DIV>
<DIV>>>> rabbitmq-discuss mailing list</DIV>
<DIV>>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>>></DIV>
<DIV>>> Email Confidentiality Notice</DIV>
<DIV>>></DIV>
<DIV>>> The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. This message is intended for the sole use of the individual or entity to whom it's addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer.</DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV> </DIV>
<DIV>Email Confidentiality Notice</DIV>
<DIV> </DIV>
<DIV>The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. This message is intended for the sole use of the individual or entity to whom it's addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 23</DIV>
<DIV>Date: Mon, 22 Oct 2012 18:05:43 -0500</DIV>
<DIV>From: Travis <hcoyote@ghostar.org></DIV>
<DIV>Subject: [rabbitmq-discuss] Memory leak caused by error_logger in</DIV>
<DIV>2.8.6?</DIV>
<DIV>To: rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>Message-ID:</DIV>
<DIV><CAChq9g0hgKBX6LdhDxtva0OAfG+86TVrTcAWCksYs9WYUH1ofw@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset=ISO-8859-1</DIV>
<DIV> </DIV>
<DIV>Hello,</DIV>
<DIV> </DIV>
<DIV>We're seeing large amounts of memory being used in some of our single</DIV>
<DIV>instance 2.8.6 rabbitmq. When we do a memory</DIV>
<DIV>dump, the output appears to say that error_logger is taking up</DIV>
<DIV>hundreds of megabytes. For example:</DIV>
<DIV> </DIV>
<DIV>[{{memory,847631144},</DIV>
<DIV> <4865.6.0>,</DIV>
<DIV> [{registered_name,error_logger},</DIV>
<DIV> {current_function,{gen_event,fetch_msg,5}},</DIV>
<DIV> {initial_call,{proc_lib,init_p,5}},</DIV>
<DIV> {status,waiting},</DIV>
<DIV> {message_queue_len,0},</DIV>
<DIV> {messages,[]},</DIV>
<DIV> {links,[<4865.0.0>,<4865.30.0>]},</DIV>
<DIV> {dictionary,</DIV>
<DIV> [{{xtype_to_module,topic},rabbit_exchange_type_topic},</DIV>
<DIV> {'$ancestors',[<4865.2.0>]},</DIV>
<DIV> {'$initial_call',{gen_event,init_it,6}},</DIV>
<DIV> {guid,{{36630272,1263673450,3038695659,1008081001},3102285}}]},</DIV>
<DIV> {trap_exit,true},</DIV>
<DIV> {error_handler,error_handler},</DIV>
<DIV> {priority,normal},</DIV>
<DIV> {group_leader,<4865.30.0>},</DIV>
<DIV> {total_heap_size,105953765},</DIV>
<DIV> {heap_size,12538050},</DIV>
<DIV> {stack_size,8},</DIV>
<DIV> {reductions,3561515316},</DIV>
<DIV> {garbage_collection,</DIV>
<DIV> [{min_bin_vheap_size,46368},</DIV>
<DIV> {min_heap_size,233},</DIV>
<DIV> {fullsweep_after,65535},</DIV>
<DIV> {minor_gcs,578}]},</DIV>
<DIV> {suspending,[]}]},</DIV>
<DIV> </DIV>
<DIV>(If more of the dump is needed, I can provide)</DIV>
<DIV> </DIV>
<DIV> We're a bit perplexed as to what's causing this. There's nothing odd</DIV>
<DIV>looking in the logs. For example, we see stuff like this:</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:11 ===</DIV>
<DIV>accepting AMQP connection <0.1339.402> (127.0.0.1:32803 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=WARNING REPORT==== 22-Oct-2012::18:03:11 ===</DIV>
<DIV>closing AMQP connection <0.1339.402> (127.0.0.1:32803 -> 127.0.0.1:5672):</DIV>
<DIV>connection_closed_abruptly</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:12 ===</DIV>
<DIV>closing AMQP connection <0.1331.402> (127.0.0.1:32796 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:12 ===</DIV>
<DIV>accepting AMQP connection <0.1347.402> (127.0.0.1:32840 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=WARNING REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>closing AMQP connection <0.1347.402> (127.0.0.1:32840 -> 127.0.0.1:5672):</DIV>
<DIV>connection_closed_abruptly</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>closing AMQP connection <0.32496.401> (127.0.0.1:57108 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>closing AMQP connection <0.32476.401> (127.0.0.1:57104 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>closing AMQP connection <0.32492.401> (127.0.0.1:57107 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>closing AMQP connection <0.32468.401> (127.0.0.1:57103 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:14 ===</DIV>
<DIV>accepting AMQP connection <0.1355.402> (127.0.0.1:32875 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:14 ===</DIV>
<DIV>closing AMQP connection <0.1355.402> (127.0.0.1:32875 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>accepting AMQP connection <0.1363.402> (127.0.0.1:32898 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>accepting AMQP connection <0.1371.402> (127.0.0.1:32899 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>closing AMQP connection <0.1371.402> (127.0.0.1:32899 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>closing AMQP connection <0.32484.401> (127.0.0.1:57106 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>closing AMQP connection <0.32452.401> (127.0.0.1:57081 -> 127.0.0.1:5672)</DIV>
<DIV> </DIV>
<DIV>=WARNING REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>closing AMQP connection <0.1363.402> (127.0.0.1:32898 -> 127.0.0.1:5672):</DIV>
<DIV>connection_closed_abruptly</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Is there a way to tell what's really going on with the error_logger</DIV>
<DIV>and if we're really generating so many messages that it's causing</DIV>
<DIV>memory to balloon so much?</DIV>
<DIV> </DIV>
<DIV>Travis</DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Travis Campbell</DIV>
<DIV>travis@ghostar.org</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 24</DIV>
<DIV>Date: Mon, 22 Oct 2012 17:41:05 -0700 (PDT)</DIV>
<DIV>From: theBuckWheat <tbw@rg6.org></DIV>
<DIV>Subject: [rabbitmq-discuss] How to structure Master with many slaves?</DIV>
<DIV>RPC??</DIV>
<DIV>To: rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>Message-ID: <1350952865620-22782.post@n5.nabble.com></DIV>
<DIV>Content-Type: text/plain; charset=us-ascii</DIV>
<DIV> </DIV>
<DIV>I have a SETI-like slave pool, but I maintain the list of which slaves I want</DIV>
<DIV>to send work to and which are kept idle. The slave does the work assigned</DIV>
<DIV>and prepares the response dataset to be sent back.. </DIV>
<DIV> </DIV>
<DIV>Question: since I may turn on a slave to accept some work and later take</DIV>
<DIV>others out of the pool dynamically, what is the best RabbitMQ queue</DIV>
<DIV>topology? RPC? </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>--</DIV>
<DIV>View this message in context: http://rabbitmq.1065348.n5.nabble.com/How-to-structure-Master-with-many-slaves-RPC-tp22782.html</DIV>
<DIV>Sent from the RabbitMQ mailing list archive at Nabble.com.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 25</DIV>
<DIV>Date: Mon, 22 Oct 2012 21:08:54 -0400</DIV>
<DIV>From: Laurent Vauthrin <lvauthrin@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Channel thread-safety</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID:</DIV>
<DIV><CAM8Y7yCLUSV9ker3OWqENkKEFEWPoppos0k3jehWb3-8wqyPaA@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV> </DIV>
<DIV>Thanks for clearing that up!</DIV>
<DIV> </DIV>
<DIV>On Mon, Oct 22, 2012 at 3:46 PM, Michael Klishin <</DIV>
<DIV>michael.s.klishin@gmail.com> wrote:</DIV>
<DIV> </DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> 2012/10/22 Laurent Vauthrin <lvauthrin@gmail.com></DIV>
<DIV>></DIV>
<DIV>>> My questions are:</DIV>
<DIV>>> 1. Should we be using a channel per thread considering that we're</DIV>
<DIV>>> synchronizing the basicPublish call anyway?</DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>> Yes. Channels are just integer on the wire and a little bit of memory</DIV>
<DIV>> allocated on the JVM heap. They are very cheap</DIV>
<DIV>> for all intents and purposes and you are much more likely to max out your</DIV>
<DIV>> OS and hardware resources (assuming 1 channel per JVM thread) before</DIV>
<DIV>> you run into issues with channel objects.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>>> 2. Can we just share one channel across all threads and not synchronize</DIV>
<DIV>>> the call to basicPublish?</DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> No. The real issue with shared channels is that large messages will result</DIV>
<DIV>> in multiple protocol frames being sent</DIV>
<DIV>> for a single basicPublish operation. When publishing on the same channel</DIV>
<DIV>> from multiple threads, this may result</DIV>
<DIV>> in frames being delivered out of order:</DIV>
<DIV>></DIV>
<DIV>> T1 => basicPublish => [Frame11] [Frame12] [Frame13]</DIV>
<DIV>> T2 => basicPublish => [Frame21] [Frame22] [Frame23]</DIV>
<DIV>></DIV>
<DIV>> may result in the following delivery order, all on the same channel:</DIV>
<DIV>></DIV>
<DIV>> [Frame11][Frame21][Frame12][Frame13][Frame22][Frame23]</DIV>
<DIV>></DIV>
<DIV>> and because all frames are on the same channel, RabbitMQ won't be able to</DIV>
<DIV>> tell how to reconstruct your messages.</DIV>
<DIV>> --</DIV>
<DIV>> MK</DIV>
<DIV>></DIV>
<DIV>> http://github.com/michaelklishin</DIV>
<DIV>> http://twitter.com/michaelklishin</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121022/ddb12951/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 26</DIV>
<DIV>Date: Tue, 23 Oct 2012 09:12:01 +0100</DIV>
<DIV>From: Tim Watson <watson.timothy@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Clustering</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <140F445C-D95D-45F5-874C-F62DB4D695B3@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset="us-ascii"</DIV>
<DIV> </DIV>
<DIV>Please provide me with full details of your environments (os, version, etc) and can you please post a full transcript of all the commands and their output.</DIV>
<DIV> </DIV>
<DIV>Thanks</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>On 22 Oct 2012, at 20:28, chetan dev <dev440@gmail.com> wrote:</DIV>
<DIV> </DIV>
<DIV>> Hi,</DIV>
<DIV>> </DIV>
<DIV>> Yes i clustered them as given on rabbitmq clustering documentation for e.g</DIV>
<DIV>> on the first place both nodes are running </DIV>
<DIV>> now i stopped app using rabbitmqctl stop_app then i reset that node than i clusterd that node with another using rabbitmqctl cluster rabbit@SHIKHARM</DIV>
<DIV>> then i started the node using rabbitmqctl start_app</DIV>
<DIV>> when i checked the cluster status it was showing fine then i did as i mentioned earlier </DIV>
<DIV>> </DIV>
<DIV>> Thanks</DIV>
<DIV>> </DIV>
<DIV>> On Mon, Oct 22, 2012 at 7:51 PM, Tim Watson <watson.timothy@gmail.com> wrote:</DIV>
<DIV>> Yes but how did you cluster them on the first place? You do realise that rabbit nodes are not clustered automatically?</DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> On 22 Oct 2012, at 14:17, chetan dev <dev440@gmail.com> wrote:</DIV>
<DIV>> </DIV>
<DIV>>> Hi,</DIV>
<DIV>>> </DIV>
<DIV>>> Thanks for your reply i am using 2.8.6</DIV>
<DIV>>> here is what i am doing </DIV>
<DIV>>> 1. two nodes rabbit@SHIKHARM and rabbit@CHETANDEV are clustered </DIV>
<DIV>>> 2. now i stop node rabbit@SHIKHARM using rabbitmqctl stop commnad</DIV>
<DIV>>> 3. now i start the node rabbit@SHIKHARM using rabbitmq-server start commnad</DIV>
<DIV>>> 4. and then i check cluster status it shows only one running node </DIV>
<DIV>>> Cluster status of node rabbit@CHETANDEV ...</DIV>
<DIV>>> [{nodes,[{disc,[rabbit@SHIKHARM]},{ram,[rabbit@CHETANDEV]}]},</DIV>
<DIV>>> {running_nodes,[rabbit@CHETANDEV]}]</DIV>
<DIV>>> ...done.</DIV>
<DIV>>> </DIV>
<DIV>>> On Mon, Oct 22, 2012 at 6:39 PM, Tim Watson <tim@rabbitmq.com> wrote:</DIV>
<DIV>>> Works for me! ;)</DIV>
<DIV>>> </DIV>
<DIV>>> What version(s) of rabbit are you running and can you please post the exact commands you're using to start each node, to stop one of the applications (not the node) and cluster it with the other one and then finally the command you're using to start again.</DIV>
<DIV>>> </DIV>
<DIV>>> Cheers</DIV>
<DIV>>> Tim</DIV>
<DIV>>> </DIV>
<DIV>>> On 22 Oct 2012, at 14:04, chetan dev wrote:</DIV>
<DIV>>> </DIV>
<DIV>>> > Hi,</DIV>
<DIV>>> > I have two nodes clustered together , but when i stop a node using rabbbitmqctl stop command and start the broker with rabbitmq-server detached commnad</DIV>
<DIV>>> > now when i see the cluster status it shows only one broker running while both of the brokers are running fine.</DIV>
<DIV>>> > can anybody explain this or tell me what mistake i am making?</DIV>
<DIV>>> ></DIV>
<DIV>>> > Thanks</DIV>
<DIV>>> ></DIV>
<DIV>>> ></DIV>
<DIV>>> ></DIV>
<DIV>>> > --</DIV>
<DIV>>> > Cheten Dev</DIV>
<DIV>>> ></DIV>
<DIV>>> > B.Tech Final Year</DIV>
<DIV>>> > Dept. of Electrical Engg.</DIV>
<DIV>>> > IIT Delhi, New Delhi</DIV>
<DIV>>> > ph 8527333215</DIV>
<DIV>>> ></DIV>
<DIV>>> > _______________________________________________</DIV>
<DIV>>> > rabbitmq-discuss mailing list</DIV>
<DIV>>> > rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>>> </DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>>> </DIV>
<DIV>>> </DIV>
<DIV>>> </DIV>
<DIV>>> -- </DIV>
<DIV>>> Cheten Dev </DIV>
<DIV>>> </DIV>
<DIV>>> B.Tech Final Year</DIV>
<DIV>>> Dept. of Electrical Engg.</DIV>
<DIV>>> IIT Delhi, New Delhi</DIV>
<DIV>>> ph 8527333215</DIV>
<DIV>>> </DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>> </DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> -- </DIV>
<DIV>> Cheten Dev </DIV>
<DIV>> </DIV>
<DIV>> B.Tech Final Year</DIV>
<DIV>> Dept. of Electrical Engg.</DIV>
<DIV>> IIT Delhi, New Delhi</DIV>
<DIV>> ph 8527333215</DIV>
<DIV>> </DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121023/01aa6e11/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 27</DIV>
<DIV>Date: Tue, 23 Oct 2012 09:18:22 +0100</DIV>
<DIV>From: Tim Watson <watson.timothy@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] RabbitMQ + Messages between virtual</DIV>
<DIV>machines and physical hosts on a cloud</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: "rabbitmq-discuss@lists.rabbitmq.com"</DIV>
<DIV><rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <9ACEF152-DE73-41F6-8927-DCA43DC8C2E8@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset="us-ascii"</DIV>
<DIV> </DIV>
<DIV>Hi</DIV>
<DIV> </DIV>
<DIV>On 22 Oct 2012, at 20:50, Desta Haileselassie Hagos <deshai-0@student.ltu.se> wrote:</DIV>
<DIV> </DIV>
<DIV>> Dear Sir/Madam,</DIV>
<DIV>> </DIV>
<DIV>> The problem is that I am not able to send and receive messages between the Virtual machines and the physical hosts on my cloud. I want to receive full information by manipulating the VMs APIs if it is possible.</DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV> </DIV>
<DIV>Ok, let's try and address one problem at a time. Are you saying that you don't know *how* to configure messaging between hosts using rabbit? If so, I would recommend reading through the tutorials on our website in the first instance, then coming back with any questions you might have.</DIV>
<DIV> </DIV>
<DIV>Or are you saying that youve set up rabbit and/or deployed a messaging client application on these machines, but it is not working as expected? In that case: What are you doing to test sending messages between hosts (virtual or otherwise) - how are your rabbit nodes set up? What client(s) are you using? What version of rabbit? Which os/vsn? Can you post a transcript of the failing commands or application and/or server logs, demonstrating the errors you're encountering?</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>> </DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121023/5d29091c/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 28</DIV>
<DIV>Date: Tue, 23 Oct 2012 09:20:31 +0100</DIV>
<DIV>From: Tim Watson <watson.timothy@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Clustering</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <31488449-99C6-4430-807E-4657D7A9137A@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=us-ascii</DIV>
<DIV> </DIV>
<DIV>Ah of course - sorry i missed that guys. After so recently looking at the 3.0 cluster commands I'd forgotten that the choice of disk/ram was done that way in 2.8.x. </DIV>
<DIV> </DIV>
<DIV>On 22 Oct 2012, at 21:26, Matthias Radestock <matthias@rabbitmq.com> wrote:</DIV>
<DIV> </DIV>
<DIV>> On 22/10/12 20:28, chetan dev wrote:</DIV>
<DIV>>>> here is what i am doing</DIV>
<DIV>>>> 1. two nodes rabbit@SHIKHARM and rabbit@CHETANDEV are clustered</DIV>
<DIV>> </DIV>
<DIV>> yes, but...</DIV>
<DIV>> </DIV>
<DIV>>>> i clustered them as given on rabbitmq clustering documentation for e.g</DIV>
<DIV>>>> on the first place both nodes are running</DIV>
<DIV>>>> now i stopped app using rabbitmqctl stop_app then i reset that node than</DIV>
<DIV>>>> i clusterd that node with another using rabbitmqctl cluster rabbit@SHIKHARM</DIV>
<DIV>>>> then i started the node using rabbitmqctl start_app</DIV>
<DIV>>>> when i checked the cluster status it was showing fine then i did as i</DIV>
<DIV>>>> mentioned earlier</DIV>
<DIV>> </DIV>
<DIV>> That will make rabbit@CHETANDEV a *ram* node. To make both nodes disk nodes the node itself would have to be mentioned in the cluster command too, i.e. 'rabbitmqctl cluster rabbit@SHIKHAR rabbit@CHETANDEV'.</DIV>
<DIV>> </DIV>
<DIV>>>> 2. now i stop node rabbit@SHIKHARM using rabbitmqctl stop commnad</DIV>
<DIV>>>> 3. now i start the node rabbit@SHIKHARM using rabbitmq-server</DIV>
<DIV>>>> start commnad</DIV>
<DIV>> </DIV>
<DIV>> You have just stopped and restarted the clusters' only disk node. Rabbit clusters won't function properly if they have only ram nodes.</DIV>
<DIV>> </DIV>
<DIV>>>> 4. and then i check cluster status it shows only one running node</DIV>
<DIV>>>> Cluster status of node rabbit@CHETANDEV ...</DIV>
<DIV>>>> [{nodes,[{disc,[rabbit@SHIKHARM]},{ram,[rabbit@CHETANDEV]}]},</DIV>
<DIV>>>> {running_nodes,[rabbit@CHETANDEV]}]</DIV>
<DIV>>>> ...done.</DIV>
<DIV>> </DIV>
<DIV>> Try running that command against rabbit@SHIKHARM. I suspect it will tell you that it only knows about itself.</DIV>
<DIV>> </DIV>
<DIV>> Anyway, I suggest you change your cluster configuration s.t. both nodes are disk nodes.</DIV>
<DIV>> </DIV>
<DIV>> Regards,</DIV>
<DIV>> </DIV>
<DIV>> Matthias.</DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 29</DIV>
<DIV>Date: Tue, 23 Oct 2012 10:27:40 +0200</DIV>
<DIV>From: Michael Justin <michael.justin@gmx.net></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] STOMP plugin - durable subscription</DIV>
<DIV>limitation</DIV>
<DIV>To: rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>Message-ID: <k65kdv$jok$1@ger.gmane.org></DIV>
<DIV>Content-Type: text/plain; charset=UTF-8; format=flowed</DIV>
<DIV> </DIV>
<DIV>Am 22.10.2012 11:49, Emile Joubert wrote:> Hi Michael,</DIV>
<DIV> ></DIV>
<DIV> > On 21/10/12 09:32, Michael Justin wrote:</DIV>
<DIV> >> So I understand with the frames shown, the clients would use the same</DIV>
<DIV> >> shared queue.</DIV>
<DIV> >></DIV>
<DIV> >> Does this mean that all waiting messages in the topic will be</DIV>
<DIV> >> distributed between the two clients because of the identical</DIV>
<DIV> >> subscription ID x destination?</DIV>
<DIV> ></DIV>
<DIV> > Yes, this is correct. Both clients will be consuming from the same queue</DIV>
<DIV> > and messages will be distributed between them. You can use the prefetch</DIV>
<DIV> > header to control the distribution:</DIV>
<DIV> ></DIV>
<DIV> > http://www.rabbitmq.com/stomp.html#pear.p</DIV>
<DIV> </DIV>
<DIV>This is interesting - so the behavior of the broker is not undefined, </DIV>
<DIV>and clients could implement load balancing with durable subscribers if </DIV>
<DIV>they all use the same subscription ID (instead of using STOMP queues), </DIV>
<DIV>is this correct (just curious)?</DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Michael Justin</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 30</DIV>
<DIV>Date: Tue, 23 Oct 2012 09:33:26 +0100</DIV>
<DIV>From: Tim Watson <watson.timothy@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] nodename variable and mnesia directory</DIV>
<DIV>To: Elizabeth Liao <eliao@seegrid.com></DIV>
<DIV>Cc: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <1EDE5727-72BE-4384-A943-9F79DDB75819@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=us-ascii</DIV>
<DIV> </DIV>
<DIV>Hi</DIV>
<DIV> </DIV>
<DIV>On 22 Oct 2012, at 23:14, Elizabeth Liao <eliao@seegrid.com> wrote:</DIV>
<DIV> </DIV>
<DIV>> Hi,</DIV>
<DIV>> </DIV>
<DIV>> This is what I tried</DIV>
<DIV>> * I start running rabbit with no NODENAME set and entered the following commands</DIV>
<DIV>> * rabbitmqctl stop</DIV>
<DIV>> * /etc/init.d/rabbitmq-server stop</DIV>
<DIV>> * epmd -kill ( Is this correct? I didn't see a restart in the documentation )</DIV>
<DIV> </DIV>
<DIV>That is correct.</DIV>
<DIV> </DIV>
<DIV>> * In /etc/hosts changed line from 127.0.1.1 <oldhostname> <oldhostname>.localdomain -> 127.0.1.1 <newhostname> <newhostname>.localdomain</DIV>
<DIV>> * in /etc/sysconfig/network changed HOSTNAME=<oldhostname> -> HOSTNAME=<newhostname></DIV>
<DIV>> * /bin/hostname <newhostname></DIV>
<DIV> </DIV>
<DIV>At this point I found I needed to log out and back in again, though that was on centos an I'm not sure it's necessary to restart a profile on all operating systems. What os are you running an what does the documentation state about hostname changes? Do you, for example, have to restart the os networking sub system?</DIV>
<DIV> </DIV>
<DIV>> * /etc/init.d/rabbitmq-server start</DIV>
<DIV>> </DIV>
<DIV>> The error I get is this:</DIV>
<DIV>> Activating RabbitMQ plugins ...</DIV>
<DIV>> 3 plugins activated:</DIV>
<DIV>> * amqp_client-2.8.6</DIV>
<DIV>> * erlando-2.8.6</DIV>
<DIV>> * rabbitmq_shovel-2.8.6</DIV>
<DIV>> </DIV>
<DIV>> ERROR: epmd error for host "<oldhostname>": nxdomain (non-existing domain)</DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> ________________________________________</DIV>
<DIV>> From: Tim Watson [tim@rabbitmq.com]</DIV>
<DIV>> Sent: Monday, October 22, 2012 6:41 AM</DIV>
<DIV>> To: Discussions about RabbitMQ</DIV>
<DIV>> Cc: Elizabeth Liao</DIV>
<DIV>> Subject: Re: [rabbitmq-discuss] nodename variable and mnesia directory</DIV>
<DIV>> </DIV>
<DIV>> Hi again,</DIV>
<DIV>> </DIV>
<DIV>> On 20 Oct 2012, at 10:52, Tim Watson wrote:</DIV>
<DIV>> </DIV>
<DIV>>> Hi Liz,</DIV>
<DIV>>> </DIV>
<DIV>>> Sorry i wasn't aware of the context. What Ian recommended should not be necessary, though I'll follow up with him on Monday to try and figure out why he needed to do that.</DIV>
<DIV>>> </DIV>
<DIV>>> Once you change the hostname you,ll possibly need to restart epmd and restart your rabbit, but you shouldn't need to change the node name from say rabbit to hare.</DIV>
<DIV>>> </DIV>
<DIV>> </DIV>
<DIV>> Were you able to try this again (changing only the host name but not the node name) and did it work for you? If not I'd like to know so we can investigate.</DIV>
<DIV>> </DIV>
<DIV>> Cheers</DIV>
<DIV>> Tim</DIV>
<DIV>> </DIV>
<DIV>>> Cheers</DIV>
<DIV>>> Tim</DIV>
<DIV>>> </DIV>
<DIV>>> </DIV>
<DIV>>> </DIV>
<DIV>>> On 19 Oct 2012, at 19:44, Elizabeth Liao <eliao@seegrid.com> wrote:</DIV>
<DIV>>> </DIV>
<DIV>>>> Hi Tim,</DIV>
<DIV>>>> </DIV>
<DIV>>>> I'm going to back up a bit because it seems that I've misunderstood something previously.</DIV>
<DIV>>>> </DIV>
<DIV>>>>> The first thing I'm going to say is that this isn't really a desirable</DIV>
<DIV>>>> state of affairs. Why do you need to change NODENAME at all, just</DIV>
<DIV>>>> because the host name has changed? This seems like an odd step to me -</DIV>
<DIV>>>> can you explain the rationale behind it?</DIV>
<DIV>>>> </DIV>
<DIV>>>> I had an earlier problem changing the hostname and restarting the rabbitmq-server. The proposed fix was to add the NODENAME variable which I'm guessing was not right? :</DIV>
<DIV>>>> http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2012-July/021435.html</DIV>
<DIV>>>> </DIV>
<DIV>>>>> Can you explain a bit more about this 'bug' please? What exactly is</DIV>
<DIV>>>> going wrong?</DIV>
<DIV>>>> </DIV>
<DIV>>>> The bug is on our end where the NODENAME is set to an empty string. Of course this is moot if NODENAME doesn't even have to be set in the first place.</DIV>
<DIV>>>> </DIV>
<DIV>>>> Liz</DIV>
<DIV>>>> ________________________________________</DIV>
<DIV>>>> From: Tim Watson [tim@rabbitmq.com]</DIV>
<DIV>>>> Sent: Friday, October 19, 2012 12:48 PM</DIV>
<DIV>>>> To: Discussions about RabbitMQ</DIV>
<DIV>>>> Cc: Elizabeth Liao</DIV>
<DIV>>>> Subject: Re: [rabbitmq-discuss] nodename variable and mnesia directory</DIV>
<DIV>>>> </DIV>
<DIV>>>> Hi</DIV>
<DIV>>>> </DIV>
<DIV>>>> On 10/19/2012 03:41 PM, Elizabeth Liao wrote:</DIV>
<DIV>>>>> Hi,</DIV>
<DIV>>>>> </DIV>
<DIV>>>>> We are currently running rabbitmq on a system where there is a need to change the hostname occasionally. Right now, when the hostname is changed, we also update the NODENAME variable in the rabbitmq-env.conf file.</DIV>
<DIV>>>> </DIV>
<DIV>>>> The first thing I'm going to say is that this isn't really a desirable</DIV>
<DIV>>>> state of affairs. Why do you need to change NODENAME at all, just</DIV>
<DIV>>>> because the host name has changed? This seems like an odd step to me -</DIV>
<DIV>>>> can you explain the rationale behind it?</DIV>
<DIV>>>> </DIV>
<DIV>>>>> The problem we're having right now is that due to a bug when setting up the rabbitmq-env.conf file, sometimes the NODENAME variable exists but is not set to anything ( NODENAME=) so rabbit never successfully starts up. Even after setting the NODENAME variable to the hostname, rabbit still doesn't start up properly.</DIV>
<DIV>>>> </DIV>
<DIV>>>> Can you explain a bit more about this 'bug' please? What exactly is</DIV>
<DIV>>>> going wrong?</DIV>
<DIV>>>> </DIV>
<DIV>>>>> The only way that I could find to recover from this situation without killing the erlang process, was to also set a MNESIA_DIR variable. After I did that, once the NODENAME was set to the correct hostname, rabbit started up properly.</DIV>
<DIV>>>> </DIV>
<DIV>>>> Now this makes no sense at all to me. If you are trying to recover</DIV>
<DIV>>>> 'without killing the erlang process' then how are you planning on</DIV>
<DIV>>>> changing the NODENAME? Once an erlang node has become part of a</DIV>
<DIV>>>> distributed system, you cannot arbitrarily change the node's name</DIV>
<DIV>>>> without restarting the net_kernel AFAIK so I can't see how this is even</DIV>
<DIV>>>> possible. Also, because you're stating that 'rabbit started up properly'</DIV>
<DIV>>>> I'm assuming that you have in fact taken the node offline (using</DIV>
<DIV>>>> `rabbitmqctl stop` or one of the various service scripts that invokes</DIV>
<DIV>>>> it) and that you are now starting the node again. The rabbit startup</DIV>
<DIV>>>> scripts (and associated infrastructure) is not set up to handle changing</DIV>
<DIV>>>> the name of a node post-installation in this manner, so I would not</DIV>
<DIV>>>> expect this to work smoothly.</DIV>
<DIV>>>> </DIV>
<DIV>>>>> A couple of questions:</DIV>
<DIV>>>>> Is this the proper way to fix the situation?</DIV>
<DIV>>>> </DIV>
<DIV>>>> No. As I said a moment ago, rabbit is not set up for this kind of</DIV>
<DIV>>>> scenario so I'd be very cautious about doing this and would really</DIV>
<DIV>>>> recommend against it.</DIV>
<DIV>>>> </DIV>
<DIV>>>>> Will this have unintended consequences?</DIV>
<DIV>>>> </DIV>
<DIV>>>> I have no idea, but it is entirely possible that various things could</DIV>
<DIV>>>> break in obscure and alarming ways. I really would not do this if I were</DIV>
<DIV>>>> you.</DIV>
<DIV>>>> </DIV>
<DIV>>>>> We are running rabbitmq-server-2.8.6 and erlang-R15B.</DIV>
<DIV>>>>> </DIV>
<DIV>>>>> Thanks!</DIV>
<DIV>>>> </DIV>
<DIV>>>> Liz. I would like to help you find a safe work-around so that you can</DIV>
<DIV>>>> use rabbit in your environment. I would really like to understand why</DIV>
<DIV>>>> the changing of a machine's host-name is causing problems for you. I</DIV>
<DIV>>>> fully realise that after changing the hostname, it is possible that a</DIV>
<DIV>>>> restart may be required (although I'd have to do some research to verify</DIV>
<DIV>>>> whether or not this is a hard requirement). But I cannot understand why</DIV>
<DIV>>>> a change to the machine's host name requires changing the rabbit</DIV>
<DIV>>>> NODENAME at all, unless you've altered the rabbit start scripts to use</DIV>
<DIV>>>> 'longnames' configuration (i.e., including the complete host name in the</DIV>
<DIV>>>> node name) in which case, a simple solution to your problem might be to</DIV>
<DIV>>>> switch back to using 'shortnames'. If erlang is started using -sname</DIV>
<DIV>>>> rabbit@`hostname -s` and your /etc/hosts configuration supports</DIV>
<DIV>>>> resolving the machine's IP to the short version of the name, then</DIV>
<DIV>>>> changing the hostname shouldn't cause all of these headaches.</DIV>
<DIV>>>> </DIV>
<DIV>>>> For example, if I launch rabbit with something like this:</DIV>
<DIV>>>> </DIV>
<DIV>>>> env RABBITMQ_NODENAME=rabbit RABBITMQ_NODE_PORT=5672</DIV>
<DIV>>>> RABBITMQ_LOG_BASE="/tmp"</DIV>
<DIV>>>> RABBITMQ_MNESIA_DIR="/tmp/rabbitmq-rabbit-mnesia"</DIV>
<DIV>>>> RABBITMQ_PID_FILE="/tmp/rabbitmq-rabbit.pid"</DIV>
<DIV>>>> RABBITMQ_PLUGINS_EXPAND_DIR="/tmp/rabbitmq-rabbit-plugins-scratch"</DIV>
<DIV>>>> RABBITMQ_ENABLED_PLUGINS_FILE="/tmp/enabled-plugins"</DIV>
<DIV>>>> RABBITMQ_CONFIG_FILE="/tmp/etc/rabbit" ./scripts/rabbitmq-server</DIV>
<DIV>>>> </DIV>
<DIV>>>> Then change the hostname, then stop rabbit and start it again,</DIV>
<DIV>>>> everything is fine.</DIV>
<DIV>>>> </DIV>
<DIV>>>> Cheers,</DIV>
<DIV>>>> Tim</DIV>
<DIV>>>> </DIV>
<DIV>>>>> Liz</DIV>
<DIV>>>>> Email Confidentiality Notice</DIV>
<DIV>>>>> </DIV>
<DIV>>>>> The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. This message is intended for the sole use of the individual or entity to whom it's addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer.</DIV>
<DIV>>>>> _______________________________________________</DIV>
<DIV>>>>> rabbitmq-discuss mailing list</DIV>
<DIV>>>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>>>> </DIV>
<DIV>>>> Email Confidentiality Notice</DIV>
<DIV>>>> </DIV>
<DIV>>>> The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. This message is intended for the sole use of the individual or entity to whom it's addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer.</DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>> </DIV>
<DIV>> Email Confidentiality Notice</DIV>
<DIV>> </DIV>
<DIV>> The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. This message is intended for the sole use of the individual or entity to whom it's addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 31</DIV>
<DIV>Date: Tue, 23 Oct 2012 09:38:50 +0100</DIV>
<DIV>From: Tim Watson <watson.timothy@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Memory leak caused by error_logger in</DIV>
<DIV>2.8.6?</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: "rabbitmq-discuss@lists.rabbitmq.com"</DIV>
<DIV><rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <8A746A1E-A89E-420F-BA54-9D27B0E4AE5F@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=us-ascii</DIV>
<DIV> </DIV>
<DIV>How log does the situation last when this happens? Can you post the logs 'after' the memory goes up unexpectedly - is there any larger terms in there?</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>On 23 Oct 2012, at 00:05, Travis <hcoyote@ghostar.org> wrote:</DIV>
<DIV> </DIV>
<DIV>> Hello,</DIV>
<DIV>> </DIV>
<DIV>> We're seeing large amounts of memory being used in some of our single</DIV>
<DIV>> instance 2.8.6 rabbitmq. When we do a memory</DIV>
<DIV>> dump, the output appears to say that error_logger is taking up</DIV>
<DIV>> hundreds of megabytes. For example:</DIV>
<DIV>> </DIV>
<DIV>> [{{memory,847631144},</DIV>
<DIV>> <4865.6.0>,</DIV>
<DIV>> [{registered_name,error_logger},</DIV>
<DIV>> {current_function,{gen_event,fetch_msg,5}},</DIV>
<DIV>> {initial_call,{proc_lib,init_p,5}},</DIV>
<DIV>> {status,waiting},</DIV>
<DIV>> {message_queue_len,0},</DIV>
<DIV>> {messages,[]},</DIV>
<DIV>> {links,[<4865.0.0>,<4865.30.0>]},</DIV>
<DIV>> {dictionary,</DIV>
<DIV>> [{{xtype_to_module,topic},rabbit_exchange_type_topic},</DIV>
<DIV>> {'$ancestors',[<4865.2.0>]},</DIV>
<DIV>> {'$initial_call',{gen_event,init_it,6}},</DIV>
<DIV>> {guid,{{36630272,1263673450,3038695659,1008081001},3102285}}]},</DIV>
<DIV>> {trap_exit,true},</DIV>
<DIV>> {error_handler,error_handler},</DIV>
<DIV>> {priority,normal},</DIV>
<DIV>> {group_leader,<4865.30.0>},</DIV>
<DIV>> {total_heap_size,105953765},</DIV>
<DIV>> {heap_size,12538050},</DIV>
<DIV>> {stack_size,8},</DIV>
<DIV>> {reductions,3561515316},</DIV>
<DIV>> {garbage_collection,</DIV>
<DIV>> [{min_bin_vheap_size,46368},</DIV>
<DIV>> {min_heap_size,233},</DIV>
<DIV>> {fullsweep_after,65535},</DIV>
<DIV>> {minor_gcs,578}]},</DIV>
<DIV>> {suspending,[]}]},</DIV>
<DIV>> </DIV>
<DIV>> (If more of the dump is needed, I can provide)</DIV>
<DIV>> </DIV>
<DIV>> We're a bit perplexed as to what's causing this. There's nothing odd</DIV>
<DIV>> looking in the logs. For example, we see stuff like this:</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:11 ===</DIV>
<DIV>> accepting AMQP connection <0.1339.402> (127.0.0.1:32803 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =WARNING REPORT==== 22-Oct-2012::18:03:11 ===</DIV>
<DIV>> closing AMQP connection <0.1339.402> (127.0.0.1:32803 -> 127.0.0.1:5672):</DIV>
<DIV>> connection_closed_abruptly</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:12 ===</DIV>
<DIV>> closing AMQP connection <0.1331.402> (127.0.0.1:32796 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:12 ===</DIV>
<DIV>> accepting AMQP connection <0.1347.402> (127.0.0.1:32840 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =WARNING REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>> closing AMQP connection <0.1347.402> (127.0.0.1:32840 -> 127.0.0.1:5672):</DIV>
<DIV>> connection_closed_abruptly</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>> closing AMQP connection <0.32496.401> (127.0.0.1:57108 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>> closing AMQP connection <0.32476.401> (127.0.0.1:57104 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>> closing AMQP connection <0.32492.401> (127.0.0.1:57107 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>> closing AMQP connection <0.32468.401> (127.0.0.1:57103 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:14 ===</DIV>
<DIV>> accepting AMQP connection <0.1355.402> (127.0.0.1:32875 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:14 ===</DIV>
<DIV>> closing AMQP connection <0.1355.402> (127.0.0.1:32875 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>> accepting AMQP connection <0.1363.402> (127.0.0.1:32898 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>> accepting AMQP connection <0.1371.402> (127.0.0.1:32899 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>> closing AMQP connection <0.1371.402> (127.0.0.1:32899 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>> closing AMQP connection <0.32484.401> (127.0.0.1:57106 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>> closing AMQP connection <0.32452.401> (127.0.0.1:57081 -> 127.0.0.1:5672)</DIV>
<DIV>> </DIV>
<DIV>> =WARNING REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>> closing AMQP connection <0.1363.402> (127.0.0.1:32898 -> 127.0.0.1:5672):</DIV>
<DIV>> connection_closed_abruptly</DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> Is there a way to tell what's really going on with the error_logger</DIV>
<DIV>> and if we're really generating so many messages that it's causing</DIV>
<DIV>> memory to balloon so much?</DIV>
<DIV>> </DIV>
<DIV>> Travis</DIV>
<DIV>> </DIV>
<DIV>> -- </DIV>
<DIV>> Travis Campbell</DIV>
<DIV>> travis@ghostar.org</DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 32</DIV>
<DIV>Date: Tue, 23 Oct 2012 09:40:46 +0100</DIV>
<DIV>From: Tim Watson <watson.timothy@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] RabbitMQ + Messages between virtual</DIV>
<DIV>machines and physical hosts on a cloud</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <84B878DB-6611-4FD8-A1AB-BDE520F6385B@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset="us-ascii"</DIV>
<DIV> </DIV>
<DIV>And of course of you have set it up and it's not working, Brett's question (which I foolishly forgot to ask) is perhaps the most important one: is there any firewall between the nodes preventing traffic on the relevant ports from getting through?</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>On 23 Oct 2012, at 09:18, Tim Watson <watson.timothy@gmail.com> wrote:</DIV>
<DIV> </DIV>
<DIV>> Hi</DIV>
<DIV>> </DIV>
<DIV>> On 22 Oct 2012, at 20:50, Desta Haileselassie Hagos <deshai-0@student.ltu.se> wrote:</DIV>
<DIV>> </DIV>
<DIV>>> Dear Sir/Madam,</DIV>
<DIV>>> </DIV>
<DIV>>> The problem is that I am not able to send and receive messages between the Virtual machines and the physical hosts on my cloud. I want to receive full information by manipulating the VMs APIs if it is possible.</DIV>
<DIV>>> </DIV>
<DIV>>> </DIV>
<DIV>> </DIV>
<DIV>> Ok, let's try and address one problem at a time. Are you saying that you don't know *how* to configure messaging between hosts using rabbit? If so, I would recommend reading through the tutorials on our website in the first instance, then coming back with any questions you might have.</DIV>
<DIV>> </DIV>
<DIV>> Or are you saying that youve set up rabbit and/or deployed a messaging client application on these machines, but it is not working as expected? In that case: What are you doing to test sending messages between hosts (virtual or otherwise) - how are your rabbit nodes set up? What client(s) are you using? What version of rabbit? Which os/vsn? Can you post a transcript of the failing commands or application and/or server logs, demonstrating the errors you're encountering?</DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>>> </DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121023/bbaaf626/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 33</DIV>
<DIV>Date: Tue, 23 Oct 2012 09:42:36 +0100</DIV>
<DIV>From: Tim Watson <watson.timothy@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Memory leak caused by error_logger in</DIV>
<DIV>2.8.6?</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <FA9367DD-D418-4E1D-BB68-8E0B1E563CBC@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=us-ascii</DIV>
<DIV> </DIV>
<DIV>Hi - sorry typing on my phone isn't too reliable....</DIV>
<DIV> </DIV>
<DIV>s/how log/how long/</DIV>
<DIV> </DIV>
<DIV>On 23 Oct 2012, at 09:38, Tim Watson <watson.timothy@gmail.com> wrote:</DIV>
<DIV> </DIV>
<DIV>> How log does the situation last when this happens? Can you post the logs 'after' the memory goes up unexpectedly - is there any larger terms in there?</DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> On 23 Oct 2012, at 00:05, Travis <hcoyote@ghostar.org> wrote:</DIV>
<DIV>> </DIV>
<DIV>>> Hello,</DIV>
<DIV>>> </DIV>
<DIV>>> We're seeing large amounts of memory being used in some of our single</DIV>
<DIV>>> instance 2.8.6 rabbitmq. When we do a memory</DIV>
<DIV>>> dump, the output appears to say that error_logger is taking up</DIV>
<DIV>>> hundreds of megabytes. For example:</DIV>
<DIV>>> </DIV>
<DIV>>> [{{memory,847631144},</DIV>
<DIV>>> <4865.6.0>,</DIV>
<DIV>>> [{registered_name,error_logger},</DIV>
<DIV>>> {current_function,{gen_event,fetch_msg,5}},</DIV>
<DIV>>> {initial_call,{proc_lib,init_p,5}},</DIV>
<DIV>>> {status,waiting},</DIV>
<DIV>>> {message_queue_len,0},</DIV>
<DIV>>> {messages,[]},</DIV>
<DIV>>> {links,[<4865.0.0>,<4865.30.0>]},</DIV>
<DIV>>> {dictionary,</DIV>
<DIV>>> [{{xtype_to_module,topic},rabbit_exchange_type_topic},</DIV>
<DIV>>> {'$ancestors',[<4865.2.0>]},</DIV>
<DIV>>> {'$initial_call',{gen_event,init_it,6}},</DIV>
<DIV>>> {guid,{{36630272,1263673450,3038695659,1008081001},3102285}}]},</DIV>
<DIV>>> {trap_exit,true},</DIV>
<DIV>>> {error_handler,error_handler},</DIV>
<DIV>>> {priority,normal},</DIV>
<DIV>>> {group_leader,<4865.30.0>},</DIV>
<DIV>>> {total_heap_size,105953765},</DIV>
<DIV>>> {heap_size,12538050},</DIV>
<DIV>>> {stack_size,8},</DIV>
<DIV>>> {reductions,3561515316},</DIV>
<DIV>>> {garbage_collection,</DIV>
<DIV>>> [{min_bin_vheap_size,46368},</DIV>
<DIV>>> {min_heap_size,233},</DIV>
<DIV>>> {fullsweep_after,65535},</DIV>
<DIV>>> {minor_gcs,578}]},</DIV>
<DIV>>> {suspending,[]}]},</DIV>
<DIV>>> </DIV>
<DIV>>> (If more of the dump is needed, I can provide)</DIV>
<DIV>>> </DIV>
<DIV>>> We're a bit perplexed as to what's causing this. There's nothing odd</DIV>
<DIV>>> looking in the logs. For example, we see stuff like this:</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:11 ===</DIV>
<DIV>>> accepting AMQP connection <0.1339.402> (127.0.0.1:32803 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =WARNING REPORT==== 22-Oct-2012::18:03:11 ===</DIV>
<DIV>>> closing AMQP connection <0.1339.402> (127.0.0.1:32803 -> 127.0.0.1:5672):</DIV>
<DIV>>> connection_closed_abruptly</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:12 ===</DIV>
<DIV>>> closing AMQP connection <0.1331.402> (127.0.0.1:32796 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:12 ===</DIV>
<DIV>>> accepting AMQP connection <0.1347.402> (127.0.0.1:32840 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =WARNING REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>>> closing AMQP connection <0.1347.402> (127.0.0.1:32840 -> 127.0.0.1:5672):</DIV>
<DIV>>> connection_closed_abruptly</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>>> closing AMQP connection <0.32496.401> (127.0.0.1:57108 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>>> closing AMQP connection <0.32476.401> (127.0.0.1:57104 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>>> closing AMQP connection <0.32492.401> (127.0.0.1:57107 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:13 ===</DIV>
<DIV>>> closing AMQP connection <0.32468.401> (127.0.0.1:57103 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:14 ===</DIV>
<DIV>>> accepting AMQP connection <0.1355.402> (127.0.0.1:32875 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:14 ===</DIV>
<DIV>>> closing AMQP connection <0.1355.402> (127.0.0.1:32875 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>>> accepting AMQP connection <0.1363.402> (127.0.0.1:32898 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>>> accepting AMQP connection <0.1371.402> (127.0.0.1:32899 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>>> closing AMQP connection <0.1371.402> (127.0.0.1:32899 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>>> closing AMQP connection <0.32484.401> (127.0.0.1:57106 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =INFO REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>>> closing AMQP connection <0.32452.401> (127.0.0.1:57081 -> 127.0.0.1:5672)</DIV>
<DIV>>> </DIV>
<DIV>>> =WARNING REPORT==== 22-Oct-2012::18:03:15 ===</DIV>
<DIV>>> closing AMQP connection <0.1363.402> (127.0.0.1:32898 -> 127.0.0.1:5672):</DIV>
<DIV>>> connection_closed_abruptly</DIV>
<DIV>>> </DIV>
<DIV>>> </DIV>
<DIV>>> Is there a way to tell what's really going on with the error_logger</DIV>
<DIV>>> and if we're really generating so many messages that it's causing</DIV>
<DIV>>> memory to balloon so much?</DIV>
<DIV>>> </DIV>
<DIV>>> Travis</DIV>
<DIV>>> </DIV>
<DIV>>> -- </DIV>
<DIV>>> Travis Campbell</DIV>
<DIV>>> travis@ghostar.org</DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 34</DIV>
<DIV>Date: Tue, 23 Oct 2012 14:16:10 +0530</DIV>
<DIV>From: chetan dev <dev440@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Clustering</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID:</DIV>
<DIV><CAB0ZxM7WUWg2Z6RRupkfOcaSwabKpGki6AN1PTLhcX5DpxJa=w@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV> </DIV>
<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV>Thanks you very much for this information</DIV>
<DIV>another problem i am facing is i have two nodes clustered lets say</DIV>
<DIV>rabbit@SHIKHARM(ram) and rabbit@CHETANDEV(disc)</DIV>
<DIV>now if i stop rabbit@SHIKHARM using rabbitmwctl stop command and then i</DIV>
<DIV>stop rabbit@CHETANDEV using stop_app command and then reset it this way i</DIV>
<DIV>remove it from cluster and restart the node</DIV>
<DIV>now rabbit@CHETANDEV starts and works fine but when i try to start</DIV>
<DIV>rabbit@SHIKHARM it fails .</DIV>
<DIV>i think it is trying to cluster with rabbit@CHETANDEV but that node is now</DIV>
<DIV>not in cluster but is there a way so that i can reset rabbit@SHIKHARM and</DIV>
<DIV>start it normally</DIV>
<DIV>here is the error that i got:</DIV>
<DIV>node : rabbit@SHIKHARM</DIV>
<DIV>app descriptor : c:/Program Files/RabbitMQ</DIV>
<DIV>Server/rabbitmq_server-2.8.6/sbin/../</DIV>
<DIV>ebin/rabbit.app</DIV>
<DIV>home dir : C:\Users\Acer</DIV>
<DIV>config file(s) : (none)</DIV>
<DIV>cookie hash : +3xbT32/GKScN3yhCcE0Ag==</DIV>
<DIV>log :</DIV>
<DIV>C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM.log</DIV>
<DIV>sasl log :</DIV>
<DIV>C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM-sasl</DIV>
<DIV>.log</DIV>
<DIV>database dir :</DIV>
<DIV>c:/Users/Acer/AppData/Roaming/RabbitMQ/db/rabbit@SHIKHARM-mnesi</DIV>
<DIV>a</DIV>
<DIV>erlang version : 5.9.1</DIV>
<DIV> </DIV>
<DIV>-- rabbit boot start</DIV>
<DIV>starting file handle cache server</DIV>
<DIV>...done</DIV>
<DIV>starting worker pool</DIV>
<DIV> ...done</DIV>
<DIV>starting database ...</DIV>
<DIV> </DIV>
<DIV>BOOT FAILED</DIV>
<DIV>===========</DIV>
<DIV> </DIV>
<DIV>Error description:</DIV>
<DIV> {error,{failed_to_cluster_with,[rabbit@CHETANDEV],</DIV>
<DIV> "Mnesia could not connect to any disc</DIV>
<DIV>nodes."}</DIV>
<DIV>}</DIV>
<DIV> </DIV>
<DIV>Log files (may contain more information):</DIV>
<DIV> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM.log</DIV>
<DIV> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM-sasl.log</DIV>
<DIV> </DIV>
<DIV>Stack trace:</DIV>
<DIV> [{rabbit_mnesia,init_db,3,[]},</DIV>
<DIV> {rabbit_mnesia,init,0,[]},</DIV>
<DIV> {rabbit,'-run_boot_step/1-lc$^1/1-1-',1,[]},</DIV>
<DIV> {rabbit,run_boot_step,1,[]},</DIV>
<DIV> {rabbit,'-start/2-lc$^0/1-0-',1,[]},</DIV>
<DIV> {rabbit,start,2,[]},</DIV>
<DIV> {application_master,start_it_old,4,</DIV>
<DIV> [{file,"application_master.erl"},{line,274}]}]</DIV>
<DIV> </DIV>
<DIV>{"Kernel pid</DIV>
<DIV>terminated",application_controller,"{application_start_failure,rabb</DIV>
<DIV>it,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}</DIV>
<DIV>}}}"}</DIV>
<DIV> </DIV>
<DIV>Crash dump was written to: erl_crash.dump</DIV>
<DIV>Kernel pid terminated (application_controller)</DIV>
<DIV>({application_start_failure,rabbi</DIV>
<DIV>t,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}}</DIV>
<DIV>}})</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Thanks</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>On Tue, Oct 23, 2012 at 1:50 PM, Tim Watson <watson.timothy@gmail.com>wrote:</DIV>
<DIV> </DIV>
<DIV>> Ah of course - sorry i missed that guys. After so recently looking at the</DIV>
<DIV>> 3.0 cluster commands I'd forgotten that the choice of disk/ram was done</DIV>
<DIV>> that way in 2.8.x.</DIV>
<DIV>></DIV>
<DIV>> On 22 Oct 2012, at 21:26, Matthias Radestock <matthias@rabbitmq.com></DIV>
<DIV>> wrote:</DIV>
<DIV>></DIV>
<DIV>> > On 22/10/12 20:28, chetan dev wrote:</DIV>
<DIV>> >>> here is what i am doing</DIV>
<DIV>> >>> 1. two nodes rabbit@SHIKHARM and rabbit@CHETANDEV are clustered</DIV>
<DIV>> ></DIV>
<DIV>> > yes, but...</DIV>
<DIV>> ></DIV>
<DIV>> >>> i clustered them as given on rabbitmq clustering documentation for e.g</DIV>
<DIV>> >>> on the first place both nodes are running</DIV>
<DIV>> >>> now i stopped app using rabbitmqctl stop_app then i reset that node</DIV>
<DIV>> than</DIV>
<DIV>> >>> i clusterd that node with another using rabbitmqctl cluster</DIV>
<DIV>> rabbit@SHIKHARM</DIV>
<DIV>> >>> then i started the node using rabbitmqctl start_app</DIV>
<DIV>> >>> when i checked the cluster status it was showing fine then i did as i</DIV>
<DIV>> >>> mentioned earlier</DIV>
<DIV>> ></DIV>
<DIV>> > That will make rabbit@CHETANDEV a *ram* node. To make both nodes disk</DIV>
<DIV>> nodes the node itself would have to be mentioned in the cluster command</DIV>
<DIV>> too, i.e. 'rabbitmqctl cluster rabbit@SHIKHAR rabbit@CHETANDEV'.</DIV>
<DIV>> ></DIV>
<DIV>> >>> 2. now i stop node rabbit@SHIKHARM using rabbitmqctl stop commnad</DIV>
<DIV>> >>> 3. now i start the node rabbit@SHIKHARM using rabbitmq-server</DIV>
<DIV>> >>> start commnad</DIV>
<DIV>> ></DIV>
<DIV>> > You have just stopped and restarted the clusters' only disk node. Rabbit</DIV>
<DIV>> clusters won't function properly if they have only ram nodes.</DIV>
<DIV>> ></DIV>
<DIV>> >>> 4. and then i check cluster status it shows only one running node</DIV>
<DIV>> >>> Cluster status of node rabbit@CHETANDEV ...</DIV>
<DIV>> >>> [{nodes,[{disc,[rabbit@SHIKHARM]},{ram,[rabbit@CHETANDEV]}]},</DIV>
<DIV>> >>> {running_nodes,[rabbit@CHETANDEV]}]</DIV>
<DIV>> >>> ...done.</DIV>
<DIV>> ></DIV>
<DIV>> > Try running that command against rabbit@SHIKHARM. I suspect it will</DIV>
<DIV>> tell you that it only knows about itself.</DIV>
<DIV>> ></DIV>
<DIV>> > Anyway, I suggest you change your cluster configuration s.t. both nodes</DIV>
<DIV>> are disk nodes.</DIV>
<DIV>> ></DIV>
<DIV>> > Regards,</DIV>
<DIV>> ></DIV>
<DIV>> > Matthias.</DIV>
<DIV>> > _______________________________________________</DIV>
<DIV>> > rabbitmq-discuss mailing list</DIV>
<DIV>> > rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Cheten Dev</DIV>
<DIV> </DIV>
<DIV>B.Tech Final Year</DIV>
<DIV>Dept. of Electrical Engg.</DIV>
<DIV>IIT Delhi, New Delhi</DIV>
<DIV>ph 8527333215</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121023/1830ac65/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 35</DIV>
<DIV>Date: Tue, 23 Oct 2012 10:48:17 +0200</DIV>
<DIV>From: Michael Justin <michael.justin@gmx.net></DIV>
<DIV>Subject: [rabbitmq-discuss] STOMP 1.0 adapter escapes colon as \c</DIV>
<DIV>(STOMP 1.1 style)</DIV>
<DIV>To: rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>Message-ID: <k65lkj$uhe$1@ger.gmane.org></DIV>
<DIV>Content-Type: text/plain; charset=UTF-8; format=flowed</DIV>
<DIV> </DIV>
<DIV>Hello,</DIV>
<DIV> </DIV>
<DIV>a test showed that a colon in a SEND frame will be escaped STOMP </DIV>
<DIV>1.1-style as \c, so this</DIV>
<DIV> </DIV>
<DIV>SEND</DIV>
<DIV>destination:/queue/ExampleQueue</DIV>
<DIV>testcolon1:a:test</DIV>
<DIV> </DIV>
<DIV>will be received as:</DIV>
<DIV> </DIV>
<DIV>MESSAGE</DIV>
<DIV>destination:/queue/ExampleQueue</DIV>
<DIV>testcolon1:a\ctest</DIV>
<DIV> </DIV>
<DIV>Is this as designed? The STOMP plugin page does not cover this escape </DIV>
<DIV>mechanism, which was introduced with STOMP 1.1</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>I also noticed that messages with header line which contains a backslash </DIV>
<DIV>seem to be dropped on the broker side:</DIV>
<DIV> </DIV>
<DIV>SEND</DIV>
<DIV>destination:/queue/ExampleQueue</DIV>
<DIV>testbackslash:\x</DIV>
<DIV> </DIV>
<DIV>-> the message does not appear in the Management console</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Regards</DIV>
<DIV>-- </DIV>
<DIV>Michael Justin</DIV>
<DIV>habarisoft - Enterprise Messaging Software for Delphi</DIV>
<DIV>http://www.habarisoft.com/</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 36</DIV>
<DIV>Date: Tue, 23 Oct 2012 10:13:53 +0100</DIV>
<DIV>From: Emile Joubert <emile@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] How to structure Master with many</DIV>
<DIV>slaves? RPC??</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: theBuckWheat <tbw@rg6.org></DIV>
<DIV>Message-ID: <50865FD1.7040305@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=ISO-8859-1</DIV>
<DIV> </DIV>
<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV>On 23/10/12 01:41, theBuckWheat wrote:</DIV>
<DIV>> I have a SETI-like slave pool, but I maintain the list of which slaves I want</DIV>
<DIV>> to send work to and which are kept idle. The slave does the work assigned</DIV>
<DIV>> and prepares the response dataset to be sent back.. </DIV>
<DIV>> </DIV>
<DIV>> Question: since I may turn on a slave to accept some work and later take</DIV>
<DIV>> others out of the pool dynamically, what is the best RabbitMQ queue</DIV>
<DIV>> topology? RPC?</DIV>
<DIV> </DIV>
<DIV>If the slaves are interchangeable and you don't care about separating</DIV>
<DIV>different types of work items then you only need one work queue and one</DIV>
<DIV>response queue. Slaves all consume from the same shared work queue and</DIV>
<DIV>send completed work to the shared response queue in this scenario. This</DIV>
<DIV>corresponds to the pattern in tutorial 2 and 6:</DIV>
<DIV>http://www.rabbitmq.com/tutorials/tutorial-two-python.html</DIV>
<DIV>http://www.rabbitmq.com/tutorials/tutorial-six-python.html</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-Emile</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 37</DIV>
<DIV>Date: Tue, 23 Oct 2012 10:08:28 +0100</DIV>
<DIV>From: Tim Watson <tim@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Clustering</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <50865E8C.3070906@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"</DIV>
<DIV> </DIV>
<DIV>Don't do that - take the second node out of the cluster whilst the other </DIV>
<DIV>node(s) are still running, so that they can see it leaving. See the </DIV>
<DIV>clustering transcripts in http://www.rabbitmq.com/clustering.html for </DIV>
<DIV>details.</DIV>
<DIV> </DIV>
<DIV>On 10/23/2012 09:46 AM, chetan dev wrote:</DIV>
<DIV>> Hi,</DIV>
<DIV>></DIV>
<DIV>> Thanks you very much for this information</DIV>
<DIV>> another problem i am facing is i have two nodes clustered lets say </DIV>
<DIV>> rabbit@SHIKHARM(ram) and rabbit@CHETANDEV(disc)</DIV>
<DIV>> now if i stop rabbit@SHIKHARM using rabbitmwctl stop command and then </DIV>
<DIV>> i stop rabbit@CHETANDEV using stop_app command and then reset it </DIV>
<DIV>> this way i remove it from cluster and restart the node</DIV>
<DIV>> now rabbit@CHETANDEV starts and works fine but when i try to start </DIV>
<DIV>> rabbit@SHIKHARM it fails .</DIV>
<DIV>> i think it is trying to cluster with rabbit@CHETANDEV but that node is </DIV>
<DIV>> now not in cluster but is there a way so that i can reset </DIV>
<DIV>> rabbit@SHIKHARM and start it normally</DIV>
<DIV>> here is the error that i got:</DIV>
<DIV>> node : rabbit@SHIKHARM</DIV>
<DIV>> app descriptor : c:/Program Files/RabbitMQ </DIV>
<DIV>> Server/rabbitmq_server-2.8.6/sbin/../</DIV>
<DIV>> ebin/rabbit.app</DIV>
<DIV>> home dir : C:\Users\Acer</DIV>
<DIV>> config file(s) : (none)</DIV>
<DIV>> cookie hash : +3xbT32/GKScN3yhCcE0Ag==</DIV>
<DIV>> log : </DIV>
<DIV>> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM.log</DIV>
<DIV>> sasl log : </DIV>
<DIV>> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM-sasl</DIV>
<DIV>> .log</DIV>
<DIV>> database dir : </DIV>
<DIV>> c:/Users/Acer/AppData/Roaming/RabbitMQ/db/rabbit@SHIKHARM-mnesi</DIV>
<DIV>> a</DIV>
<DIV>> erlang version : 5.9.1</DIV>
<DIV>></DIV>
<DIV>> -- rabbit boot start</DIV>
<DIV>> starting file handle cache server </DIV>
<DIV>> ...done</DIV>
<DIV>> starting worker pool </DIV>
<DIV>> ...done</DIV>
<DIV>> starting database ...</DIV>
<DIV>></DIV>
<DIV>> BOOT FAILED</DIV>
<DIV>> ===========</DIV>
<DIV>></DIV>
<DIV>> Error description:</DIV>
<DIV>> {error,{failed_to_cluster_with,[rabbit@CHETANDEV],</DIV>
<DIV>> "Mnesia could not connect to any </DIV>
<DIV>> disc nodes."}</DIV>
<DIV>> }</DIV>
<DIV>></DIV>
<DIV>> Log files (may contain more information):</DIV>
<DIV>> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM.log</DIV>
<DIV>> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM-sasl.log</DIV>
<DIV>></DIV>
<DIV>> Stack trace:</DIV>
<DIV>> [{rabbit_mnesia,init_db,3,[]},</DIV>
<DIV>> {rabbit_mnesia,init,0,[]},</DIV>
<DIV>> {rabbit,'-run_boot_step/1-lc$^1/1-1-',1,[]},</DIV>
<DIV>> {rabbit,run_boot_step,1,[]},</DIV>
<DIV>> {rabbit,'-start/2-lc$^0/1-0-',1,[]},</DIV>
<DIV>> {rabbit,start,2,[]},</DIV>
<DIV>> {application_master,start_it_old,4,</DIV>
<DIV>> [{file,"application_master.erl"},{line,274}]}]</DIV>
<DIV>></DIV>
<DIV>> {"Kernel pid </DIV>
<DIV>> terminated",application_controller,"{application_start_failure,rabb</DIV>
<DIV>> it,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}</DIV>
<DIV>> }}}"}</DIV>
<DIV>></DIV>
<DIV>> Crash dump was written to: erl_crash.dump</DIV>
<DIV>> Kernel pid terminated (application_controller) </DIV>
<DIV>> ({application_start_failure,rabbi</DIV>
<DIV>> t,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}}</DIV>
<DIV>> }})</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> Thanks</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> On Tue, Oct 23, 2012 at 1:50 PM, Tim Watson <watson.timothy@gmail.com </DIV>
<DIV>> <mailto:watson.timothy@gmail.com>> wrote:</DIV>
<DIV>></DIV>
<DIV>> Ah of course - sorry i missed that guys. After so recently looking</DIV>
<DIV>> at the 3.0 cluster commands I'd forgotten that the choice of</DIV>
<DIV>> disk/ram was done that way in 2.8.x.</DIV>
<DIV>></DIV>
<DIV>> On 22 Oct 2012, at 21:26, Matthias Radestock</DIV>
<DIV>> <matthias@rabbitmq.com <mailto:matthias@rabbitmq.com>> wrote:</DIV>
<DIV>></DIV>
<DIV>> > On 22/10/12 20:28, chetan dev wrote:</DIV>
<DIV>> >>> here is what i am doing</DIV>
<DIV>> >>> 1. two nodes rabbit@SHIKHARM and rabbit@CHETANDEV are clustered</DIV>
<DIV>> ></DIV>
<DIV>> > yes, but...</DIV>
<DIV>> ></DIV>
<DIV>> >>> i clustered them as given on rabbitmq clustering documentation</DIV>
<DIV>> for e.g</DIV>
<DIV>> >>> on the first place both nodes are running</DIV>
<DIV>> >>> now i stopped app using rabbitmqctl stop_app then i reset that</DIV>
<DIV>> node than</DIV>
<DIV>> >>> i clusterd that node with another using rabbitmqctl cluster</DIV>
<DIV>> rabbit@SHIKHARM</DIV>
<DIV>> >>> then i started the node using rabbitmqctl start_app</DIV>
<DIV>> >>> when i checked the cluster status it was showing fine then i</DIV>
<DIV>> did as i</DIV>
<DIV>> >>> mentioned earlier</DIV>
<DIV>> ></DIV>
<DIV>> > That will make rabbit@CHETANDEV a *ram* node. To make both nodes</DIV>
<DIV>> disk nodes the node itself would have to be mentioned in the</DIV>
<DIV>> cluster command too, i.e. 'rabbitmqctl cluster rabbit@SHIKHAR</DIV>
<DIV>> rabbit@CHETANDEV'.</DIV>
<DIV>> ></DIV>
<DIV>> >>> 2. now i stop node rabbit@SHIKHARM using rabbitmqctl stop</DIV>
<DIV>> commnad</DIV>
<DIV>> >>> 3. now i start the node rabbit@SHIKHARM using rabbitmq-server</DIV>
<DIV>> >>> start commnad</DIV>
<DIV>> ></DIV>
<DIV>> > You have just stopped and restarted the clusters' only disk</DIV>
<DIV>> node. Rabbit clusters won't function properly if they have only</DIV>
<DIV>> ram nodes.</DIV>
<DIV>> ></DIV>
<DIV>> >>> 4. and then i check cluster status it shows only one</DIV>
<DIV>> running node</DIV>
<DIV>> >>> Cluster status of node rabbit@CHETANDEV ...</DIV>
<DIV>> >>> [{nodes,[{disc,[rabbit@SHIKHARM]},{ram,[rabbit@CHETANDEV]}]},</DIV>
<DIV>> >>> {running_nodes,[rabbit@CHETANDEV]}]</DIV>
<DIV>> >>> ...done.</DIV>
<DIV>> ></DIV>
<DIV>> > Try running that command against rabbit@SHIKHARM. I suspect it</DIV>
<DIV>> will tell you that it only knows about itself.</DIV>
<DIV>> ></DIV>
<DIV>> > Anyway, I suggest you change your cluster configuration s.t.</DIV>
<DIV>> both nodes are disk nodes.</DIV>
<DIV>> ></DIV>
<DIV>> > Regards,</DIV>
<DIV>> ></DIV>
<DIV>> > Matthias.</DIV>
<DIV>> > _______________________________________________</DIV>
<DIV>> > rabbitmq-discuss mailing list</DIV>
<DIV>> > rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> <mailto:rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> <mailto:rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> -- </DIV>
<DIV>> Cheten Dev</DIV>
<DIV>></DIV>
<DIV>> B.Tech Final Year</DIV>
<DIV>> Dept. of Electrical Engg.</DIV>
<DIV>> IIT Delhi, New Delhi</DIV>
<DIV>> ph 8527333215</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV> </DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121023/7ad3d6e3/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 38</DIV>
<DIV>Date: Tue, 23 Oct 2012 10:18:52 +0100</DIV>
<DIV>From: Simon MacMullen <simon@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Memory leak caused by error_logger in</DIV>
<DIV>2.8.6?</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <508660FC.8020706@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=ISO-8859-1; format=flowed</DIV>
<DIV> </DIV>
<DIV>On 23/10/12 00:05, Travis wrote:</DIV>
<DIV>> {total_heap_size,105953765},</DIV>
<DIV>> {heap_size,12538050},</DIV>
<DIV> </DIV>
<DIV>> Is there a way to tell what's really going on with the error_logger</DIV>
<DIV>> and if we're really generating so many messages that it's causing</DIV>
<DIV>> memory to balloon so much?</DIV>
<DIV> </DIV>
<DIV>Hmm.</DIV>
<DIV> </DIV>
<DIV>Looks like it is progressing too slowly towards GC; what happens if you </DIV>
<DIV>GC it manually?</DIV>
<DIV> </DIV>
<DIV>We are considering adding some background process that will GC the </DIV>
<DIV>biggest process every so often, since it seems to be possible to end up </DIV>
<DIV>with processes that consume a lot of memory but haven't chalked up </DIV>
<DIV>enough reductions to get GCed.</DIV>
<DIV> </DIV>
<DIV>Cheers, Simon</DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Simon MacMullen</DIV>
<DIV>RabbitMQ, VMware</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 39</DIV>
<DIV>Date: Tue, 23 Oct 2012 14:51:15 +0530</DIV>
<DIV>From: chetan dev <dev440@gmail.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Clustering</DIV>
<DIV>To: Tim Watson <tim@rabbitmq.com></DIV>
<DIV>Cc: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID:</DIV>
<DIV><CAB0ZxM5xb-dPXybW4wq0V+6cG1y2MEznbzue-1gCFHFy5ZTU_w@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV> </DIV>
<DIV>Yes , but now the node is failing to start because it is not able to find</DIV>
<DIV>other node for clustering</DIV>
<DIV>so how do i reset this node to run it normally?</DIV>
<DIV> </DIV>
<DIV>Thanks</DIV>
<DIV> </DIV>
<DIV>On Tue, Oct 23, 2012 at 2:38 PM, Tim Watson <tim@rabbitmq.com> wrote:</DIV>
<DIV> </DIV>
<DIV>> Don't do that - take the second node out of the cluster whilst the other</DIV>
<DIV>> node(s) are still running, so that they can see it leaving. See the</DIV>
<DIV>> clustering transcripts in http://www.rabbitmq.com/clustering.html for</DIV>
<DIV>> details.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> On 10/23/2012 09:46 AM, chetan dev wrote:</DIV>
<DIV>></DIV>
<DIV>> Hi,</DIV>
<DIV>></DIV>
<DIV>> Thanks you very much for this information</DIV>
<DIV>> another problem i am facing is i have two nodes clustered lets say</DIV>
<DIV>> rabbit@SHIKHARM(ram) and rabbit@CHETANDEV(disc)</DIV>
<DIV>> now if i stop rabbit@SHIKHARM using rabbitmwctl stop command and then i</DIV>
<DIV>> stop rabbit@CHETANDEV using stop_app command and then reset it this way</DIV>
<DIV>> i remove it from cluster and restart the node</DIV>
<DIV>> now rabbit@CHETANDEV starts and works fine but when i try to start</DIV>
<DIV>> rabbit@SHIKHARM it fails .</DIV>
<DIV>> i think it is trying to cluster with rabbit@CHETANDEV but that node is</DIV>
<DIV>> now not in cluster but is there a way so that i can reset rabbit@SHIKHARMand start it normally</DIV>
<DIV>> here is the error that i got:</DIV>
<DIV>> node : rabbit@SHIKHARM</DIV>
<DIV>> app descriptor : c:/Program Files/RabbitMQ</DIV>
<DIV>> Server/rabbitmq_server-2.8.6/sbin/../</DIV>
<DIV>> ebin/rabbit.app</DIV>
<DIV>> home dir : C:\Users\Acer</DIV>
<DIV>> config file(s) : (none)</DIV>
<DIV>> cookie hash : +3xbT32/GKScN3yhCcE0Ag==</DIV>
<DIV>> log :</DIV>
<DIV>> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM.log</DIV>
<DIV>> sasl log :</DIV>
<DIV>> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM-sasl</DIV>
<DIV>> .log</DIV>
<DIV>> database dir :</DIV>
<DIV>> c:/Users/Acer/AppData/Roaming/RabbitMQ/db/rabbit@SHIKHARM-mnesi</DIV>
<DIV>> a</DIV>
<DIV>> erlang version : 5.9.1</DIV>
<DIV>></DIV>
<DIV>> -- rabbit boot start</DIV>
<DIV>> starting file handle cache server</DIV>
<DIV>> ...done</DIV>
<DIV>> starting worker pool</DIV>
<DIV>> ...done</DIV>
<DIV>> starting database ...</DIV>
<DIV>></DIV>
<DIV>> BOOT FAILED</DIV>
<DIV>> ===========</DIV>
<DIV>></DIV>
<DIV>> Error description:</DIV>
<DIV>> {error,{failed_to_cluster_with,[rabbit@CHETANDEV],</DIV>
<DIV>> "Mnesia could not connect to any disc</DIV>
<DIV>> nodes."}</DIV>
<DIV>> }</DIV>
<DIV>></DIV>
<DIV>> Log files (may contain more information):</DIV>
<DIV>> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM.log</DIV>
<DIV>> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM-sasl.log</DIV>
<DIV>></DIV>
<DIV>> Stack trace:</DIV>
<DIV>> [{rabbit_mnesia,init_db,3,[]},</DIV>
<DIV>> {rabbit_mnesia,init,0,[]},</DIV>
<DIV>> {rabbit,'-run_boot_step/1-lc$^1/1-1-',1,[]},</DIV>
<DIV>> {rabbit,run_boot_step,1,[]},</DIV>
<DIV>> {rabbit,'-start/2-lc$^0/1-0-',1,[]},</DIV>
<DIV>> {rabbit,start,2,[]},</DIV>
<DIV>> {application_master,start_it_old,4,</DIV>
<DIV>> [{file,"application_master.erl"},{line,274}]}]</DIV>
<DIV>></DIV>
<DIV>> {"Kernel pid</DIV>
<DIV>> terminated",application_controller,"{application_start_failure,rabb</DIV>
<DIV>></DIV>
<DIV>> it,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}</DIV>
<DIV>> }}}"}</DIV>
<DIV>></DIV>
<DIV>> Crash dump was written to: erl_crash.dump</DIV>
<DIV>> Kernel pid terminated (application_controller)</DIV>
<DIV>> ({application_start_failure,rabbi</DIV>
<DIV>></DIV>
<DIV>> t,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}}</DIV>
<DIV>> }})</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> Thanks</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> On Tue, Oct 23, 2012 at 1:50 PM, Tim Watson <watson.timothy@gmail.com>wrote:</DIV>
<DIV>></DIV>
<DIV>>> Ah of course - sorry i missed that guys. After so recently looking at the</DIV>
<DIV>>> 3.0 cluster commands I'd forgotten that the choice of disk/ram was done</DIV>
<DIV>>> that way in 2.8.x.</DIV>
<DIV>>></DIV>
<DIV>>> On 22 Oct 2012, at 21:26, Matthias Radestock <matthias@rabbitmq.com></DIV>
<DIV>>> wrote:</DIV>
<DIV>>></DIV>
<DIV>>> > On 22/10/12 20:28, chetan dev wrote:</DIV>
<DIV>>> >>> here is what i am doing</DIV>
<DIV>>> >>> 1. two nodes rabbit@SHIKHARM and rabbit@CHETANDEV are clustered</DIV>
<DIV>>> ></DIV>
<DIV>>> > yes, but...</DIV>
<DIV>>> ></DIV>
<DIV>>> >>> i clustered them as given on rabbitmq clustering documentation for e.g</DIV>
<DIV>>> >>> on the first place both nodes are running</DIV>
<DIV>>> >>> now i stopped app using rabbitmqctl stop_app then i reset that node</DIV>
<DIV>>> than</DIV>
<DIV>>> >>> i clusterd that node with another using rabbitmqctl cluster</DIV>
<DIV>>> rabbit@SHIKHARM</DIV>
<DIV>>> >>> then i started the node using rabbitmqctl start_app</DIV>
<DIV>>> >>> when i checked the cluster status it was showing fine then i did as i</DIV>
<DIV>>> >>> mentioned earlier</DIV>
<DIV>>> ></DIV>
<DIV>>> > That will make rabbit@CHETANDEV a *ram* node. To make both nodes disk</DIV>
<DIV>>> nodes the node itself would have to be mentioned in the cluster command</DIV>
<DIV>>> too, i.e. 'rabbitmqctl cluster rabbit@SHIKHAR rabbit@CHETANDEV'.</DIV>
<DIV>>> ></DIV>
<DIV>>> >>> 2. now i stop node rabbit@SHIKHARM using rabbitmqctl stop commnad</DIV>
<DIV>>> >>> 3. now i start the node rabbit@SHIKHARM using rabbitmq-server</DIV>
<DIV>>> >>> start commnad</DIV>
<DIV>>> ></DIV>
<DIV>>> > You have just stopped and restarted the clusters' only disk node.</DIV>
<DIV>>> Rabbit clusters won't function properly if they have only ram nodes.</DIV>
<DIV>>> ></DIV>
<DIV>>> >>> 4. and then i check cluster status it shows only one running node</DIV>
<DIV>>> >>> Cluster status of node rabbit@CHETANDEV ...</DIV>
<DIV>>> >>> [{nodes,[{disc,[rabbit@SHIKHARM]},{ram,[rabbit@CHETANDEV]}]},</DIV>
<DIV>>> >>> {running_nodes,[rabbit@CHETANDEV]}]</DIV>
<DIV>>> >>> ...done.</DIV>
<DIV>>> ></DIV>
<DIV>>> > Try running that command against rabbit@SHIKHARM. I suspect it will</DIV>
<DIV>>> tell you that it only knows about itself.</DIV>
<DIV>>> ></DIV>
<DIV>>> > Anyway, I suggest you change your cluster configuration s.t. both nodes</DIV>
<DIV>>> are disk nodes.</DIV>
<DIV>>> ></DIV>
<DIV>>> > Regards,</DIV>
<DIV>>> ></DIV>
<DIV>>> > Matthias.</DIV>
<DIV>>> > _______________________________________________</DIV>
<DIV>>> > rabbitmq-discuss mailing list</DIV>
<DIV>>> > rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> --</DIV>
<DIV>> Cheten Dev</DIV>
<DIV>></DIV>
<DIV>> B.Tech Final Year</DIV>
<DIV>> Dept. of Electrical Engg.</DIV>
<DIV>> IIT Delhi, New Delhi</DIV>
<DIV>> ph 8527333215</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing listrabbitmq-discuss@lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Cheten Dev</DIV>
<DIV> </DIV>
<DIV>B.Tech Final Year</DIV>
<DIV>Dept. of Electrical Engg.</DIV>
<DIV>IIT Delhi, New Delhi</DIV>
<DIV>ph 8527333215</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121023/51afb9ec/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 40</DIV>
<DIV>Date: Tue, 23 Oct 2012 10:28:58 +0100</DIV>
<DIV>From: Simon MacMullen <simon@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Upgrading RabbitMQ2.8.6</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: Matt Long <matt@crocodoc.com></DIV>
<DIV>Message-ID: <5086635A.3000407@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=ISO-8859-1; format=flowed</DIV>
<DIV> </DIV>
<DIV>Somewhat on purpose - due to the vagaries of our build system, we treat </DIV>
<DIV>the apt repository as just another build artefact, so it gets created </DIV>
<DIV>from scratch each time. I know this is not ideal.</DIV>
<DIV> </DIV>
<DIV>If you want to pin to a particular version you will need to download the </DIV>
<DIV>deb directly.</DIV>
<DIV> </DIV>
<DIV>Cheers, Simon</DIV>
<DIV> </DIV>
<DIV>On 22/10/12 17:07, Matt Long wrote:</DIV>
<DIV>> While we're on the topic of older versions, it appears they are removed</DIV>
<DIV>> from the RabbitMQ APT repository; only the newest version is ever</DIV>
<DIV>> available. Is this done on purpose? It has led to some issues for us</DIV>
<DIV>> since we specify explicit package versions in our provisioning system</DIV>
<DIV>> and occasionally they'll no longer be there!</DIV>
<DIV>></DIV>
<DIV>> Thanks,</DIV>
<DIV>> Matt</DIV>
<DIV>></DIV>
<DIV>> On Mon, Oct 22, 2012 at 4:21 AM, Matthias Radestock</DIV>
<DIV>> <matthias@rabbitmq.com <mailto:matthias@rabbitmq.com>> wrote:</DIV>
<DIV>></DIV>
<DIV>> On 19/10/12 10:24, PSL 88506 wrote:</DIV>
<DIV>></DIV>
<DIV>> When i try to understand about installation procedure for 2.8.6</DIV>
<DIV>></DIV>
<DIV>> All links are getting redirected to same page with following URL:</DIV>
<DIV>> http://www.rabbitmq.com/__download.html</DIV>
<DIV>> <http://www.rabbitmq.com/download.html></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> Links will always point to the latest version, which is 2.8.7. I</DIV>
<DIV>> recommend you install that rather than 2.8.6. If you really must</DIV>
<DIV>> install 2.8.6, follow the "Older Versions / Download" link on the</DIV>
<DIV>> download.html page.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> Regards,</DIV>
<DIV>></DIV>
<DIV>> Matthias.</DIV>
<DIV>> _________________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.__rabbitmq.com</DIV>
<DIV>> <mailto:rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>> https://lists.rabbitmq.com/__cgi-bin/mailman/listinfo/__rabbitmq-discuss</DIV>
<DIV>> <https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> --</DIV>
<DIV>> Matt Long</DIV>
<DIV>> Cofounder and Lead Developer</DIV>
<DIV>> crocodoc.com <http://crocodoc.com/></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Simon MacMullen</DIV>
<DIV>RabbitMQ, VMware</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 41</DIV>
<DIV>Date: Tue, 23 Oct 2012 10:31:32 +0100</DIV>
<DIV>From: Tim Watson <tim@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Clustering</DIV>
<DIV>To: chetan dev <dev440@gmail.com></DIV>
<DIV>Cc: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <508663F4.3040507@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"</DIV>
<DIV> </DIV>
<DIV>Post me the *exact* commands you're using on each node, in sequence </DIV>
<DIV>please. If you follow the 'Breaking up a cluster' transcript from </DIV>
<DIV>http://www.rabbitmq.com/clustering.html then you should not have *any* </DIV>
<DIV>problems. In particular, note the use of 'force_reset' on the surviving </DIV>
<DIV>node, so that it does not attempt to connect to nodes that are no longer </DIV>
<DIV>part of the cluster - who's residual configuration is still present on </DIV>
<DIV>the extant node we're now resetting.</DIV>
<DIV> </DIV>
<DIV>On 10/23/2012 10:21 AM, chetan dev wrote:</DIV>
<DIV>> Yes , but now the node is failing to start because it is not able to </DIV>
<DIV>> find other node for clustering</DIV>
<DIV>> so how do i reset this node to run it normally?</DIV>
<DIV>></DIV>
<DIV>> Thanks</DIV>
<DIV>></DIV>
<DIV>> On Tue, Oct 23, 2012 at 2:38 PM, Tim Watson <tim@rabbitmq.com </DIV>
<DIV>> <mailto:tim@rabbitmq.com>> wrote:</DIV>
<DIV>></DIV>
<DIV>> Don't do that - take the second node out of the cluster whilst the</DIV>
<DIV>> other node(s) are still running, so that they can see it leaving.</DIV>
<DIV>> See the clustering transcripts in</DIV>
<DIV>> http://www.rabbitmq.com/clustering.html for details.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> On 10/23/2012 09:46 AM, chetan dev wrote:</DIV>
<DIV>>> Hi,</DIV>
<DIV>>></DIV>
<DIV>>> Thanks you very much for this information</DIV>
<DIV>>> another problem i am facing is i have two nodes clustered lets</DIV>
<DIV>>> say rabbit@SHIKHARM(ram) and rabbit@CHETANDEV(disc)</DIV>
<DIV>>> now if i stop rabbit@SHIKHARM using rabbitmwctl stop command and</DIV>
<DIV>>> then i stop rabbit@CHETANDEV using stop_app command and then</DIV>
<DIV>>> reset it this way i remove it from cluster and restart the node</DIV>
<DIV>>> now rabbit@CHETANDEV starts and works fine but when i try to</DIV>
<DIV>>> start rabbit@SHIKHARM it fails .</DIV>
<DIV>>> i think it is trying to cluster with rabbit@CHETANDEV but that</DIV>
<DIV>>> node is now not in cluster but is there a way so that i can reset</DIV>
<DIV>>> rabbit@SHIKHARM and start it normally</DIV>
<DIV>>> here is the error that i got:</DIV>
<DIV>>> node : rabbit@SHIKHARM</DIV>
<DIV>>> app descriptor : c:/Program Files/RabbitMQ</DIV>
<DIV>>> Server/rabbitmq_server-2.8.6/sbin/../</DIV>
<DIV>>> ebin/rabbit.app</DIV>
<DIV>>> home dir : C:\Users\Acer</DIV>
<DIV>>> config file(s) : (none)</DIV>
<DIV>>> cookie hash : +3xbT32/GKScN3yhCcE0Ag==</DIV>
<DIV>>> log :</DIV>
<DIV>>> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM.log</DIV>
<DIV>>> <mailto:C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM.log></DIV>
<DIV>>> sasl log :</DIV>
<DIV>>> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM-sasl</DIV>
<DIV>>> .log</DIV>
<DIV>>> database dir :</DIV>
<DIV>>> c:/Users/Acer/AppData/Roaming/RabbitMQ/db/rabbit@SHIKHARM-mnesi</DIV>
<DIV>>> a</DIV>
<DIV>>> erlang version : 5.9.1</DIV>
<DIV>>></DIV>
<DIV>>> -- rabbit boot start</DIV>
<DIV>>> starting file handle cache server </DIV>
<DIV>>> ...done</DIV>
<DIV>>> starting worker pool </DIV>
<DIV>>> ...done</DIV>
<DIV>>> starting database </DIV>
<DIV>>> ...</DIV>
<DIV>>></DIV>
<DIV>>> BOOT FAILED</DIV>
<DIV>>> ===========</DIV>
<DIV>>></DIV>
<DIV>>> Error description:</DIV>
<DIV>>> {error,{failed_to_cluster_with,[rabbit@CHETANDEV],</DIV>
<DIV>>> "Mnesia could not connect to</DIV>
<DIV>>> any disc nodes."}</DIV>
<DIV>>> }</DIV>
<DIV>>></DIV>
<DIV>>> Log files (may contain more information):</DIV>
<DIV>>> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM.log</DIV>
<DIV>>> <mailto:C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM.log></DIV>
<DIV>>> C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM-sasl.log</DIV>
<DIV>>> <mailto:C:/Users/Acer/AppData/Roaming/RabbitMQ/log/rabbit@SHIKHARM-sasl.log></DIV>
<DIV>>></DIV>
<DIV>>> Stack trace:</DIV>
<DIV>>> [{rabbit_mnesia,init_db,3,[]},</DIV>
<DIV>>> {rabbit_mnesia,init,0,[]},</DIV>
<DIV>>> {rabbit,'-run_boot_step/1-lc$^1/1-1-',1,[]},</DIV>
<DIV>>> {rabbit,run_boot_step,1,[]},</DIV>
<DIV>>> {rabbit,'-start/2-lc$^0/1-0-',1,[]},</DIV>
<DIV>>> {rabbit,start,2,[]},</DIV>
<DIV>>> {application_master,start_it_old,4,</DIV>
<DIV>>> </DIV>
<DIV>>> [{file,"application_master.erl"},{line,274}]}]</DIV>
<DIV>>></DIV>
<DIV>>> {"Kernel pid</DIV>
<DIV>>> terminated",application_controller,"{application_start_failure,rabb</DIV>
<DIV>>> it,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}</DIV>
<DIV>>> }}}"}</DIV>
<DIV>>></DIV>
<DIV>>> Crash dump was written to: erl_crash.dump</DIV>
<DIV>>> Kernel pid terminated (application_controller)</DIV>
<DIV>>> ({application_start_failure,rabbi</DIV>
<DIV>>> t,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}}</DIV>
<DIV>>> }})</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> Thanks</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> On Tue, Oct 23, 2012 at 1:50 PM, Tim Watson</DIV>
<DIV>>> <watson.timothy@gmail.com <mailto:watson.timothy@gmail.com>> wrote:</DIV>
<DIV>>></DIV>
<DIV>>> Ah of course - sorry i missed that guys. After so recently</DIV>
<DIV>>> looking at the 3.0 cluster commands I'd forgotten that the</DIV>
<DIV>>> choice of disk/ram was done that way in 2.8.x.</DIV>
<DIV>>></DIV>
<DIV>>> On 22 Oct 2012, at 21:26, Matthias Radestock</DIV>
<DIV>>> <matthias@rabbitmq.com <mailto:matthias@rabbitmq.com>> wrote:</DIV>
<DIV>>></DIV>
<DIV>>> > On 22/10/12 20:28, chetan dev wrote:</DIV>
<DIV>>> >>> here is what i am doing</DIV>
<DIV>>> >>> 1. two nodes rabbit@SHIKHARM and rabbit@CHETANDEV are</DIV>
<DIV>>> clustered</DIV>
<DIV>>> ></DIV>
<DIV>>> > yes, but...</DIV>
<DIV>>> ></DIV>
<DIV>>> >>> i clustered them as given on rabbitmq clustering</DIV>
<DIV>>> documentation for e.g</DIV>
<DIV>>> >>> on the first place both nodes are running</DIV>
<DIV>>> >>> now i stopped app using rabbitmqctl stop_app then i reset</DIV>
<DIV>>> that node than</DIV>
<DIV>>> >>> i clusterd that node with another using rabbitmqctl</DIV>
<DIV>>> cluster rabbit@SHIKHARM</DIV>
<DIV>>> >>> then i started the node using rabbitmqctl start_app</DIV>
<DIV>>> >>> when i checked the cluster status it was showing fine</DIV>
<DIV>>> then i did as i</DIV>
<DIV>>> >>> mentioned earlier</DIV>
<DIV>>> ></DIV>
<DIV>>> > That will make rabbit@CHETANDEV a *ram* node. To make both</DIV>
<DIV>>> nodes disk nodes the node itself would have to be mentioned</DIV>
<DIV>>> in the cluster command too, i.e. 'rabbitmqctl cluster</DIV>
<DIV>>> rabbit@SHIKHAR rabbit@CHETANDEV'.</DIV>
<DIV>>> ></DIV>
<DIV>>> >>> 2. now i stop node rabbit@SHIKHARM using rabbitmqctl</DIV>
<DIV>>> stop commnad</DIV>
<DIV>>> >>> 3. now i start the node rabbit@SHIKHARM using</DIV>
<DIV>>> rabbitmq-server</DIV>
<DIV>>> >>> start commnad</DIV>
<DIV>>> ></DIV>
<DIV>>> > You have just stopped and restarted the clusters' only disk</DIV>
<DIV>>> node. Rabbit clusters won't function properly if they have</DIV>
<DIV>>> only ram nodes.</DIV>
<DIV>>> ></DIV>
<DIV>>> >>> 4. and then i check cluster status it shows only one</DIV>
<DIV>>> running node</DIV>
<DIV>>> >>> Cluster status of node rabbit@CHETANDEV ...</DIV>
<DIV>>> >>> </DIV>
<DIV>>> [{nodes,[{disc,[rabbit@SHIKHARM]},{ram,[rabbit@CHETANDEV]}]},</DIV>
<DIV>>> >>> {running_nodes,[rabbit@CHETANDEV]}]</DIV>
<DIV>>> >>> ...done.</DIV>
<DIV>>> ></DIV>
<DIV>>> > Try running that command against rabbit@SHIKHARM. I suspect</DIV>
<DIV>>> it will tell you that it only knows about itself.</DIV>
<DIV>>> ></DIV>
<DIV>>> > Anyway, I suggest you change your cluster configuration</DIV>
<DIV>>> s.t. both nodes are disk nodes.</DIV>
<DIV>>> ></DIV>
<DIV>>> > Regards,</DIV>
<DIV>>> ></DIV>
<DIV>>> > Matthias.</DIV>
<DIV>>> > _______________________________________________</DIV>
<DIV>>> > rabbitmq-discuss mailing list</DIV>
<DIV>>> > rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> <mailto:rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>>> ></DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> <mailto:rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> -- </DIV>
<DIV>>> Cheten Dev</DIV>
<DIV>>></DIV>
<DIV>>> B.Tech Final Year</DIV>
<DIV>>> Dept. of Electrical Engg.</DIV>
<DIV>>> IIT Delhi, New Delhi</DIV>
<DIV>>> ph 8527333215</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com <mailto:rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> -- </DIV>
<DIV>> Cheten Dev</DIV>
<DIV>></DIV>
<DIV>> B.Tech Final Year</DIV>
<DIV>> Dept. of Electrical Engg.</DIV>
<DIV>> IIT Delhi, New Delhi</DIV>
<DIV>> ph 8527333215</DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121023/27fa243d/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 42</DIV>
<DIV>Date: Tue, 23 Oct 2012 11:05:50 +0100</DIV>
<DIV>From: Emile Joubert <emile@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] STOMP 1.0 adapter escapes colon as \c</DIV>
<DIV>(STOMP 1.1 style)</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: Michael Justin <michael.justin@gmx.net></DIV>
<DIV>Message-ID: <50866BFE.9060605@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=ISO-8859-1</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Hi Michael,</DIV>
<DIV> </DIV>
<DIV>On 23/10/12 09:48, Michael Justin wrote:</DIV>
<DIV>> Hello,</DIV>
<DIV>> </DIV>
<DIV>> a test showed that a colon in a SEND frame will be escaped STOMP </DIV>
<DIV>> 1.1-style as \c, so this</DIV>
<DIV>> </DIV>
<DIV>> SEND</DIV>
<DIV>> destination:/queue/ExampleQueue</DIV>
<DIV>> testcolon1:a:test</DIV>
<DIV>> </DIV>
<DIV>> will be received as:</DIV>
<DIV>> </DIV>
<DIV>> MESSAGE</DIV>
<DIV>> destination:/queue/ExampleQueue</DIV>
<DIV>> testcolon1:a\ctest</DIV>
<DIV>> </DIV>
<DIV>> Is this as designed? The STOMP plugin page does not cover this escape </DIV>
<DIV>> mechanism, which was introduced with STOMP 1.1</DIV>
<DIV> </DIV>
<DIV>The only difference in framing between 1.0 and 1.1 in the RabbitMQ STOMP</DIV>
<DIV>implementation at present is trimming. If the negotiated version is 1.0</DIV>
<DIV>then headers are trimmed. Only 1.1 frame parsing is implemented, under</DIV>
<DIV>the assumption that this is backwards-compatible.</DIV>
<DIV> </DIV>
<DIV>Are you relying on the STOMP 1.0 behaviour w.r.t colons in header values?</DIV>
<DIV> </DIV>
<DIV>> I also noticed that messages with header line which contains a backslash </DIV>
<DIV>> seem to be dropped on the broker side:</DIV>
<DIV>> </DIV>
<DIV>> SEND</DIV>
<DIV>> destination:/queue/ExampleQueue</DIV>
<DIV>> testbackslash:\x</DIV>
<DIV>> </DIV>
<DIV>> -> the message does not appear in the Management console</DIV>
<DIV> </DIV>
<DIV>This is compatible with 1.1, which says that undefined escape sequences</DIV>
<DIV>must be treated as a fatal protocol error.</DIV>
<DIV> </DIV>
<DIV>We'd be interested in your opinion of how important strict STOMP 1.0</DIV>
<DIV>framing support is to help us decide whether to invest in that effort or</DIV>
<DIV>focus on 1.2 instead.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-Emile</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 43</DIV>
<DIV>Date: Tue, 23 Oct 2012 11:18:11 +0100</DIV>
<DIV>From: Emile Joubert <emile@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] STOMP plugin - durable subscription</DIV>
<DIV>limitation</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Cc: Michael Justin <michael.justin@gmx.net></DIV>
<DIV>Message-ID: <50866EE3.4000409@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset=ISO-8859-1</DIV>
<DIV> </DIV>
<DIV>On 23/10/12 09:27, Michael Justin wrote:</DIV>
<DIV>> This is interesting - so the behavior of the broker is not undefined, </DIV>
<DIV>> and clients could implement load balancing with durable subscribers if </DIV>
<DIV>> they all use the same subscription ID (instead of using STOMP queues), </DIV>
<DIV>> is this correct (just curious)?</DIV>
<DIV> </DIV>
<DIV>Yes, I don't see anything preventing it being used in that way.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-Emile</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 44</DIV>
<DIV>Date: Tue, 23 Oct 2012 11:29:57 +0100</DIV>
<DIV>From: Tim Watson <tim@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Channel thread-safety</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <508671A5.6050007@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"</DIV>
<DIV> </DIV>
<DIV>Actually, that's not quite right. Channels *are* thread safe in the </DIV>
<DIV>java-client, and can be shared across multiple threads if you wish. As </DIV>
<DIV>the Java client API documentation </DIV>
<DIV>(http://www.rabbitmq.com/api-guide.html) states however:</DIV>
<DIV> </DIV>
<DIV>"Channel instances are safe for use by multiple threads. Requests into a </DIV>
<DIV>Channel are serialized, with only one thread being able to run a command </DIV>
<DIV>on the Channel at a time. Even so, applications should prefer using a </DIV>
<DIV>Channel per thread instead of sharing the same Channel across multiple </DIV>
<DIV>threads."</DIV>
<DIV> </DIV>
<DIV>In other words, because the transmission of AMQP commands via a given </DIV>
<DIV>Channel is serialised, there is probably little or no benefit in sharing </DIV>
<DIV>the channel between threads.</DIV>
<DIV> </DIV>
<DIV>Unfortunately, whilst we've updated the documentation on the website to </DIV>
<DIV>reflect this change (which was merged in September 2011 and released in </DIV>
<DIV>2.7.0) we appear to have missed the javadocs for the Channel class - I </DIV>
<DIV>will get that fixed asap so as to avoid any further confusion!</DIV>
<DIV> </DIV>
<DIV>Cheers,</DIV>
<DIV>Tim</DIV>
<DIV> </DIV>
<DIV>On 10/23/2012 02:08 AM, Laurent Vauthrin wrote:</DIV>
<DIV>> Thanks for clearing that up!</DIV>
<DIV>></DIV>
<DIV>> On Mon, Oct 22, 2012 at 3:46 PM, Michael Klishin </DIV>
<DIV>> <michael.s.klishin@gmail.com <mailto:michael.s.klishin@gmail.com>> wrote:</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> 2012/10/22 Laurent Vauthrin <lvauthrin@gmail.com</DIV>
<DIV>> <mailto:lvauthrin@gmail.com>></DIV>
<DIV>></DIV>
<DIV>> My questions are:</DIV>
<DIV>> 1. Should we be using a channel per thread considering that</DIV>
<DIV>> we're synchronizing the basicPublish call anyway?</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> Yes. Channels are just integer on the wire and a little bit of</DIV>
<DIV>> memory allocated on the JVM heap. They are very cheap</DIV>
<DIV>> for all intents and purposes and you are much more likely to max</DIV>
<DIV>> out your OS and hardware resources (assuming 1 channel per JVM</DIV>
<DIV>> thread) before</DIV>
<DIV>> you run into issues with channel objects.</DIV>
<DIV>></DIV>
<DIV>> 2. Can we just share one channel across all threads and not</DIV>
<DIV>> synchronize the call to basicPublish?</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> No. The real issue with shared channels is that large messages</DIV>
<DIV>> will result in multiple protocol frames being sent</DIV>
<DIV>> for a single basicPublish operation. When publishing on the same</DIV>
<DIV>> channel from multiple threads, this may result</DIV>
<DIV>> in frames being delivered out of order:</DIV>
<DIV>></DIV>
<DIV>> T1 => basicPublish => [Frame11] [Frame12] [Frame13]</DIV>
<DIV>> T2 => basicPublish => [Frame21] [Frame22] [Frame23]</DIV>
<DIV>></DIV>
<DIV>> may result in the following delivery order, all on the same channel:</DIV>
<DIV>></DIV>
<DIV>> [Frame11][Frame21][Frame12][Frame13][Frame22][Frame23]</DIV>
<DIV>></DIV>
<DIV>> and because all frames are on the same channel, RabbitMQ won't be</DIV>
<DIV>> able to tell how to reconstruct your messages.</DIV>
<DIV>> -- </DIV>
<DIV>> MK</DIV>
<DIV>></DIV>
<DIV>> http://github.com/michaelklishin</DIV>
<DIV>> http://twitter.com/michaelklishin</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> <mailto:rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV> </DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121023/5eefd15e/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>Message: 45</DIV>
<DIV>Date: Tue, 23 Oct 2012 11:42:58 +0100</DIV>
<DIV>From: Tim Watson <tim@rabbitmq.com></DIV>
<DIV>Subject: Re: [rabbitmq-discuss] Channel thread-safety</DIV>
<DIV>To: Discussions about RabbitMQ <rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>Message-ID: <508674B2.8050706@rabbitmq.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"</DIV>
<DIV> </DIV>
<DIV>Important addendum: channel calls are *not* thread-safe for </DIV>
<DIV>confirmations: The channel interface is thread-safe now, except for </DIV>
<DIV>counting confirms and checking!</DIV>
<DIV> </DIV>
<DIV>There is an outstanding bug to review this, and the problems associated </DIV>
<DIV>with the fact that publishing and receiving a seqno is not an atomic </DIV>
<DIV>operation.</DIV>
<DIV> </DIV>
<DIV>Anyway - you *may* wish to share a Channel between threads or not, but </DIV>
<DIV>if you're using confirms then you should *not* share a Channel between </DIV>
<DIV>multiple threads. I'll make sure the javadoc changes reflect this state </DIV>
<DIV>of affairs.</DIV>
<DIV> </DIV>
<DIV>Cheers,</DIV>
<DIV>Tim</DIV>
<DIV> </DIV>
<DIV>On 10/23/2012 11:29 AM, Tim Watson wrote:</DIV>
<DIV>> Actually, that's not quite right. Channels *are* thread safe in the </DIV>
<DIV>> java-client, and can be shared across multiple threads if you wish. As </DIV>
<DIV>> the Java client API documentation </DIV>
<DIV>> (http://www.rabbitmq.com/api-guide.html) states however:</DIV>
<DIV>></DIV>
<DIV>> "Channel instances are safe for use by multiple threads. Requests into </DIV>
<DIV>> a Channel are serialized, with only one thread being able to run a </DIV>
<DIV>> command on the Channel at a time. Even so, applications should prefer </DIV>
<DIV>> using a Channel per thread instead of sharing the same Channel across </DIV>
<DIV>> multiple threads."</DIV>
<DIV>></DIV>
<DIV>> In other words, because the transmission of AMQP commands via a given </DIV>
<DIV>> Channel is serialised, there is probably little or no benefit in </DIV>
<DIV>> sharing the channel between threads.</DIV>
<DIV>></DIV>
<DIV>> Unfortunately, whilst we've updated the documentation on the website </DIV>
<DIV>> to reflect this change (which was merged in September 2011 and </DIV>
<DIV>> released in 2.7.0) we appear to have missed the javadocs for the </DIV>
<DIV>> Channel class - I will get that fixed asap so as to avoid any further </DIV>
<DIV>> confusion!</DIV>
<DIV>></DIV>
<DIV>> Cheers,</DIV>
<DIV>> Tim</DIV>
<DIV>></DIV>
<DIV>> On 10/23/2012 02:08 AM, Laurent Vauthrin wrote:</DIV>
<DIV>>> Thanks for clearing that up!</DIV>
<DIV>>></DIV>
<DIV>>> On Mon, Oct 22, 2012 at 3:46 PM, Michael Klishin </DIV>
<DIV>>> <michael.s.klishin@gmail.com <mailto:michael.s.klishin@gmail.com>> wrote:</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> 2012/10/22 Laurent Vauthrin <lvauthrin@gmail.com</DIV>
<DIV>>> <mailto:lvauthrin@gmail.com>></DIV>
<DIV>>></DIV>
<DIV>>> My questions are:</DIV>
<DIV>>> 1. Should we be using a channel per thread considering that</DIV>
<DIV>>> we're synchronizing the basicPublish call anyway?</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> Yes. Channels are just integer on the wire and a little bit of</DIV>
<DIV>>> memory allocated on the JVM heap. They are very cheap</DIV>
<DIV>>> for all intents and purposes and you are much more likely to max</DIV>
<DIV>>> out your OS and hardware resources (assuming 1 channel per JVM</DIV>
<DIV>>> thread) before</DIV>
<DIV>>> you run into issues with channel objects.</DIV>
<DIV>>></DIV>
<DIV>>> 2. Can we just share one channel across all threads and not</DIV>
<DIV>>> synchronize the call to basicPublish?</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> No. The real issue with shared channels is that large messages</DIV>
<DIV>>> will result in multiple protocol frames being sent</DIV>
<DIV>>> for a single basicPublish operation. When publishing on the same</DIV>
<DIV>>> channel from multiple threads, this may result</DIV>
<DIV>>> in frames being delivered out of order:</DIV>
<DIV>>></DIV>
<DIV>>> T1 => basicPublish => [Frame11] [Frame12] [Frame13]</DIV>
<DIV>>> T2 => basicPublish => [Frame21] [Frame22] [Frame23]</DIV>
<DIV>>></DIV>
<DIV>>> may result in the following delivery order, all on the same channel:</DIV>
<DIV>>></DIV>
<DIV>>> [Frame11][Frame21][Frame12][Frame13][Frame22][Frame23]</DIV>
<DIV>>></DIV>
<DIV>>> and because all frames are on the same channel, RabbitMQ won't be</DIV>
<DIV>>> able to tell how to reconstruct your messages.</DIV>
<DIV>>> -- </DIV>
<DIV>>> MK</DIV>
<DIV>>></DIV>
<DIV>>> http://github.com/michaelklishin</DIV>
<DIV>>> http://twitter.com/michaelklishin</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> <mailto:rabbitmq-discuss@lists.rabbitmq.com></DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> rabbitmq-discuss mailing list</DIV>
<DIV>>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> rabbitmq-discuss mailing list</DIV>
<DIV>> rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV> </DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121023/6b69fdfd/attachment-0001.htm></DIV>
<DIV> </DIV>
<DIV>------------------------------</DIV>
<DIV> </DIV>
<DIV>_______________________________________________</DIV>
<DIV>rabbitmq-discuss mailing list</DIV>
<DIV>rabbitmq-discuss@lists.rabbitmq.com</DIV>
<DIV>https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>End of rabbitmq-discuss Digest, Vol 65, Issue 23</DIV>
<DIV>************************************************</DIV>
<DIV> </DIV></DIV></BODY></HTML>