Thanks Tim for youe feedback!
I'm using JDBC persistence adapter, storing the messages in PostgreSQL.
I'm using GroupID for ordering the messages withing the group. So, adding
more consumers does not help if message burst is from couple of groups.
I'm using memoryUsage setting to limit the memor
ActiveMQ version 5.11.3
No producer flow control.
I've noticed the following issue:
- Consumers
he problem messages,
> you could write a consumer that uses that selector and simply acks the
> message (discarding it) to clear things up.
>
> Tim
> On Dec 1, 2015 12:43 PM, "Takawale, Pankaj"
> wrote:
>
> > Yes, there are messages in the queue that do not ma
Yes, there are messages in the queue that do not match any of the consumer
selectors. I wonder why they landed up in the queue.
I've also noticed the high CPU usage that you mentioned.
I've one VirtualTopic, and around 50 selector-aware queues on it. System
processes around 40K different JMSXGrou
, Takawale, Pankaj <
pankaj.takaw...@dowjones.com> wrote:
> Further update:
> These are all Selector Aware Queues.
> One VirtualTopic, and multiple Selector Aware queues underneath it.
> I noticed one of the big queue that is not dispatching messages to the
> consumers has lot
of matched messages due to mixing of
priorities.
On Mon, Nov 30, 2015 at 11:36 AM, Takawale, Pankaj <
pankaj.takaw...@dowjones.com> wrote:
> One more observation:
> Number of consumers being displayed on Admin UI are way more than actual
> consumers.
> Admin UI is showing
On Mon, Nov 30, 2015 at 10:02 AM, Takawale, Pankaj <
pankaj.takaw...@dowjones.com> wrote:
> Yes, my messages has mixed priorities.
>
> I've around 100 queues, 1500 connections, 2500 consumers, and 20
> producers. Broker processes around 6 million messages per day.
> This
h" wrote:
>
> >
> > Just set your store version to 6 via
> BrokerService#setStoreOpenWireVersion
> >
> > On 11/27/2015 02:29 PM, Takawale, Pankaj wrote:
> > > I tried that, but ActiveMQ 5.12 does not start with the 5.11 messages
> in
> > > datab
I tried that, but ActiveMQ 5.12 does not start with the 5.11 messages in
database.
I got the same exception mentioned in
https://issues.apache.org/jira/browse/AMQ-5995
Thanks
Pankaj
On Fri, Nov 27, 2015 at 2:08 PM, Timothy Bish wrote:
> On 11/27/2015 01:31 PM, Takawale, Pankaj wr
Version: 5.11.1
Persistence: JDBC (Postgresql)
Consumers are using Selector expressions to select messages based on
JMSXGroupID.
When a queue receives burst of messages, sometimes all messages gets stuck
in queue, and consumers would not receive any messages.
But, when I click on the queue throu
You could achieve it from your application logic. You could have your
producer or consumers break the JMSXGroupID stickiness by sending
JMSXGroupSeq=-1
message after producing or receiving N messages from the same groupID.
After stickiness break up, new consumers would get a chance to acquire the
g
t how to optimize them (or the software algorithm that needs them
> in the first place, whichever), and submit a patch to make the JDBC adapter
> better.
>
> Tim
>
> Tim
>
> On Sat, May 30, 2015 at 9:54 AM, Takawale, Pankaj <
> pankaj.takaw...@dowjones.com> wrote:
>
I ran into same situation again. When I reboot database service, and
activemq service. AMQ starts delivering messages for a while, and it stops
doing that.
Thread dump is showing all stomp threads are waiting on a lock - not sure
if it's normal scenario?
I'm using nio for openwire, and stomp+nio
Any update on this issue?
https://issues.apache.org/jira/browse/AMQ-5459
Regards,
Pankaj.
On Mon, Dec 1, 2014 at 6:16 PM, pankajtakawale
wrote:
> Hi,
>
> I faced following exception while testing ActiveMQ leveldb cluster.
> On this exception, master demotes itself to slave. New master faces sam
14 matches
Mail list logo
