Hi Kevin,
Do you have any update on this issue?
It looks to me that this config is not really production ready.
What do you think?
Is someone of the development team having a look?
Chris
Il giorno gio 18 dic 2014 21:50 Kevin Burton bur...@spinn3r.com ha
scritto:
Is there a bug report in Jira for it, and has someone been able to identify
a configuration and set of steps to reliably reproduce it? If not, the
odds are good that no one is actively investigating it, so doing those
things would be the first step towards getting the problem fixed.
On Dec 23,
the jira is the folowing
https://issues.apache.org/jira/browse/AMQ-5300
It was opened on july.
I can reproduce it always, with the configuration in my first mail.
Christian
On Tue, Dec 23, 2014 at 3:54 PM, Tim Bain tb...@alumni.duke.edu wrote:
Is there a bug report in Jira for it, and has
I was going to tell you that since you have a configuration that reliably
reproduces the problem, and it's not described in that JIRA (which
describes symptoms but no means of reproducing the problem), you should
update it to provide the configuration so that someone can investigate.
But looking
I’m still working on it and trying to figure it out.. it might take me some
time to reproduce it as it seems to have a few issues that might be
compounding the issue.
Bumping up memory definitely seemed to help resolve the issue.
I think what would be ideal is for me to write a producer/consumer
that bug is very specifically about deleting the
index files for LevelDB and then restarting the broker, whereas you haven't
described doing either of those things.
Yes.. I agree as well. That’s why I didn’t follow up on that thread. I’m
concerned about the error message though.
On Tue, Dec
Based on what Christian has said, it sounds like he's got a configuration
that reliably reproduces his problem whereas you're not at that point yet,
so let's have him create a JIRA bug for that so we don't lose the details
about how to produce it. As you investigate, hopefully you'll be able
Hey. I have a similar configuration and I’m getting a ton of No reader
available for position” messages as well as significant data loss on AMQ
restart.
It literally loses about 95% of the messages I enqueued..
On Wed, Dec 17, 2014 at 9:06 AM, Christian Grassi christiangra...@gmail.com
wrote:
I have a 3 node 5.10 cluster with replicated levelDB as persistent store.
persistenceAdapter
replicatedLevelDB
directory=activemq-data
replicas=3
bind=tcp://0.0.0.0:0
zkAddress=queue1:2181,queue2:2181,queue3:2181
