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't expect the broker to be happy if you switch between KahaDB and mKahaDB using the same data directory (and the same files within it, more importantly). Unless your process for switching the KahaDB type already involved deleting the files in the data directory?
Tim Tim On Sat, Mar 21, 2020, 8:03 AM nexus <a...@mastersoft.lv> wrote: > Hello, > > Encountering following issue with network of brokers on Windows 10 / 64-bit > / ActiveMQ v5.15.12 > > Problem > > > Cannot re-establish duplex network connection on remote broker with > following error: > > > > Remote broker is configured to delete inactive destinations > <https://activemq.apache.org/delete-inactive-destinations.html> and uses > mKahaDB persistence adapters for different destinations ( Automatic Per > Destination Persistence Adapter <https://activemq.apache.org/kahadb> ). > > Same setup, but single kahaDB persistence adapter on remote broker is not > causing the issue. > > See attached files for detailed configuration and logs: > > * local-activemq.xml > <http://activemq.2283324.n4.nabble.com/file/t379838/local-activemq.xml> > * good-remote-activemq.xml > < > http://activemq.2283324.n4.nabble.com/file/t379838/good-remote-activemq.xml> > > * good-remote-wrapper.log > < > http://activemq.2283324.n4.nabble.com/file/t379838/good-remote-wrapper.log> > > * bad-remote-activemq.xml > < > http://activemq.2283324.n4.nabble.com/file/t379838/bad-remote-activemq.xml> > > * bad-remote-wrapper.log > <http://activemq.2283324.n4.nabble.com/file/t379838/bad-remote-wrapper.log> > > > Use case > > > Simulate network connection loss and then re-astablish duplex communication > after remote broker destinations were purged due to inactivity: > > 1. start remote broker > 2. start local broker > 3. destination queue created automatically on remote (active consumer from > local broker is also shown correctly in web-console) > 4. stop local broker > 5. wait for a while until destination is deleted on remote due to > inactivity > 6. start local broker again > > Results > > > GOOD: single kahaDB persistence adapter on remote broker > > > > > BAD: multiple kahaDb persistence adapters on remote broker with > perDestination="true" > > > > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
