mKahaDB with perDestination=true creates cryptic directory names on the file system.
Issue
When using the mKahaDB persistence adapter and configuring it to map every destination to its own KahaDB instance with perDestination="true",
the directories created for each destination contain cryptic characters such as #3a#2f#2f.
E.g. we see a directory called queue3a#2f#2ftest1.
We would expect to see directories without these strange characters.
Is there a way to configure this behaviour?
Environment
- JBoss A-MQ 6.x
- Apache ActiveMQ 5.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
