[
https://issues.apache.org/jira/browse/AMQ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503824#comment-13503824
]
Adrian Lisenberg commented on AMQ-4183:
---------------------------------------
If you don't set those system properties and still use long queue names, then
there is no warning or error alerting those queues will disappear after broker
restart. One solution would be controlling the length of queue names while
creating them and verifying against MaximumDirNameLength and
MaximumFileNameLength.
adrian
> AMQ 5.7 lost long queue names with filteredKahaDB
> -------------------------------------------------
>
> Key: AMQ-4183
> URL: https://issues.apache.org/jira/browse/AMQ-4183
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.7.0
> Environment: Linux, AMQ 5.7, KahaDB, filteredKahaDB,
> perDestination="true", long queueNames.
> Reporter: Adrian Lisenberg
> Priority: Minor
>
> Using AMQ 5.7 with filteredKahaDB and perDestination="true". I send
> persistent messages to a queue with a long name (more than 60 chars in the
> name). After broker restart this queue is not there anymore.
> It seems that kahadb is generating a truncated directory for that queue. The
> directory name is missing first letters. For short queue names, directory
> start with something like "queue#3a#2f#2f....", but for long queue names
> directory start with "#2f#2f...".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
