I am trying to integrate with JBoss using the ActiveMQ resourse adapter as
suggested on the http://activemq.apache.org/jboss-integration.html JBoss
Integration page. However I am getting the following exception:
javax.jms.InvalidDestinationException: Destination is not an instance of
SpyDestina
I tried a little experiment to understand ActiveMQ's behavior when the
network is disrupted. It appears that there is some sort of connection
monitoring going on between the client and the ActiveMQ broker (either at
the broker level or at the socket level). ActiveMQ keeps retrying the
message unti
Tom Samplonius-2 wrote:
>
>
> I don't understand the distinction between, "subscriber can not lose a
> message" vs. "subscriber can drop messages when it is disconnected".
> Subscribers are only going to lose messages unless they disconnect, or are
> disconnected. So I think you want durabl
Could someone please help me with this question?
Naresh Bhatia wrote:
>
> I would like to use ActiveMQ in an application where subcribers must
> receive EVERY message published to their topic. If a subscriber looses a
> message, its state would be out-of-sync with the publishe
I would like to use ActiveMQ in an application where subcribers must receive
EVERY message published to their topic. If a subscriber looses a message,
its state would be out-of-sync with the publisher - and that would be a bad
thing! Note however, that there is no need to receive messages when the
Great! Thanks.
Naresh
--
View this message in context:
http://www.nabble.com/How-to-receive-messages-concurrently-from-a-queue--tf3949698s2354.html#a11215154
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Jonas, that did the trick. Thank you.
BTW, are the default values documented somewhere? I could only find them
burried deep in the JMX console.
Naresh
--
View this message in context:
http://www.nabble.com/How-to-receive-messages-concurrently-from-a-queue--tf3949698s2354.html#a11213111
Sent fr
I have a very simple Java program that creates 10 MessageListeners to receive
JMS messages concurrently from a queue. The MessageListeners share the same
JMS Connection, but create their own Session and MessageConsumer (I have
also tried this with each MessageListener creating its own Connection).