Hi, are you using queues or topic destination? I'm also experiencing it right
now. I'm using topics.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/After-failover-earlier-messages-are-lost-tp4706630p4716097.html
Sent from the ActiveMQ - User mailing list archive at Nabbl
I have an app that submits JMS messages to a queue. I'd like to check that
there is a consumer listening on teh other side when I submit. If not, I'd
like to raise a warning to the callilng program. Is there a java call that
will tell me how many consumers are subscribed to a queue after I conne
Hi,
I'm running Artemis 1.3.0 embedded inside a spring app running in Tomcat.
I have a remote message producer (NumberGuessMain.java) that uses the Apache
Qpid Proton library to push messages onto an Artemis queue with the URL:
amqp://localhost:5672/native-2-java
The messages cre
I am not certain about this but I think the version mismatch was discovered
because the ackType in the exception was = 6, and someone (not me because at
that time I was not involved with the project) noticed that v5.5.1 did not
support ackType = 6, i.e. the max ackType for v5.5.1 is 5.
I don't
Normally, the operation of message acknowledgement and redelivery should
have nothing to do with publisher settings. With that said, there are some
broker configurations that change operation in non-obvious ways, such as
the "optimized dispatch" option.
Are these persistent messages delivered to
A couple of thoughts on this front.
First, how was the conclusion of different client versions made? I'm
curious because I can't think of any way that should be an issue.
Second, is the consumer using the failover transport?
This JMS Exception can happen normally without indicating a problem,
e
I realize using retroactive consumers with a
custom SubscriptionRecoveryPolicy might be just what I need.
2016-09-01 21:06 GMT+02:00 Julien Nicoulaud :
> Hi,
>
> I'm trying to implement the following simple pattern using ActiveMQ:
> - my server maintains a "state"
> - my clients connect to the
Hi,
I'm trying to implement the following simple pattern using ActiveMQ:
- my server maintains a "state"
- my clients connect to the server, get a snapshot of the state and
suscribe to updates of the state
So I need the "state snapshot + subscription" step to be atomic for each
client connectin
Thanks Matt. And yes I was aware of the behavior of CLIENT_ACK, although when
I started this research I was not. Before this I was under the impression that
it was a single message ack.
Michael Tarullo
Contractor (Engility Corp)
Software Engineer
FAA WJH Technical Center
(609)485-5294
-O
+1 Agree that debugging it is the only surefire way to understand what
is going on.
On a side note-- CLIENT_ACKNOWLEDGE is kludgy of sorts. Be sure to
understand that it acknowledges the current message and _all_ previous
messages. It isn't an individual message acknowledgement as most people
Got it to work when using spring boot at both sender and listener.
Is there anything I must do to make it work when sender is in plain java
without spring but listener is using spring boot
--
View this message in context:
http://activemq.2283324.n4.nabble.com/kill-9-in-message-listener-tp471462
Thank you Tim.
Michael Tarullo
Contractor (Engility Corp)
Software Engineer
FAA WJH Technical Center
(609)485-5294
-Original Message-
From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain
Sent: Thursday, September 01, 2016 8:47 AM
To: ActiveMQ Users
Subject: Re: Need He
Since you have the 5.5.1 source code, I recommend you attach a debugger to
the broker process and set a breakpoint on the
TopicSubscription.acknowledge() method; the stack will tell you how you got
there. Setting breakpoints on the broker can lead to instability and may
force you to restart it (pl
Hi Martin,
When updating from 5.11 to 5.14 I encountered a different issue (which might
have existed during earlier upgrades as well). I am in the situation that I can
remove the kahadb contents before starting 5.14. Maybe that can be a solution
for you as well.
Also see the thread "Updating
When trying to upgrade from 5.12.2 to 5.14.0 we encounter this exception at
startup:
Caused by: java.io.IOException: Detected missing journal files. [3]
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:978)[102:org.apache.activemq.activemq-osgi:5.14.0]
at
15 matches
Mail list logo