ActiveMQ version 5.3.2 and 5.4 Snapshot
ActiveMQ is setup as a standalone broker.
NODE_REQUEST topic is non-persistent.
I have been getting an “Invalid acknowledgment” exception, after a process
which was subscribed to a non-durable topic was killed by a SIGKILL (kill
-9). It appears as thoug
I have a java class which subscribes to a TOPIC. When the broker goes down
(no failover broker), the code shuts down the session, connection and
consumer and then tries to reconnect to the broker.
http://old.nabble.com/file/p28365609/activemq-shutdown.png
Once the broker is back up, the co
Thanks. I figured out the problem had nothing to do with ACTIVEMQ. The
onMessage method was calling a DB function which was blocking.
T
Márcio Geovani Jasinski wrote:
>
> Hi Tom,
>
> This is pretty strange behavior - looks like your consumer is not running
> after a while.
> I think you
Environment
ActiveMQ-5.3.0 standalone
Java 1.6.0_11
Fedora 10
Using publish/subscribe (TOPICS) in non persistent messaging mode. The
ActiveMQ broker is setup with persistent=false.
Publisher is sending an ObjectMessage every 5 seconds. I have one message
consumer subscribing to the Topic. Th
