kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KYLIN-3556) Interned string should not be used as lock object
Date Mon, 01 Oct 2018 16:52:00 GMT

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

Ted Yu updated KYLIN-3556:
--------------------------
    Description: 
In JDBCResourceDAO :

{code}
            public void execute(Connection connection) throws SQLException {
                synchronized (resPath.intern()) {
{code}
Locking on an interned string can cause unexpected locking collisions with other part of code.

  was:
In JDBCResourceDAO :
{code}
            public void execute(Connection connection) throws SQLException {
                synchronized (resPath.intern()) {
{code}
Locking on an interned string can cause unexpected locking collisions with other part of code.


> Interned string should not be used as lock object
> -------------------------------------------------
>
>                 Key: KYLIN-3556
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3556
>             Project: Kylin
>          Issue Type: Bug
>          Components: Metadata
>    Affects Versions: v2.5.0
>            Reporter: Ted Yu
>            Assignee:  Kaige Liu
>            Priority: Minor
>             Fix For: v2.5.1
>
>
> In JDBCResourceDAO :
> {code}
>             public void execute(Connection connection) throws SQLException {
>                 synchronized (resPath.intern()) {
> {code}
> Locking on an interned string can cause unexpected locking collisions with other part
of code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message