One important thing I forgot to mention in last update is:
> There is no durable subscriber on this topic.
> messages sent on this topic are non-persistent.
Then how come kahaDB indexes are getting corrupted ? I think the messages
send on this topic should not even go to kahaDB.
Can someone p
Greetings,
We are on version 5.10 - recently migrated, but don't think my problem
is version specific.
In short, it boils down to can I evaluate the selector information on
producer side? I need to make decision whether this is a good time to
place the job or not.
I have multiple producers
+1
This approach is a derivative of the single purpose queue anti-pattern see
http://books.google.com.au/books?id=1G3Pa_LoIGQC&pg=PA236&lpg=PA236&dq=single+purpose+queue&source=bl&ots=O57wy-t5MZ&sig=ADfUPDpAUywSVNnrnanjnkus13g&hl=en&sa=X&ei=nNDFU6DYIcvn8AWPgoKYBw&ved=0CB4Q6AEwAA#v=onepage&q=single
I have been happily testing clusters of activemq 5.10 nodes; we desire highly
available distributed topics. I just wanted to sanity check my
understanding of the persistent storage with a cluster.
My master cluster nodes are each configured with a unique kahaDB directory.
i.e.
Good questions. For Perl and Python, I'm unsure; I know STOMP works with
them. Of course, an openwire implementation will open up a lot of ActiveMQ
features, but I can't speak to the state of such solutions.
Maybe we'll get lucky and hear from someone with more experience in the area
;-).
--
Sorry for the mis-information and noise previously on this thread.
I've dug into this more and found out a few more details: our producer app
(Spring-base web app) spins up an embedded broker (v5.3-fuse libraries) that
'receives' messages from the app and forwards those messages on to the 'hub'
br
If I understand correctly, the code is doing the following:
* Competing consumers read from the same queue
* One of several consumers will be able to process a message while the other
two will not
* When the process can handle the message, it does so and acknowledges it
* When the process cannot h
Thanks very much! I'll check them out.
I'm not wedded to the STOMP protocol, but I haven't yet succeeded in
understanding what I've read about the different protocols available. What
protocol should I use for a simple example like this, and what Python
package should I use that implements it?
T
Start with basic network troubleshooting, such as using telnet from the
client machine to the port on the server to make sure it's reachable.
Using strace or tcpdump to trace the operations to see if they are making it
across the network as well is a good way to go.
--
View this message in con
Have you seen this page?
http://stomp.github.io/implementations.html
It lists at least 2 Python solutions, one specific to ActiveMQ. Note that
the the base STOMP protocol does not include acknowledgements; in perl,
that's the Net::Stomp module. There is an enhancement that supports
acknowledgem
I am beginning to do my homework, and I think I have a basic idea of the
difference between a topic and a queue. Since my current task is to send
messages to a queue (or a topic), I don't care how the message will be
received. That's our client's responsibility.
But I remain curious. I'd like t
Hi,
I've checked it once again and broker's web console shows 3 active
consumers.
TIA.
Sergey
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Activating-consumer-for-each-message-groups-tp4683066p4683266.html
Sent from the ActiveMQ - User mailing list archive at Nabble
12 matches
Mail list logo
