[jira] [Updated] (IGNITE-11738) Incorrect check ObjectInput.available() in CacheMetricsSnapshot

2019-04-12 Thread Dmitriy Govorukhin (JIRA)


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

Dmitriy Govorukhin updated IGNITE-11738:

Description: 
CacheMetricsSnapshot.readExternal
{code}
 // 11 long and 5 float values give 108 bytes in total.
if (in.available() >= 108) {
entryProcessorPuts = in.readLong();
entryProcessorAverageInvocationTime = in.readFloat();
entryProcessorInvocations = in.readLong();
entryProcessorMaxInvocationTime = in.readFloat();
entryProcessorMinInvocationTime = in.readFloat();
entryProcessorReadOnlyInvocations = in.readLong();
entryProcessorHitPercentage = in.readFloat();
entryProcessorHits = in.readLong();
entryProcessorMisses = in.readLong();
entryProcessorMissPercentage = in.readFloat();
entryProcessorRemovals = in.readLong();
}
{code}

Here we have 6 long variables but not an 11.

  was:
{code}
 // 11 long and 5 float values give 108 bytes in total.
if (in.available() >= 108) {
entryProcessorPuts = in.readLong();
entryProcessorAverageInvocationTime = in.readFloat();
entryProcessorInvocations = in.readLong();
entryProcessorMaxInvocationTime = in.readFloat();
entryProcessorMinInvocationTime = in.readFloat();
entryProcessorReadOnlyInvocations = in.readLong();
entryProcessorHitPercentage = in.readFloat();
entryProcessorHits = in.readLong();
entryProcessorMisses = in.readLong();
entryProcessorMissPercentage = in.readFloat();
entryProcessorRemovals = in.readLong();
}
{code}

Here we have 6 long variables but not an 11.


> Incorrect check  ObjectInput.available() in CacheMetricsSnapshot
> 
>
> Key: IGNITE-11738
> URL: https://issues.apache.org/jira/browse/IGNITE-11738
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>
> CacheMetricsSnapshot.readExternal
> {code}
>  // 11 long and 5 float values give 108 bytes in total.
> if (in.available() >= 108) {
> entryProcessorPuts = in.readLong();
> entryProcessorAverageInvocationTime = in.readFloat();
> entryProcessorInvocations = in.readLong();
> entryProcessorMaxInvocationTime = in.readFloat();
> entryProcessorMinInvocationTime = in.readFloat();
> entryProcessorReadOnlyInvocations = in.readLong();
> entryProcessorHitPercentage = in.readFloat();
> entryProcessorHits = in.readLong();
> entryProcessorMisses = in.readLong();
> entryProcessorMissPercentage = in.readFloat();
> entryProcessorRemovals = in.readLong();
> }
> {code}
> Here we have 6 long variables but not an 11.



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


[jira] [Updated] (IGNITE-11738) Incorrect check ObjectInput.available() in CacheMetricsSnapshot

2019-04-12 Thread Dmitriy Govorukhin (JIRA)


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

Dmitriy Govorukhin updated IGNITE-11738:

Description: 
{code}
 // 11 long and 5 float values give 108 bytes in total.
if (in.available() >= 108) {
entryProcessorPuts = in.readLong();
entryProcessorAverageInvocationTime = in.readFloat();
entryProcessorInvocations = in.readLong();
entryProcessorMaxInvocationTime = in.readFloat();
entryProcessorMinInvocationTime = in.readFloat();
entryProcessorReadOnlyInvocations = in.readLong();
entryProcessorHitPercentage = in.readFloat();
entryProcessorHits = in.readLong();
entryProcessorMisses = in.readLong();
entryProcessorMissPercentage = in.readFloat();
entryProcessorRemovals = in.readLong();
}
{code}

Here we have 6 long variables but not an 11.

  was:
{code}
 // 11 long and 5 float values give 108 bytes in total.
if (in.available() >= 108) {
entryProcessorPuts = in.readLong();
entryProcessorAverageInvocationTime = in.readFloat();
entryProcessorInvocations = in.readLong();
entryProcessorMaxInvocationTime = in.readFloat();
entryProcessorMinInvocationTime = in.readFloat();
entryProcessorReadOnlyInvocations = in.readLong();
entryProcessorHitPercentage = in.readFloat();
entryProcessorHits = in.readLong();
entryProcessorMisses = in.readLong();
entryProcessorMissPercentage = in.readFloat();
entryProcessorRemovals = in.readLong();
}
{code}

Here we have 6 long but not an 11.


> Incorrect check  ObjectInput.available() in CacheMetricsSnapshot
> 
>
> Key: IGNITE-11738
> URL: https://issues.apache.org/jira/browse/IGNITE-11738
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>
> {code}
>  // 11 long and 5 float values give 108 bytes in total.
> if (in.available() >= 108) {
> entryProcessorPuts = in.readLong();
> entryProcessorAverageInvocationTime = in.readFloat();
> entryProcessorInvocations = in.readLong();
> entryProcessorMaxInvocationTime = in.readFloat();
> entryProcessorMinInvocationTime = in.readFloat();
> entryProcessorReadOnlyInvocations = in.readLong();
> entryProcessorHitPercentage = in.readFloat();
> entryProcessorHits = in.readLong();
> entryProcessorMisses = in.readLong();
> entryProcessorMissPercentage = in.readFloat();
> entryProcessorRemovals = in.readLong();
> }
> {code}
> Here we have 6 long variables but not an 11.



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


[jira] [Updated] (IGNITE-11738) Incorrect check ObjectInput.available() in CacheMetricsSnapshot

