uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-3663) UimaConterxt_ImplBase code to generate uniqueIdentifier may not be unique
Date Tue, 18 Mar 2014 19:20:45 GMT

    [ https://issues.apache.org/jira/browse/UIMA-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939675#comment-13939675

Marshall Schor commented on UIMA-3663:

fixed as part of commit of UIMA-3662

> UimaConterxt_ImplBase code to generate uniqueIdentifier may not be unique
> -------------------------------------------------------------------------
>                 Key: UIMA-3663
>                 URL: https://issues.apache.org/jira/browse/UIMA-3663
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.5.0SDK
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Trivial
>             Fix For: 2.5.1SDK
> Code in the construction of UimaConterxt_ImplBase calls UID() to get a unique id.  One
use is as a way to allow (for scaled-out apps) unique identification of otherwise similar
MBeans, using different mbean names. MBean names cannot have colons or dashes.  This code
removes those from the string value returned by UID().  This means that 2 different UIDs that
differ only in having some part have a minus sign, could be confused with another not having
this.  A small test case shows this can arise if > 32768 UIMA Contexts are created within
one millisecond.  While extremely unlikely, this is easily avoided, for example, by substituting
_ for the characters, rather than deleting them.

This message was sent by Atlassian JIRA

View raw message