[jira] [Updated] (AMQ-4183) AMQ 5.7 lost long queue names with filteredKahaDB

["Adrian Lisenberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrian Lisenberg updated AMQ-4183:
----------------------------------

    Priority: Minor  (was: Blocker)

Setting system properties MaximumDirNameLength (defaults to 200) and MaximumFileNameLength (defaults to 64) to a higher value solved the problem. 
                
> 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