If the problem is still occurring with regular KahaDB, then KahaDB probably
isn't the problem. Can you share your full broker configuration, rather
than just snippets?
Tim
On Wed, Nov 20, 2019, 8:16 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
> Basically the same as you:
>
> <kahaDB directory="/path/nfs/kahadb"
> indexWriteBatchSize="1000"
> indexCacheSize="2000"
> journalMaxFileLength="32mb"
> checkForCorruptJournalFiles="false"
> maxAsyncJobs="5000"
> concurrentStoreAndDispatchQueues="true"
> concurrentStoreAndDispatchTopics="true"
> enableJournalDiskSyncs="true"
> enableIndexWriteAsync="true"/>
>
> Let me try with AMQP client.
>
> I just commented the Jira.
>
> Regards
> JB
>
> On 20/11/2019 15:49, Ashish Vaishno wrote:
> > Hello Tim,
> >
> > I have tried to change mkahadb to standard kahadb as well in my dev
> > environment. I still face the same issue.
> > <broker .... persistent="true">
> > <persistenceAdapter>
> > <kahaDB directory="${activemq.data}" journalMaxFileLength="32mb"/>
> > </persistenceAdapter>
> > </broker>
> > I will create a JIRA bug for the same.
> >
> > @JB would it be possible to share your config?
> >
> > Regards
> > Ashish
> >
> >
> >
> > --
> > Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
