Hi Jose,
I'm using the prioritizedMessages=true because of the JMS grouping feature.
In the application I'm running, one of the most important features is that
messages with the same group ID are not processed in parallel, thus the
message grouping ensuring the same consumer always gets the mess
Are you acknowledging your messages as you finish consuming them?
Also, what's the reason you're using a selector on the JMSMessageId?
Can you describe what messages you "can find" (and what "find" means) and
which ones you can't, as well as where?
Tim
On Dec 10, 2015 4:06 PM, "dabayev" wrote:
Hello,
I have a very simple setup. I am using ActiveMQ 5.11.1 and have a simple
persistent Queue where I publish messages. I am running a utility to update
headers on these messages.
I simply make my connection, then I start it, get the session, create the
Queue and then create the consumer usin
Adding "priorityBackup=true" on client seem to work as in falling back
to original node once it is back to service. Thanks.
On 12/9/15 10:30 PM, Tim Bain wrote:
Also, did you see the "Update" paragraph at the bottom of
http://bsnyderblog.blogspot.com/2010/10/new-features-in-activemq-54-automati
2015-12-09 13:55 GMT+01:00 frankie_hr :
> Hi All,
>
> I'm having issues with a little piece of the code which is supposed to
> selectively consume the messages from a queue, using the message priority as
> the selector value. In addition to that, the grouping of messages is also
> being used.
>
> T
The broker itself (class BrokerService) offers a method
void addShutdownHook(Runnable hook)
khandelwalanuj wrote
> My requirement :
>
> I need to execute some code when I stop the broker. What is the best way
> to do this ?
>
> Thanks,
> Anuj
--
View this message in context:
http:
Hello:
I'm trying to understand how message priority works in AMQ 5.10
I'm reading
http://activemq.apache.org/how-can-i-support-priority-queues.html
and I don't understand this sentence
"Since the message cursors (and client side) implement strict ordering
of priorities, it's possible to obser
Also, this fix will be included in 5.12.2 as well when that is released.
On Wed, Dec 9, 2015 at 5:41 AM, Dejan Bosanac wrote:
> Hi Tim, yes, it prevents untrusted classes deserializing inside the broker,
> including when you want to look at them in the web console.
>
> Regards
> --
> Dejan Bosan
I think that's exactly what's going on. I didn't notice that line in your
code when you first posted it; sorry!
On Dec 10, 2015 7:28 AM, "frankie_hr" wrote:
> Hi All,
>
> Here's an update to the point Three:
>
> > Third, use a JMX viewer such as JConsole to look at the subscriptions on
> > that
I do not have "priorityBackup=true" as I have only one URL for client to
connect to. I do have "updateClusterClientsOnRemove=true" set however.
On 12/9/15 10:30 PM, Tim Bain wrote:
Also, did you see the "Update" paragraph at the bottom of
http://bsnyderblog.blogspot.com/2010/10/new-features-in-
Hi All,
Here's an update to the point Three:
> Third, use a JMX viewer such as JConsole to look at the subscriptions on
> that queue. Find the subscription that isn't working (#1) and see whether
> it's present and whether its selector looks correct. See whether any
> messages have been disp
Many thanks, and apologies for the duplicate post; I thought I'd searched for
posts about this before opening this one, but I obviously couldn't have
searched hard enough!
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-and-commons-collection-security-vulnerabil
12 matches
Mail list logo
