kk, on the up side, if you do get it to work and document what you have learned either here or in a documentation jira issue or in a blog, the situation w.r.t documentation can only get better and the learning curve will shorten.
2009/7/14 kkarank <karan...@gmail.com>: > > Many thanks JLuna > > I must confess I am a newbie to STOMP Php library and find it really poor in > terms of documentation. Feels like someone developer on some planet has done > us all a favor by dumping some code on the google code list and given us a > free hand on how to scratch our heads and try to get it all working > together. The joys of open-source i guess. > > The poor and sparse STOMP documentation makes no mention of the points you > raise below but I will try following your suggestions and see how it goes. > It is unlikely though that I will ever use such a poorly documented library > in a production environment for the simple reason that it will be a huge > learning curve for developers - time that I guess would be better spent in > more productive activities. > > Regards > kk > > > > Jose Luna-2 wrote: >> >> >> Are you sure you're not setting the same client-id header for both >> clients? If you are, I don't believe the second client will be allowed to >> connect -- you'll receive an exception from the broker. >> >> On that note, do you know if you're connecting to the broker at all with >> the second client? If so, what's the broker's response when you subscribe >> to the queue? If you're not sure how to check for these things, you >> should start by seeing how errors are handled by the PHP stomp library, >> and make sure that you're handling them properly. Next, you'll want to >> tail the activemq log to see if the broker is throwing any exceptions, on >> *nix OSes: >> $ tail -f data/activemq.log >> >> Finally, use wireshark (or some other packet sniffing software) to see the >> exact traffic going on between the client and broker. You should capture >> the data in plain text (ascii). If you're not sure how to interpret it, >> you can then respond with the output so that we can have a look. >> >> JLuna >> >> >> >> ----- Original Message ---- >>> From: kkarank <karan...@gmail.com> >>> To: users@activemq.apache.org >>> Sent: Tuesday, July 14, 2009 12:40:08 AM >>> Subject: Re: Unable to have multiple consumers on the same broker >>> >>> >>> Ok just played around with setting the prefetch size to 50 in the URL >>> when >>> using the connect command from STOMP - still the same problem >>> >>> I am struggling to understand though as to how the prefetch size could >>> have >>> anything to do with this. Reading through the docs - this setting takes >>> care >>> of how many messages are streamed to EACH consumer - my problem is >>> completely irrelevant to this fact. I am only able to set ONE consumer >>> per >>> queue. >>> >>> kkarank wrote: >>> > >>> > No I did not set the prefetch size - just used the defaults that come >>> with >>> > the PHP Stomp client. - I will play around and come back >>> > >>> > Thanks :) >>> > >>> > bsnyder wrote: >>> >> >>> >> On Mon, Jul 13, 2009 at 9:53 PM, kkarankwrote: >>> >>> >>> >>> Thanks Bruce, >>> >>> >>> >>> I am connecting to the broker from PHP Stomp library and there is >>> >>> nothing in >>> >>> the examples you mention that talks about how to setup multiple >>> >>> consumers >>> >>> listening to the same broker port but on multiple queues? >>> >> >>> >> Ah, you didn't mention anything about using Stomp. Have you set the >>> >> prefetch size? See the following for more info about prefetch and >>> >> prefetch with Stomp: >>> >> >>> >> http://activemq.apache.org/what-is-the-prefetch-limit-for.html >>> >> >>> >> http://activemq.apache.org/stomp.html#Stomp-ActiveMQextensionstoStomp >>> >> >>> >> Bruce >>> >> -- >>> >> perl -e 'print >>> >> unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E >>> >> );' >>> >> >>> >> ActiveMQ in Action: http://bit.ly/2je6cQ >>> >> Blog: http://bruceblog.org/ >>> >> Twitter: http://twitter.com/brucesnyder >>> >> >>> >> >>> > >>> > >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Unable-to-have-multiple-consumers-on-the-same-broker-tp24467033p24473573.html >>> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> >> >> >> >> > > -- > View this message in context: > http://www.nabble.com/Unable-to-have-multiple-consumers-on-the-same-broker-tp24467033p24474067.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
