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" <[email protected]> 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 <[email protected]> > 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. > >> [email protected] | www.redhat.com > >> twitter: @tabish121 > >> blog: http://timbish.blogspot.com/ > >> > >> > > > -- > Tim Bish > Sr Software Engineer | RedHat Inc. > [email protected] | www.redhat.com > twitter: @tabish121 > blog: http://timbish.blogspot.com/ > >
