Hi guys,
I'm investigating ActiveMQ for a trial in the following scenario:
1. End-customer own ships/planes/boats (3-5 vessels) that are linked to the
HQ on land via Satellite
2. Satellite provisions on-demand datalink
3. Data will need to be sync between HQ and vessels on a regular basis
4. Sate
thanks Dejan, that worked perfect :)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Does-ActiveMQ-have-the-concepts-of-lazy-writes-to-disk-tp3040432p3044084.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hey, I just noticed that when I run only one of the consumers in the example,
one message stays in the
queue and does not get consumed.
If I start both consumers all messages are consumed. Can you explain this
scenario ?
I am using as a connection factory URL :
tcp://localhost:61616?jms.prefetchP
Great. That was it. Thanks.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Concurrent-consumers-tp3041439p3043739.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
networks of brokers in activemq are store and forward. So a persistent
message will only exist on one broker at a time.
If can start on the embedded broker and get forward to a networked
broker if there is demand, In which case it will be removed/consumed
from the embedded broker and sent to the ta
I have however also notice that persistent doesn't appear to handle
failover well when in a network of brokers setup. For instance say you
have 3 brokers with a consumer attached to each. All connected in a
persistent style. If broker 1 goes down and the consumer switches over
to broker 2. Any mess
Hi
I wonder what performance is expected with request/reply, in queries/second
We see about 500qps, just roundtripping to another server, is this low?
When we just dump messages to the activemq instance we can send approx 5000
messages per second
If you think of persistence in the same way you would a POP3 store,
i.e the object of the persistence store is more to provide reliability in that
1: Write incoming message to disk,
2: Maintain a journal of actions taken to the message
3: Remove the message from the store once consumed.
So the
I am in the phase of imagining what using ActiveMQ to design a wrapper
around a legacy process would look like, and reading the book, which I
have bought. I should say that I am impressed so far with ActiveMQ and
the mapping of what it does with what I am trying to do seems very good.
I am tr
Hi,
you can use asynchronous sending. See
http://activemq.apache.org/how-do-i-enable-asynchronous-sending.html and
http://activemq.apache.org/async-sends.html
for more info
Cheers
--
Dejan Bosanac
-
FuseSource - The experts in open source integration and messaging.
Email: dej...
10 matches
Mail list logo