I had forgotten you'd already submitted one. Thank you for doing that.
Tim
On Sat, Mar 28, 2020, 12:13 AM nexus wrote:
> I have already opened an issue AMQ-7453 with detailed description, logs and
> examples, please, take a look:
> https://issues.apache.org/jira/browse/AMQ-7453
>
>
>
> --
> Sen
I have already opened an issue AMQ-7453 with detailed description, logs and
examples, please, take a look:
https://issues.apache.org/jira/browse/AMQ-7453
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Thanks for testing that; it will help make sure that whoever works on a fix
focuses quickly on the right part of the code. Would you be able to submit
a bug in JIRA to capture the problem as you observed it? If you're able to
attach any config files that would make it easier to quickly reproduce th
> if you cycle the remote broker while the local one is down, do you get the
same behavior?
I've performed the test, there's no error after clean restart of the remote
broker, but the problem repeats whenever inactive destinations are purged
once again. So, I suppose, your assumption is right "it
What I meant was, if you cycle the remote broker while the local one is
down, do you get the same behavior? I'm trying to characterize whether the
problem is purely something in-memory on the remote broker, or whether the
problem is also in the content written to disk (and therefore the problem
per
> can you please submit a bug report for it in JIRA?
Done:
https://issues.apache.org/jira/projects/AMQ/issues/AMQ-7453
> whether the problem occurs if you cycle the remote broker between steps 5
> and 6
Steps 5. - 6. can be repeated multiple times -- problem persists.
--
Sent from: http://ac
This definitely sounds like a bug in the mKahaDB code, so can you please
submit a bug report for it in JIRA?
I'd be curious to know whether the problem occurs if you cycle the remote
broker between steps 5 and 6. If not, it's likely something in-memory that
represents an inconsistency between the
> Can you please provide a listing (ls -l) of the KahaDB data directory?
See details below aligned with use case.
> Also, can you please configure mKahaDB to point to a different (empty)
> directory rather than the same one that the normal KahaDB points to, and
> try again? I've never used mKahaDB
Can you please provide a listing (ls -l) of the KahaDB data directory?
Also, can you please configure mKahaDB to point to a different (empty)
directory rather than the same one that the normal KahaDB points to, and
try again? I've never used mKahaDB so I don't have direct experience, but I
wouldn'
