May 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (HRJS-10) Buffers and String offsets not updated when writing length

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-10?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño resolved HRJS-10. ---------------------------------- Resolution: Done > Buffers and String offsets not updated when writing length > ---------------------------------------------------------- > > Key: HRJS-10 > URL: https://issues.jboss.org/browse/HRJS-10 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.2.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 0.3.0 > > > When encoding a String, there's a chance that there's a need to extend the size of the buffer if the String won't fit the buffer. However, when calculating whether extending is required, only the String size is counted without counting the num bytes counter at the start. As a result of that, a String might end up being truncated and lead to operation hanging up. > This happened in executing a Script where the number of bytes sent as message ID was bigger than 27 and the script name being executed was exactly 23 characters. > The actual problem is that after writing the length of String or Buffers, the offset of the underlying buffer is not being updated and hence it could end up truncating data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6079) Searching nodes in management console by IP address doesn't work

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6079?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-6079: ---------------------------------- Assignee: Pedro Zapata (was: Vladimir Blagojevic) > Searching nodes in management console by IP address doesn't work > ---------------------------------------------------------------- > > Key: ISPN-6079 > URL: https://issues.jboss.org/browse/ISPN-6079 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Pedro Zapata > > Searching nodes by IP address doesn't work. e.g. 127.0.0.1 > Result: No nodes are matched. > Note: searching by part of address - "127.0" works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6079) Searching nodes in management console by IP address doesn't work

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6079?page=com.atlassian.jira.plugin.... ] Work on ISPN-6079 started by Pedro Zapata. ------------------------------------------ > Searching nodes in management console by IP address doesn't work > ---------------------------------------------------------------- > > Key: ISPN-6079 > URL: https://issues.jboss.org/browse/ISPN-6079 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Pedro Zapata > > Searching nodes by IP address doesn't work. e.g. 127.0.0.1 > Result: No nodes are matched. > Note: searching by part of address - "127.0" works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6118) CacheNotifierImplInitialTransferDistTest random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6118?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-6118. -------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) Resolution: Done Fixed with ISPN-6556 > CacheNotifierImplInitialTransferDistTest random failures > -------------------------------------------------------- > > Key: ISPN-6118 > URL: https://issues.jboss.org/browse/ISPN-6118 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.0.0.Alpha2 > > > The failures are probably related to the default consistent hash factory change. > {noformat} > 18:54:56,255 ERROR (testng-CacheNotifierImplInitialTransferDistTest:) [UnitTestTestNGListener] Test testCreateAfterIterationBeganAndSegmentNotCompleteValueNonOwnerClustered(org.infinispan.notifications.cachelistener.CacheNotifierImplInitialTransferDistTest) failed. > java.util.concurrent.TimeoutException: Timed out waiting for event pre_complete_segment_invoked > at org.infinispan.test.fwk.CheckPoint.awaitStrict(CheckPoint.java:43) ~[test-classes/:?] > at org.infinispan.test.fwk.CheckPoint.awaitStrict(CheckPoint.java:33) ~[test-classes/:?] > at org.infinispan.notifications.cachelistener.CacheNotifierImplInitialTransferDistTest.testIterationBeganAndSegmentNotComplete(CacheNotifierImplInitialTransferDistTest.java:519) ~[test-classes/:?] > at org.infinispan.notifications.cachelistener.CacheNotifierImplInitialTransferDistTest.testCreateAfterIterationBeganAndSegmentNotCompleteValueNonOwnerClustered(CacheNotifierImplInitialTransferDistTest.java:622) ~[test-classes/:?] > {noformat} > {noformat} > 18:55:06,637 ERROR (testng-CacheNotifierImplInitialTransferDistTest:) [UnitTestTestNGListener] Test testCreateAfterIterationBeganAndSegmentNotCompleteValueOwnerClustered(org.infinispan.notifications.cachelistener.CacheNotifierImplInitialTransferDistTest) failed. > java.util.concurrent.TimeoutException: Timed out waiting for event pre_complete_segment_invoked > at org.infinispan.test.fwk.CheckPoint.awaitStrict(CheckPoint.java:43) ~[test-classes/:?] > at org.infinispan.test.fwk.CheckPoint.awaitStrict(CheckPoint.java:33) ~[test-classes/:?] > at org.infinispan.notifications.cachelistener.CacheNotifierImplInitialTransferDistTest.testIterationBeganAndSegmentNotComplete(CacheNotifierImplInitialTransferDistTest.java:519) ~[test-classes/:?] > at org.infinispan.notifications.cachelistener.CacheNotifierImplInitialTransferDistTest.testCreateAfterIterationBeganAndSegmentNotCompleteValueOwnerClustered(CacheNotifierImplInitialTransferDistTest.java:633) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (HRJS-10) Buffers and String offsets not updated when writing length

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-10?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-10: --------------------------------- Description: When encoding a String, there's a chance that there's a need to extend the size of the buffer if the String won't fit the buffer. However, when calculating whether extending is required, only the String size is counted without counting the num bytes counter at the start. As a result of that, a String might end up being truncated and lead to operation hanging up. This happened in executing a Script where the number of bytes sent as message ID was bigger than 27 and the script name being executed was exactly 23 characters. The actual problem is that after writing the length of String or Buffers, the offset of the underlying buffer is not being updated and hence it could end up truncating data. was: When encoding a String, there's a chance that there's a need to extend the size of the buffer if the String won't fit the buffer. However, when calculating whether extending is required, only the String size is counted without counting the num bytes counter at the start. As a result of that, a String might end up being truncated and lead to operation hanging up. This happened in executing a Script where the number of bytes sent as message ID was bigger than 27 and the script name being executed was exactly 23 characters. > Buffers and String offsets not updated when writing length > ---------------------------------------------------------- > > Key: HRJS-10 > URL: https://issues.jboss.org/browse/HRJS-10 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.2.0 > Reporter: Galder Zamarreño > Priority: Critical > Fix For: 0.3.0 > > > When encoding a String, there's a chance that there's a need to extend the size of the buffer if the String won't fit the buffer. However, when calculating whether extending is required, only the String size is counted without counting the num bytes counter at the start. As a result of that, a String might end up being truncated and lead to operation hanging up. > This happened in executing a Script where the number of bytes sent as message ID was bigger than 27 and the script name being executed was exactly 23 characters. > The actual problem is that after writing the length of String or Buffers, the offset of the underlying buffer is not being updated and hence it could end up truncating data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (HRJS-10) Buffers and String offsets not updated when writing length

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-10?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-10: --------------------------------- Affects Version/s: 0.2.0 > Buffers and String offsets not updated when writing length > ---------------------------------------------------------- > > Key: HRJS-10 > URL: https://issues.jboss.org/browse/HRJS-10 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.2.0 > Reporter: Galder Zamarreño > Priority: Critical > Fix For: 0.3.0 > > > When encoding a String, there's a chance that there's a need to extend the size of the buffer if the String won't fit the buffer. However, when calculating whether extending is required, only the String size is counted without counting the num bytes counter at the start. As a result of that, a String might end up being truncated and lead to operation hanging up. > This happened in executing a Script where the number of bytes sent as message ID was bigger than 27 and the script name being executed was exactly 23 characters. > The actual problem is that after writing the length of String or Buffers, the offset of the underlying buffer is not being updated and hence it could end up truncating data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (HRJS-10) Buffers and String offsets not updated when writing length

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-10?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-10: --------------------------------- Status: Open (was: New) > Buffers and String offsets not updated when writing length > ---------------------------------------------------------- > > Key: HRJS-10 > URL: https://issues.jboss.org/browse/HRJS-10 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.2.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 0.3.0 > > > When encoding a String, there's a chance that there's a need to extend the size of the buffer if the String won't fit the buffer. However, when calculating whether extending is required, only the String size is counted without counting the num bytes counter at the start. As a result of that, a String might end up being truncated and lead to operation hanging up. > This happened in executing a Script where the number of bytes sent as message ID was bigger than 27 and the script name being executed was exactly 23 characters. > The actual problem is that after writing the length of String or Buffers, the offset of the underlying buffer is not being updated and hence it could end up truncating data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (HRJS-10) Buffers and String offsets not updated when writing length

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-10?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño reassigned HRJS-10: ------------------------------------ Assignee: Galder Zamarreño > Buffers and String offsets not updated when writing length > ---------------------------------------------------------- > > Key: HRJS-10 > URL: https://issues.jboss.org/browse/HRJS-10 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.2.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 0.3.0 > > > When encoding a String, there's a chance that there's a need to extend the size of the buffer if the String won't fit the buffer. However, when calculating whether extending is required, only the String size is counted without counting the num bytes counter at the start. As a result of that, a String might end up being truncated and lead to operation hanging up. > This happened in executing a Script where the number of bytes sent as message ID was bigger than 27 and the script name being executed was exactly 23 characters. > The actual problem is that after writing the length of String or Buffers, the offset of the underlying buffer is not being updated and hence it could end up truncating data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (HRJS-10) Buffers and String offsets not updated when writing length

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-10?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-10: --------------------------------- Fix Version/s: 0.3.0 > Buffers and String offsets not updated when writing length > ---------------------------------------------------------- > > Key: HRJS-10 > URL: https://issues.jboss.org/browse/HRJS-10 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.2.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 0.3.0 > > > When encoding a String, there's a chance that there's a need to extend the size of the buffer if the String won't fit the buffer. However, when calculating whether extending is required, only the String size is counted without counting the num bytes counter at the start. As a result of that, a String might end up being truncated and lead to operation hanging up. > This happened in executing a Script where the number of bytes sent as message ID was bigger than 27 and the script name being executed was exactly 23 characters. > The actual problem is that after writing the length of String or Buffers, the offset of the underlying buffer is not being updated and hence it could end up truncating data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (HRJS-10) Buffers and String offsets not updated when writing length

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-10?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-10: --------------------------------- Summary: Buffers and String offsets not updated when writing length (was: Buffer extension could lead to String truncation) > Buffers and String offsets not updated when writing length > ---------------------------------------------------------- > > Key: HRJS-10 > URL: https://issues.jboss.org/browse/HRJS-10 > Project: Infinispan Javascript client > Issue Type: Bug > Reporter: Galder Zamarreño > Priority: Critical > > When encoding a String, there's a chance that there's a need to extend the size of the buffer if the String won't fit the buffer. However, when calculating whether extending is required, only the String size is counted without counting the num bytes counter at the start. As a result of that, a String might end up being truncated and lead to operation hanging up. > This happened in executing a Script where the number of bytes sent as message ID was bigger than 27 and the script name being executed was exactly 23 characters. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2016