[jira] [Updated] (IGNITE-21690) ConfigurationNode has inconsistent synchronized access to fields `invalid` and `val`
[
https://issues.apache.org/jira/browse/IGNITE-21690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-21690:
-
Labels: ignite-3 ignite3 spotbugs (was: ignite3 spotbugs)
> ConfigurationNode has inconsistent synchronized access to fields `invalid`
> and `val`
>
>
> Key: IGNITE-21690
> URL: https://issues.apache.org/jira/browse/IGNITE-21690
> Project: Ignite
> Issue Type: Bug
>Reporter: Viacheslav Blinov
>Priority: Major
> Labels: ignite-3, ignite3, spotbugs
>
> Issue detected by SpotBugs but is also highlighted by Idea inspection.
> Specifically the warning reported is:
> {noformat}
> M M IS2_INCONSISTENT_SYNC IS: Inconsistent synchronization of
> org.apache.ignite.internal.configuration.ConfigurationNode.invalid; locked
> 66% of time Unsynchronized access at ConfigurationNode.java:[line
> 138]{noformat}
> {noformat}
> M M IS2_INCONSISTENT_SYNC IS: Inconsistent synchronization of
> org.apache.ignite.internal.configuration.ConfigurationNode.val; locked 60% of
> time Unsynchronized access at ConfigurationNode.java:[line 145]{noformat}
> Fields `val` and `invalid` are accessed in both synchronized and
> unsynchronized fashion. This can be a source of hard to catch bug.
> Investigate whenever this is a false-positive and we should suppress it, or
> we should make a proper fix.
> At the result of investigation corresponding TODO should be removed in
> spotbugs-excludes.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21690) ConfigurationNode has inconsistent synchronized access to fields `invalid` and `val`
[
https://issues.apache.org/jira/browse/IGNITE-21690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-21690:
-
Labels: ignite-3 spotbugs (was: ignite-3 ignite3 spotbugs)
> ConfigurationNode has inconsistent synchronized access to fields `invalid`
> and `val`
>
>
> Key: IGNITE-21690
> URL: https://issues.apache.org/jira/browse/IGNITE-21690
> Project: Ignite
> Issue Type: Bug
>Reporter: Viacheslav Blinov
>Priority: Major
> Labels: ignite-3, spotbugs
>
> Issue detected by SpotBugs but is also highlighted by Idea inspection.
> Specifically the warning reported is:
> {noformat}
> M M IS2_INCONSISTENT_SYNC IS: Inconsistent synchronization of
> org.apache.ignite.internal.configuration.ConfigurationNode.invalid; locked
> 66% of time Unsynchronized access at ConfigurationNode.java:[line
> 138]{noformat}
> {noformat}
> M M IS2_INCONSISTENT_SYNC IS: Inconsistent synchronization of
> org.apache.ignite.internal.configuration.ConfigurationNode.val; locked 60% of
> time Unsynchronized access at ConfigurationNode.java:[line 145]{noformat}
> Fields `val` and `invalid` are accessed in both synchronized and
> unsynchronized fashion. This can be a source of hard to catch bug.
> Investigate whenever this is a false-positive and we should suppress it, or
> we should make a proper fix.
> At the result of investigation corresponding TODO should be removed in
> spotbugs-excludes.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21690) ConfigurationNode has inconsistent synchronized access to fields `invalid` and `val`
[
https://issues.apache.org/jira/browse/IGNITE-21690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viacheslav Blinov updated IGNITE-21690:
---
Labels: ignite3 spotbugs (was: ignite3)
> ConfigurationNode has inconsistent synchronized access to fields `invalid`
> and `val`
>
>
> Key: IGNITE-21690
> URL: https://issues.apache.org/jira/browse/IGNITE-21690
> Project: Ignite
> Issue Type: Bug
>Reporter: Viacheslav Blinov
>Priority: Major
> Labels: ignite3, spotbugs
>
> Issue detected by SpotBugs but is also highlighted by Idea inspection.
> Specifically the warning reported is:
> {noformat}
> M M IS2_INCONSISTENT_SYNC IS: Inconsistent synchronization of
> org.apache.ignite.internal.configuration.ConfigurationNode.invalid; locked
> 66% of time Unsynchronized access at ConfigurationNode.java:[line
> 138]{noformat}
> {noformat}
> M M IS2_INCONSISTENT_SYNC IS: Inconsistent synchronization of
> org.apache.ignite.internal.configuration.ConfigurationNode.val; locked 60% of
> time Unsynchronized access at ConfigurationNode.java:[line 145]{noformat}
> Fields `val` and `invalid` are accessed in both synchronized and
> unsynchronized fashion. This can be a source of hard to catch bug.
> Investigate whenever this is a false-positive and we should suppress it, or
> we should make a proper fix.
> At the result of investigation corresponding TODO should be removed in
> spotbugs-excludes.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21690) ConfigurationNode has inconsistent synchronized access to fields `invalid` and `val`
[
https://issues.apache.org/jira/browse/IGNITE-21690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viacheslav Blinov updated IGNITE-21690:
---
Labels: ignite3 (was: )
> ConfigurationNode has inconsistent synchronized access to fields `invalid`
> and `val`
>
>
> Key: IGNITE-21690
> URL: https://issues.apache.org/jira/browse/IGNITE-21690
> Project: Ignite
> Issue Type: Bug
>Reporter: Viacheslav Blinov
>Priority: Major
> Labels: ignite3
>
> Issue detected by SpotBugs but is also highlighted by Idea inspection.
> Specifically the warning reported is:
> {noformat}
> M M IS2_INCONSISTENT_SYNC IS: Inconsistent synchronization of
> org.apache.ignite.internal.configuration.ConfigurationNode.invalid; locked
> 66% of time Unsynchronized access at ConfigurationNode.java:[line
> 138]{noformat}
> {noformat}
> M M IS2_INCONSISTENT_SYNC IS: Inconsistent synchronization of
> org.apache.ignite.internal.configuration.ConfigurationNode.val; locked 60% of
> time Unsynchronized access at ConfigurationNode.java:[line 145]{noformat}
> Fields `val` and `invalid` are accessed in both synchronized and
> unsynchronized fashion. This can be a source of hard to catch bug.
> Investigate whenever this is a false-positive and we should suppress it, or
> we should make a proper fix.
> At the result of investigation corresponding TODO should be removed in
> spotbugs-excludes.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21690) ConfigurationNode has inconsistent synchronized access to fields `invalid` and `val`
[
https://issues.apache.org/jira/browse/IGNITE-21690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viacheslav Blinov updated IGNITE-21690:
---
Issue Type: Bug (was: Task)
> ConfigurationNode has inconsistent synchronized access to fields `invalid`
> and `val`
>
>
> Key: IGNITE-21690
> URL: https://issues.apache.org/jira/browse/IGNITE-21690
> Project: Ignite
> Issue Type: Bug
>Reporter: Viacheslav Blinov
>Priority: Major
>
> Issue detected by SpotBugs but is also highlighted by Idea inspection.
> Specifically the warning reported is:
> {noformat}
> M M IS2_INCONSISTENT_SYNC IS: Inconsistent synchronization of
> org.apache.ignite.internal.configuration.ConfigurationNode.invalid; locked
> 66% of time Unsynchronized access at ConfigurationNode.java:[line
> 138]{noformat}
> {noformat}
> M M IS2_INCONSISTENT_SYNC IS: Inconsistent synchronization of
> org.apache.ignite.internal.configuration.ConfigurationNode.val; locked 60% of
> time Unsynchronized access at ConfigurationNode.java:[line 145]{noformat}
> Fields `val` and `invalid` are accessed in both synchronized and
> unsynchronized fashion. This can be a source of hard to catch bug.
> Investigate whenever this is a false-positive and we should suppress it, or
> we should make a proper fix.
> At the result of investigation corresponding TODO should be removed in
> spotbugs-excludes.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