2019-04-12 Thread Dmitriy Govorukhin (JIRA)


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

Dmitriy Govorukhin updated IGNITE-11738:

Description: 
{code}
 // 11 long and 5 float values give 108 bytes in total.
if (in.available() >= 108) {
entryProcessorPuts = in.readLong();
entryProcessorAverageInvocationTime = in.readFloat();
entryProcessorInvocations = in.readLong();
entryProcessorMaxInvocationTime = in.readFloat();
entryProcessorMinInvocationTime = in.readFloat();
entryProcessorReadOnlyInvocations = in.readLong();
entryProcessorHitPercentage = in.readFloat();
entryProcessorHits = in.readLong();
entryProcessorMisses = in.readLong();
entryProcessorMissPercentage = in.readFloat();
entryProcessorRemovals = in.readLong();
}
{code}

There we have 6 long but not a 11.

> Incorrect check  ObjectInput.available() in CacheMetricsSnapshot
> 
>
> Key: IGNITE-11738
> URL: https://issues.apache.org/jira/browse/IGNITE-11738
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>
> {code}
>  // 11 long and 5 float values give 108 bytes in total.
> if (in.available() >= 108) {
> entryProcessorPuts = in.readLong();
> entryProcessorAverageInvocationTime = in.readFloat();
> entryProcessorInvocations = in.readLong();
> entryProcessorMaxInvocationTime = in.readFloat();
> entryProcessorMinInvocationTime = in.readFloat();
> entryProcessorReadOnlyInvocations = in.readLong();
> entryProcessorHitPercentage = in.readFloat();
> entryProcessorHits = in.readLong();
> entryProcessorMisses = in.readLong();
> entryProcessorMissPercentage = in.readFloat();
> entryProcessorRemovals = in.readLong();
> }
> {code}
> There we have 6 long but not a 11.



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


[jira] [Updated] (IGNITE-11738) Incorrect check ObjectInput.available() in CacheMetricsSnapshot

2019-04-12 Thread Dmitriy Govorukhin (JIRA)


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

Dmitriy Govorukhin updated IGNITE-11738:

Description: 
{code}
 // 11 long and 5 float values give 108 bytes in total.
if (in.available() >= 108) {
entryProcessorPuts = in.readLong();
entryProcessorAverageInvocationTime = in.readFloat();
entryProcessorInvocations = in.readLong();
entryProcessorMaxInvocationTime = in.readFloat();
entryProcessorMinInvocationTime = in.readFloat();
entryProcessorReadOnlyInvocations = in.readLong();
entryProcessorHitPercentage = in.readFloat();
entryProcessorHits = in.readLong();
entryProcessorMisses = in.readLong();
entryProcessorMissPercentage = in.readFloat();
entryProcessorRemovals = in.readLong();
}
{code}

Here we have 6 long but not an 11.

  was:
{code}
 // 11 long and 5 float values give 108 bytes in total.
if (in.available() >= 108) {
entryProcessorPuts = in.readLong();
entryProcessorAverageInvocationTime = in.readFloat();
entryProcessorInvocations = in.readLong();
entryProcessorMaxInvocationTime = in.readFloat();
entryProcessorMinInvocationTime = in.readFloat();
entryProcessorReadOnlyInvocations = in.readLong();
entryProcessorHitPercentage = in.readFloat();
entryProcessorHits = in.readLong();
entryProcessorMisses = in.readLong();
entryProcessorMissPercentage = in.readFloat();
entryProcessorRemovals = in.readLong();
}
{code}

There we have 6 long but not a 11.


> Incorrect check  ObjectInput.available() in CacheMetricsSnapshot
> 
>
> Key: IGNITE-11738
> URL: https://issues.apache.org/jira/browse/IGNITE-11738
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>
> {code}
>  // 11 long and 5 float values give 108 bytes in total.
> if (in.available() >= 108) {
> entryProcessorPuts = in.readLong();
> entryProcessorAverageInvocationTime = in.readFloat();
> entryProcessorInvocations = in.readLong();
> entryProcessorMaxInvocationTime = in.readFloat();
> entryProcessorMinInvocationTime = in.readFloat();
> entryProcessorReadOnlyInvocations = in.readLong();
> entryProcessorHitPercentage = in.readFloat();
> entryProcessorHits = in.readLong();
> entryProcessorMisses = in.readLong();
> entryProcessorMissPercentage = in.readFloat();
> entryProcessorRemovals = in.readLong();
> }
> {code}
> Here we have 6 long but not an 11.



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


[jira] [Updated] (IGNITE-11738) Incorrect check ObjectInput.available() in CacheMetricsSnapshot

2019-04-12 Thread Dmitriy Govorukhin (JIRA)


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

Dmitriy Govorukhin updated IGNITE-11738:

Fix Version/s: 2.8

> Incorrect check  ObjectInput.available() in CacheMetricsSnapshot
> 
>
> Key: IGNITE-11738
> URL: https://issues.apache.org/jira/browse/IGNITE-11738
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>




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


[jira] [Updated] (IGNITE-11738) Incorrect check ObjectInput.available() in CacheMetricsSnapshot

2019-04-12 Thread Dmitriy Govorukhin (JIRA)


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

Dmitriy Govorukhin updated IGNITE-11738:

Ignite Flags:   (was: Docs Required)

> Incorrect check  ObjectInput.available() in CacheMetricsSnapshot
> 
>
> Key: IGNITE-11738
> URL: https://issues.apache.org/jira/browse/IGNITE-11738
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>




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