[
https://issues.apache.org/jira/browse/AMQ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-4183.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.8.0
Assignee: Timothy Bish
Added a warning to inform of name truncation in mKahaDB when filenames exceed
the system property value
> 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
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.8.0
>
>
> 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
