[jira] [Updated] (GEODE-2012) Test rolling stat archive after closing a resource instance
[ https://issues.apache.org/jira/browse/GEODE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2012: - Description: If a given ResourceType has no Resource instances at the same time that a statistics archive file is created by rolling, then the ResourceType is not written to the archive file. If a later Resource instance for that type is created, it will be written to the archive file without a ResourceType, effectively corrupting that file so that it cannot be read. Attempting to read the corrupted statistics archive file will result in a NullPointerException (GEODE-2013). Steps required to test this bug: 1) create resource instance of new type 2) sample so that resource instance and type are written to gfs 3) close resource instance so no instances exist of that type 4) sample 5) roll gfs archive 6) sample 7) create new resource instance of same type 8) sample 9) verify that resource instance and type were both written to gfs The resulting gfs archive file after #5 contains a resource instance with no corresponding resource type. Attempting to read the file in with StatArchiveReader will throw a NullPointerException (GEODE-2013). was: Need to test this scenario: 1) create resource instance of new type 2) sample so that resource instance and type are written to gfs 3) close resource instance so no instances exist of that type 4) sample 5) roll gfs archive 6) sample 7) create new resource instance of same type 8) sample 9) verify that resource instance and type were both written to gfs The resulting gfs archive file after #5 contains a resource instance with no corresponding resource type. Attempting to read the file in with StatArchiveReader will throw a NullPointerException (GEODE-2013). > Test rolling stat archive after closing a resource instance > --- > > Key: GEODE-2012 > URL: https://issues.apache.org/jira/browse/GEODE-2012 > Project: Geode > Issue Type: Bug > Components: statistics >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Kirk Lund > Fix For: 1.1.0-incubating > > > If a given ResourceType has no Resource instances at the same time that a > statistics archive file is created by rolling, then the ResourceType is not > written to the archive file. If a later Resource instance for that type is > created, it will be written to the archive file without a ResourceType, > effectively corrupting that file so that it cannot be read. > Attempting to read the corrupted statistics archive file will result in a > NullPointerException (GEODE-2013). > Steps required to test this bug: > 1) create resource instance of new type > 2) sample so that resource instance and type are written to gfs > 3) close resource instance so no instances exist of that type > 4) sample > 5) roll gfs archive > 6) sample > 7) create new resource instance of same type > 8) sample > 9) verify that resource instance and type were both written to gfs > The resulting gfs archive file after #5 contains a resource instance with no > corresponding resource type. Attempting to read the file in with > StatArchiveReader will throw a NullPointerException (GEODE-2013). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2012) Test rolling stat archive after closing a resource instance
[ https://issues.apache.org/jira/browse/GEODE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2012: - Issue Type: Bug (was: Test) > Test rolling stat archive after closing a resource instance > --- > > Key: GEODE-2012 > URL: https://issues.apache.org/jira/browse/GEODE-2012 > Project: Geode > Issue Type: Bug > Components: statistics >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Kirk Lund > Fix For: 1.1.0-incubating > > > Need to test this scenario: > 1) create resource instance of new type > 2) sample so that resource instance and type are written to gfs > 3) close resource instance so no instances exist of that type > 4) sample > 5) roll gfs archive > 6) sample > 7) create new resource instance of same type > 8) sample > 9) verify that resource instance and type were both written to gfs > The resulting gfs archive file after #5 contains a resource instance with no > corresponding resource type. Attempting to read the file in with > StatArchiveReader will throw a NullPointerException (GEODE-2013). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2012) Test rolling stat archive after closing a resource instance
[ https://issues.apache.org/jira/browse/GEODE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2012: - Description: Need to test this scenario: 1) create resource instance of new type 2) sample so that resource instance and type are written to gfs 3) close resource instance so no instances exist of that type 4) sample 5) roll gfs archive 6) sample 7) create new resource instance of same type 8) sample 9) verify that resource instance and type were both written to gfs The resulting gfs archive file after #5 contains a resource instance with no corresponding resource type. Attempting to read the file in with StatArchiveReader will throw a NullPointerException (GEODE-2013). was: Need to test this scenario: 1) create resource instance of new type 2) sample so that resource instance and type are written to gfs 3) close resource instance so no instances exist of that type 4) sample 5) roll gfs archive 6) sample 7) create new resource instance of same type 8) sample 9) verify that resource instance and type were both written to gfs > Test rolling stat archive after closing a resource instance > --- > > Key: GEODE-2012 > URL: https://issues.apache.org/jira/browse/GEODE-2012 > Project: Geode > Issue Type: Bug > Components: statistics >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Kirk Lund > Fix For: 1.1.0-incubating > > > Need to test this scenario: > 1) create resource instance of new type > 2) sample so that resource instance and type are written to gfs > 3) close resource instance so no instances exist of that type > 4) sample > 5) roll gfs archive > 6) sample > 7) create new resource instance of same type > 8) sample > 9) verify that resource instance and type were both written to gfs > The resulting gfs archive file after #5 contains a resource instance with no > corresponding resource type. Attempting to read the file in with > StatArchiveReader will throw a NullPointerException (GEODE-2013). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2012) Test rolling stat archive after closing a resource instance
[ https://issues.apache.org/jira/browse/GEODE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2012: - Issue Type: Test (was: Bug) > Test rolling stat archive after closing a resource instance > --- > > Key: GEODE-2012 > URL: https://issues.apache.org/jira/browse/GEODE-2012 > Project: Geode > Issue Type: Test > Components: statistics >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Kirk Lund > Fix For: 1.1.0-incubating > > > Need to test this scenario: > 1) create resource instance of new type > 2) sample so that resource instance and type are written to gfs > 3) close resource instance so no instances exist of that type > 4) sample > 5) roll gfs archive > 6) sample > 7) create new resource instance of same type > 8) sample > 9) verify that resource instance and type were both written to gfs > The resulting gfs archive file after #5 contains a resource instance with no > corresponding resource type. Attempting to read the file in with > StatArchiveReader will throw a NullPointerException (GEODE-2013). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2012) Test rolling stat archive after closing a resource instance
[ https://issues.apache.org/jira/browse/GEODE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2012: - Affects Version/s: 1.0.0-incubating > Test rolling stat archive after closing a resource instance > --- > > Key: GEODE-2012 > URL: https://issues.apache.org/jira/browse/GEODE-2012 > Project: Geode > Issue Type: Bug > Components: statistics >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Kirk Lund > Fix For: 1.1.0-incubating > > > Need to test this scenario: > 1) create resource instance of new type > 2) sample so that resource instance and type are written to gfs > 3) close resource instance so no instances exist of that type > 4) sample > 5) roll gfs archive > 6) sample > 7) create new resource instance of same type > 8) sample > 9) verify that resource instance and type were both written to gfs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2012) Test rolling stat archive after closing a resource instance
[ https://issues.apache.org/jira/browse/GEODE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2012: - Description: Need to test this scenario: 1) create resource instance of new type 2) sample so that resource instance and type are written to gfs 3) close resource instance so no instances exist of that type 4) sample 5) roll gfs archive 6) sample 7) create new resource instance of same type 8) sample 9) verify that resource instance and type were both written to gfs was: Need to test this scenario: 1) create resource instance of new type 2) sample so that resource instance and type are written to gfs 3) close resource instance so no instances exist of that type 4) sample 5) roll gfs archive 6) sample 7) create new resource instance of same type 8) sample 9) verify that resource instance and type were both written to gfs Ideal resource type to use for test is CacheClientProxy. > Test rolling stat archive after closing a resource instance > --- > > Key: GEODE-2012 > URL: https://issues.apache.org/jira/browse/GEODE-2012 > Project: Geode > Issue Type: Bug > Components: statistics >Reporter: Kirk Lund >Assignee: Kirk Lund > > Need to test this scenario: > 1) create resource instance of new type > 2) sample so that resource instance and type are written to gfs > 3) close resource instance so no instances exist of that type > 4) sample > 5) roll gfs archive > 6) sample > 7) create new resource instance of same type > 8) sample > 9) verify that resource instance and type were both written to gfs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
