You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by "Takawale, Pankaj" <pa...@dowjones.com> on 2015/11/27 19:31:47 UTC
JDBC 300K messages stuck in queue, consumers receives messages when
manually browsed the queue
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 through Admin UI, consumer apps receive
bunch of messages, and queue freezes again.
Is this bug related to AMQ-5853
<https://issues.apache.org/jira/browse/AMQ-5853> ?
Thanks,
Pankaj.
Re: JDBC 300K messages stuck in queue, consumers receives messages
when manually browsed the queue
Posted by "Takawale, Pankaj" <pa...@dowjones.com>.
I've started consumer with no selector on it. It started receiving all the
messages, and I'm filtering out the unwanted in application.
Thank you,
Pankaj
On Tue, Dec 1, 2015 at 4:39 PM, Tim Bain <tb...@alumni.duke.edu> wrote:
> If you control the producers and are willing to lose the unconsumed
> messages, you can have the producers set the JMSExpiration header so that
> messages expire if they're not consumed after a certain amount of time.
>
> But that won't help you get out of the current problem. For right now, if
> you can figure out a selector that will match only the 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" <pa...@dowjones.com>
> wrote:
>
> > 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 JMSXGroupIDs. So each selector-aware queue
> > only receives the subset of full fire-hose based on the consumers'
> > selectors subscription. We use JMSXGroupID for the filtering, as the same
> > attribute would be used for the load-balancing purpose across multiple
> > queue consumers. So there are multiple consumers subscribed with the same
> > selector expression.
> >
> > I've tried to upgrade activemq to v5.12.2, and nightly 5.13 snapshot
> > v5.13-20151130.033036-75. It showed the same symptoms.
> >
> > Is there any way to get out of this situation? Any way to purge the
> > unmatched messages from the queue? If there is no any existing way, could
> > you please point me to the code sample for unmarshaling the message from
> > activemq_msgs table, so that I could write cleanup job?
> >
> > Thanks
> > Pankaj
> >
> >
> >
> >
> >
> > On Mon, Nov 30, 2015 at 7:04 PM, artnaseef <ar...@artnaseef.com> wrote:
> >
> > > Are there messages in the queue that do not match any of the consumer
> > > selectors? If so, only "MaxPageSize" messages (300 by default) can
> reach
> > > the head of the queue before dispatching stops. I believe that number
> > > increases while browsing, hence the reason browsing temporarily
> aleviates
> > > the problem.
> > >
> > > Note that I'm curious why the use of selectors on JMSXGroupID since the
> > > entire purpose of JMSXGroupID is to select an exclusive consumer for a
> > > subset of the queue's messages (the subset that shares the same group
> > ID).
> > >
> > > Also note that JMSXGroup's share a similiar issue related to
> MaxPageSize,
> > > if
> > > any one of the consumers is slow.
> > >
> > > Finally, note that the backlog of messages with selectors and
> JMSXGroups,
> > > when messages cannot be dispatched (due to no available, matching
> > > consumer),
> > > leads to a significant increase in CPU usage.
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://activemq.2283324.n4.nabble.com/JDBC-300K-messages-stuck-in-queue-consumers-receives-messages-when-manually-browsed-the-queue-tp4704330p4704436.html
> > > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> > >
> >
>
Re: JDBC 300K messages stuck in queue, consumers receives messages
when manually browsed the queue
Posted by Tim Bain <tb...@alumni.duke.edu>.
If you control the producers and are willing to lose the unconsumed
messages, you can have the producers set the JMSExpiration header so that
messages expire if they're not consumed after a certain amount of time.
But that won't help you get out of the current problem. For right now, if
you can figure out a selector that will match only the 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" <pa...@dowjones.com>
wrote:
> 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 JMSXGroupIDs. So each selector-aware queue
> only receives the subset of full fire-hose based on the consumers'
> selectors subscription. We use JMSXGroupID for the filtering, as the same
> attribute would be used for the load-balancing purpose across multiple
> queue consumers. So there are multiple consumers subscribed with the same
> selector expression.
>
> I've tried to upgrade activemq to v5.12.2, and nightly 5.13 snapshot
> v5.13-20151130.033036-75. It showed the same symptoms.
>
> Is there any way to get out of this situation? Any way to purge the
> unmatched messages from the queue? If there is no any existing way, could
> you please point me to the code sample for unmarshaling the message from
> activemq_msgs table, so that I could write cleanup job?
>
> Thanks
> Pankaj
>
>
>
>
>
> On Mon, Nov 30, 2015 at 7:04 PM, artnaseef <ar...@artnaseef.com> wrote:
>
> > Are there messages in the queue that do not match any of the consumer
> > selectors? If so, only "MaxPageSize" messages (300 by default) can reach
> > the head of the queue before dispatching stops. I believe that number
> > increases while browsing, hence the reason browsing temporarily aleviates
> > the problem.
> >
> > Note that I'm curious why the use of selectors on JMSXGroupID since the
> > entire purpose of JMSXGroupID is to select an exclusive consumer for a
> > subset of the queue's messages (the subset that shares the same group
> ID).
> >
> > Also note that JMSXGroup's share a similiar issue related to MaxPageSize,
> > if
> > any one of the consumers is slow.
> >
> > Finally, note that the backlog of messages with selectors and JMSXGroups,
> > when messages cannot be dispatched (due to no available, matching
> > consumer),
> > leads to a significant increase in CPU usage.
> >
> >
> >
> > --
> > View this message in context:
> >
> http://activemq.2283324.n4.nabble.com/JDBC-300K-messages-stuck-in-queue-consumers-receives-messages-when-manually-browsed-the-queue-tp4704330p4704436.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >
>
Re: JDBC 300K messages stuck in queue, consumers receives messages
when manually browsed the queue
Posted by "Takawale, Pankaj" <pa...@dowjones.com>.
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 JMSXGroupIDs. So each selector-aware queue
only receives the subset of full fire-hose based on the consumers'
selectors subscription. We use JMSXGroupID for the filtering, as the same
attribute would be used for the load-balancing purpose across multiple
queue consumers. So there are multiple consumers subscribed with the same
selector expression.
I've tried to upgrade activemq to v5.12.2, and nightly 5.13 snapshot
v5.13-20151130.033036-75. It showed the same symptoms.
Is there any way to get out of this situation? Any way to purge the
unmatched messages from the queue? If there is no any existing way, could
you please point me to the code sample for unmarshaling the message from
activemq_msgs table, so that I could write cleanup job?
Thanks
Pankaj
On Mon, Nov 30, 2015 at 7:04 PM, artnaseef <ar...@artnaseef.com> wrote:
> Are there messages in the queue that do not match any of the consumer
> selectors? If so, only "MaxPageSize" messages (300 by default) can reach
> the head of the queue before dispatching stops. I believe that number
> increases while browsing, hence the reason browsing temporarily aleviates
> the problem.
>
> Note that I'm curious why the use of selectors on JMSXGroupID since the
> entire purpose of JMSXGroupID is to select an exclusive consumer for a
> subset of the queue's messages (the subset that shares the same group ID).
>
> Also note that JMSXGroup's share a similiar issue related to MaxPageSize,
> if
> any one of the consumers is slow.
>
> Finally, note that the backlog of messages with selectors and JMSXGroups,
> when messages cannot be dispatched (due to no available, matching
> consumer),
> leads to a significant increase in CPU usage.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/JDBC-300K-messages-stuck-in-queue-consumers-receives-messages-when-manually-browsed-the-queue-tp4704330p4704436.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Re: JDBC 300K messages stuck in queue, consumers receives messages
when manually browsed the queue
Posted by artnaseef <ar...@artnaseef.com>.
Are there messages in the queue that do not match any of the consumer
selectors? If so, only "MaxPageSize" messages (300 by default) can reach
the head of the queue before dispatching stops. I believe that number
increases while browsing, hence the reason browsing temporarily aleviates
the problem.
Note that I'm curious why the use of selectors on JMSXGroupID since the
entire purpose of JMSXGroupID is to select an exclusive consumer for a
subset of the queue's messages (the subset that shares the same group ID).
Also note that JMSXGroup's share a similiar issue related to MaxPageSize, if
any one of the consumers is slow.
Finally, note that the backlog of messages with selectors and JMSXGroups,
when messages cannot be dispatched (due to no available, matching consumer),
leads to a significant increase in CPU usage.
--
View this message in context: http://activemq.2283324.n4.nabble.com/JDBC-300K-messages-stuck-in-queue-consumers-receives-messages-when-manually-browsed-the-queue-tp4704330p4704436.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JDBC 300K messages stuck in queue, consumers receives messages
when manually browsed the queue
Posted by "Takawale, Pankaj" <pa...@dowjones.com>.
Tried updating ActiveMQ to 5.12.1. It showed the same behavior. No messages
are being dispatched from large pending message queues to consumers. After
I click on the queue, messages gets dispatched to consumer for a while, and
queue freezes again.
Thanks
Pankaj
On Mon, Nov 30, 2015 at 12:51 PM, Takawale, Pankaj <
pankaj.takawale@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 unmatched messages. I think these unmatched messages
> are suppressing the dispatching of matched messages due to mixing of
> priorities.
>
>
>
> On Mon, Nov 30, 2015 at 11:36 AM, Takawale, Pankaj <
> pankaj.takawale@dowjones.com> wrote:
>
>> One more observation:
>> Number of consumers being displayed on Admin UI are way more than actual
>> consumers.
>> Admin UI is showing incorrect? counts:
>> Pending Messages: 568073
>> Number of consumers 408 (I'm expecting only 69 consumers),
>> Messages Enqueued 354845
>> Messages Dequeued 45383
>>
>> Thanks
>> Pankaj
>>
>>
>> On Mon, Nov 30, 2015 at 10:02 AM, Takawale, Pankaj <
>> pankaj.takawale@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 problem is occurring with only couple of high-volume queues. All
>>> other queues are working fine.
>>>
>>>
>>> I drained 300K messages by writing curl script to browse the queue
>>> (whenever script successfully browses queue, consumers would receive
>>> messages). Now queue browsing is not working as I'm getting GATEWAY_TIMEOUT
>>> messages. So around 500K messages are stuck in queue.
>>>
>>> Since it's a production environment, I can not test with the latest
>>> version right away.
>>>
>>> Thanks
>>> Pankaj
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Nov 28, 2015 at 12:19 AM, Tim Bain <tb...@alumni.duke.edu>
>>> wrote:
>>>
>>>> The bug you linked to was pretty specifically about messages with mixed
>>>> priorities. Does that describe your scenario?
>>>> On Nov 27, 2015 12:58 PM, "Timothy Bish" <ta...@gmail.com> 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
>>>> > > 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 <ta...@gmail.com>
>>>> > wrote:
>>>> > >
>>>> > >> On 11/27/2015 01:31 PM, Takawale, Pankaj wrote:
>>>> > >>> 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 through Admin UI, consumer apps
>>>> receive
>>>> > >>> bunch of messages, and queue freezes again.
>>>> > >>>
>>>> > >>> Is this bug related to AMQ-5853
>>>> > >>> <https://issues.apache.org/jira/browse/AMQ-5853> ?
>>>> > >>>
>>>> > >>>
>>>> > >>> Thanks,
>>>> > >>> Pankaj.
>>>> > >>>
>>>> > >> Quick way to find out is to run with the latest release and see
>>>> what
>>>> > >> happens.
>>>> > >>
>>>> > >> --
>>>> > >> Tim Bish
>>>> > >> Sr Software Engineer | RedHat Inc.
>>>> > >> tim.bish@redhat.com | www.redhat.com
>>>> > >> twitter: @tabish121
>>>> > >> blog: http://timbish.blogspot.com/
>>>> > >>
>>>> > >>
>>>> >
>>>> >
>>>> > --
>>>> > Tim Bish
>>>> > Sr Software Engineer | RedHat Inc.
>>>> > tim.bish@redhat.com | www.redhat.com
>>>> > twitter: @tabish121
>>>> > blog: http://timbish.blogspot.com/
>>>> >
>>>> >
>>>>
>>>
>>>
>>
>
Re: JDBC 300K messages stuck in queue, consumers receives messages
when manually browsed the queue
Posted by "Takawale, Pankaj" <pa...@dowjones.com>.
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 unmatched messages. I think these unmatched messages
are suppressing the dispatching of matched messages due to mixing of
priorities.
On Mon, Nov 30, 2015 at 11:36 AM, Takawale, Pankaj <
pankaj.takawale@dowjones.com> wrote:
> One more observation:
> Number of consumers being displayed on Admin UI are way more than actual
> consumers.
> Admin UI is showing incorrect? counts:
> Pending Messages: 568073
> Number of consumers 408 (I'm expecting only 69 consumers),
> Messages Enqueued 354845
> Messages Dequeued 45383
>
> Thanks
> Pankaj
>
>
> On Mon, Nov 30, 2015 at 10:02 AM, Takawale, Pankaj <
> pankaj.takawale@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 problem is occurring with only couple of high-volume queues. All
>> other queues are working fine.
>>
>>
>> I drained 300K messages by writing curl script to browse the queue
>> (whenever script successfully browses queue, consumers would receive
>> messages). Now queue browsing is not working as I'm getting GATEWAY_TIMEOUT
>> messages. So around 500K messages are stuck in queue.
>>
>> Since it's a production environment, I can not test with the latest
>> version right away.
>>
>> Thanks
>> Pankaj
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Sat, Nov 28, 2015 at 12:19 AM, Tim Bain <tb...@alumni.duke.edu> wrote:
>>
>>> The bug you linked to was pretty specifically about messages with mixed
>>> priorities. Does that describe your scenario?
>>> On Nov 27, 2015 12:58 PM, "Timothy Bish" <ta...@gmail.com> 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
>>> > > 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 <ta...@gmail.com>
>>> > wrote:
>>> > >
>>> > >> On 11/27/2015 01:31 PM, Takawale, Pankaj wrote:
>>> > >>> 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 through Admin UI, consumer apps
>>> receive
>>> > >>> bunch of messages, and queue freezes again.
>>> > >>>
>>> > >>> Is this bug related to AMQ-5853
>>> > >>> <https://issues.apache.org/jira/browse/AMQ-5853> ?
>>> > >>>
>>> > >>>
>>> > >>> Thanks,
>>> > >>> Pankaj.
>>> > >>>
>>> > >> Quick way to find out is to run with the latest release and see what
>>> > >> happens.
>>> > >>
>>> > >> --
>>> > >> Tim Bish
>>> > >> Sr Software Engineer | RedHat Inc.
>>> > >> tim.bish@redhat.com | www.redhat.com
>>> > >> twitter: @tabish121
>>> > >> blog: http://timbish.blogspot.com/
>>> > >>
>>> > >>
>>> >
>>> >
>>> > --
>>> > Tim Bish
>>> > Sr Software Engineer | RedHat Inc.
>>> > tim.bish@redhat.com | www.redhat.com
>>> > twitter: @tabish121
>>> > blog: http://timbish.blogspot.com/
>>> >
>>> >
>>>
>>
>>
>
Re: JDBC 300K messages stuck in queue, consumers receives messages
when manually browsed the queue
Posted by "Takawale, Pankaj" <pa...@dowjones.com>.
One more observation:
Number of consumers being displayed on Admin UI are way more than actual
consumers.
Admin UI is showing incorrect? counts:
Pending Messages: 568073
Number of consumers 408 (I'm expecting only 69 consumers),
Messages Enqueued 354845
Messages Dequeued 45383
Thanks
Pankaj
On Mon, Nov 30, 2015 at 10:02 AM, Takawale, Pankaj <
pankaj.takawale@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 problem is occurring with only couple of high-volume queues. All
> other queues are working fine.
>
>
> I drained 300K messages by writing curl script to browse the queue
> (whenever script successfully browses queue, consumers would receive
> messages). Now queue browsing is not working as I'm getting GATEWAY_TIMEOUT
> messages. So around 500K messages are stuck in queue.
>
> Since it's a production environment, I can not test with the latest
> version right away.
>
> Thanks
> Pankaj
>
>
>
>
>
>
>
>
>
> On Sat, Nov 28, 2015 at 12:19 AM, Tim Bain <tb...@alumni.duke.edu> wrote:
>
>> The bug you linked to was pretty specifically about messages with mixed
>> priorities. Does that describe your scenario?
>> On Nov 27, 2015 12:58 PM, "Timothy Bish" <ta...@gmail.com> 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
>> > > 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 <ta...@gmail.com>
>> > wrote:
>> > >
>> > >> On 11/27/2015 01:31 PM, Takawale, Pankaj wrote:
>> > >>> 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 through Admin UI, consumer apps
>> receive
>> > >>> bunch of messages, and queue freezes again.
>> > >>>
>> > >>> Is this bug related to AMQ-5853
>> > >>> <https://issues.apache.org/jira/browse/AMQ-5853> ?
>> > >>>
>> > >>>
>> > >>> Thanks,
>> > >>> Pankaj.
>> > >>>
>> > >> Quick way to find out is to run with the latest release and see what
>> > >> happens.
>> > >>
>> > >> --
>> > >> Tim Bish
>> > >> Sr Software Engineer | RedHat Inc.
>> > >> tim.bish@redhat.com | www.redhat.com
>> > >> twitter: @tabish121
>> > >> blog: http://timbish.blogspot.com/
>> > >>
>> > >>
>> >
>> >
>> > --
>> > Tim Bish
>> > Sr Software Engineer | RedHat Inc.
>> > tim.bish@redhat.com | www.redhat.com
>> > twitter: @tabish121
>> > blog: http://timbish.blogspot.com/
>> >
>> >
>>
>
>
Re: JDBC 300K messages stuck in queue, consumers receives messages
when manually browsed the queue
Posted by "Takawale, Pankaj" <pa...@dowjones.com>.
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 problem is occurring with only couple of high-volume queues. All other
queues are working fine.
I drained 300K messages by writing curl script to browse the queue
(whenever script successfully browses queue, consumers would receive
messages). Now queue browsing is not working as I'm getting GATEWAY_TIMEOUT
messages. So around 500K messages are stuck in queue.
Since it's a production environment, I can not test with the latest version
right away.
Thanks
Pankaj
On Sat, Nov 28, 2015 at 12:19 AM, Tim Bain <tb...@alumni.duke.edu> wrote:
> The bug you linked to was pretty specifically about messages with mixed
> priorities. Does that describe your scenario?
> On Nov 27, 2015 12:58 PM, "Timothy Bish" <ta...@gmail.com> 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
> > > 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 <ta...@gmail.com>
> > wrote:
> > >
> > >> On 11/27/2015 01:31 PM, Takawale, Pankaj wrote:
> > >>> 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 through Admin UI, consumer apps
> receive
> > >>> bunch of messages, and queue freezes again.
> > >>>
> > >>> Is this bug related to AMQ-5853
> > >>> <https://issues.apache.org/jira/browse/AMQ-5853> ?
> > >>>
> > >>>
> > >>> Thanks,
> > >>> Pankaj.
> > >>>
> > >> Quick way to find out is to run with the latest release and see what
> > >> happens.
> > >>
> > >> --
> > >> Tim Bish
> > >> Sr Software Engineer | RedHat Inc.
> > >> tim.bish@redhat.com | www.redhat.com
> > >> twitter: @tabish121
> > >> blog: http://timbish.blogspot.com/
> > >>
> > >>
> >
> >
> > --
> > Tim Bish
> > Sr Software Engineer | RedHat Inc.
> > tim.bish@redhat.com | www.redhat.com
> > twitter: @tabish121
> > blog: http://timbish.blogspot.com/
> >
> >
>
Re: JDBC 300K messages stuck in queue, consumers receives messages
when manually browsed the queue
Posted by Tim Bain <tb...@alumni.duke.edu>.
The bug you linked to was pretty specifically about messages with mixed
priorities. Does that describe your scenario?
On Nov 27, 2015 12:58 PM, "Timothy Bish" <ta...@gmail.com> 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
> > 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 <ta...@gmail.com>
> wrote:
> >
> >> On 11/27/2015 01:31 PM, Takawale, Pankaj wrote:
> >>> 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 through Admin UI, consumer apps receive
> >>> bunch of messages, and queue freezes again.
> >>>
> >>> Is this bug related to AMQ-5853
> >>> <https://issues.apache.org/jira/browse/AMQ-5853> ?
> >>>
> >>>
> >>> Thanks,
> >>> Pankaj.
> >>>
> >> Quick way to find out is to run with the latest release and see what
> >> happens.
> >>
> >> --
> >> Tim Bish
> >> Sr Software Engineer | RedHat Inc.
> >> tim.bish@redhat.com | www.redhat.com
> >> twitter: @tabish121
> >> blog: http://timbish.blogspot.com/
> >>
> >>
>
>
> --
> Tim Bish
> Sr Software Engineer | RedHat Inc.
> tim.bish@redhat.com | www.redhat.com
> twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
>
Re: JDBC 300K messages stuck in queue, consumers receives messages
when manually browsed the queue
Posted by Timothy Bish <ta...@gmail.com>.
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
> 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 <ta...@gmail.com> wrote:
>
>> On 11/27/2015 01:31 PM, Takawale, Pankaj wrote:
>>> 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 through Admin UI, consumer apps receive
>>> bunch of messages, and queue freezes again.
>>>
>>> Is this bug related to AMQ-5853
>>> <https://issues.apache.org/jira/browse/AMQ-5853> ?
>>>
>>>
>>> Thanks,
>>> Pankaj.
>>>
>> Quick way to find out is to run with the latest release and see what
>> happens.
>>
>> --
>> Tim Bish
>> Sr Software Engineer | RedHat Inc.
>> tim.bish@redhat.com | www.redhat.com
>> twitter: @tabish121
>> blog: http://timbish.blogspot.com/
>>
>>
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.redhat.com
twitter: @tabish121
blog: http://timbish.blogspot.com/
Re: JDBC 300K messages stuck in queue, consumers receives messages
when manually browsed the queue
Posted by "Takawale, Pankaj" <pa...@dowjones.com>.
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 <ta...@gmail.com> wrote:
> On 11/27/2015 01:31 PM, Takawale, Pankaj wrote:
> > 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 through Admin UI, consumer apps receive
> > bunch of messages, and queue freezes again.
> >
> > Is this bug related to AMQ-5853
> > <https://issues.apache.org/jira/browse/AMQ-5853> ?
> >
> >
> > Thanks,
> > Pankaj.
> >
>
> Quick way to find out is to run with the latest release and see what
> happens.
>
> --
> Tim Bish
> Sr Software Engineer | RedHat Inc.
> tim.bish@redhat.com | www.redhat.com
> twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
>
Re: JDBC 300K messages stuck in queue, consumers receives messages
when manually browsed the queue
Posted by Timothy Bish <ta...@gmail.com>.
On 11/27/2015 01:31 PM, Takawale, Pankaj wrote:
> 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 through Admin UI, consumer apps receive
> bunch of messages, and queue freezes again.
>
> Is this bug related to AMQ-5853
> <https://issues.apache.org/jira/browse/AMQ-5853> ?
>
>
> Thanks,
> Pankaj.
>
Quick way to find out is to run with the latest release and see what
happens.
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.redhat.com
twitter: @tabish121
blog: http://timbish.blogspot.com/