activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (AMQ-1663) Problem in Kaha persistence with file name lengths and collisions during persistence
Date Mon, 14 Apr 2008 16:00:43 GMT

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

Rob Davies reassigned AMQ-1663:
-------------------------------

    Assignee: Rob Davies

> Problem in Kaha persistence with file name lengths and collisions during persistence
> ------------------------------------------------------------------------------------
>
>                 Key: AMQ-1663
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1663
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>         Environment: Solaris 10, JDK 1.6
>            Reporter: Kevin Yaussy
>            Assignee: Rob Davies
>            Priority: Blocker
>
> The management of file names within Kaha persistence is such that it may create a file
with a name that ends up colliding with a file meant for a different, but very close, topic
name.  The file names are ultimately managed by org/apache/activemq/util/IOHelper.java, which
will trim the file name down to a maximum file name size, default of 64.  With sufficiently
large topic names, it is possible to create a collision with this scheme.  Ours is large enough,
that even if I push the max to 200 (attempting to stay under the 256 max length in Solaris),
I can still get a collision.
> What this results in is modifications to a file for two different items and/or consumers,
which causes corruption and errors.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message