July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3308) Change the tests' JGroups rejection policy to Discard

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3308?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3308: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/1959 > Change the tests' JGroups rejection policy to Discard > ----------------------------------------------------- > > Key: ISPN-3308 > URL: https://issues.jboss.org/browse/ISPN-3308 > Project: Infinispan > Issue Type: Task > Components: Test Suite > Affects Versions: 5.3.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 6.0.0.Alpha1 > > > The test suite uses the Run rejection policy for the Incoming and OOB thread pools, which can cause deadlocks: > https://github.com/infinispan/infinispan/pull/1921#issuecomment-19980504 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3311) Unmarshalling error switching from 5.2 to 5.3

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3311?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-3311: --------------------------------------- You think we can fix this? Infinispan 5.3.0.Final was released already, so I don't think we can change the binary format anymore? > Unmarshalling error switching from 5.2 to 5.3 > --------------------------------------------- > > Key: ISPN-3311 > URL: https://issues.jboss.org/browse/ISPN-3311 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > Error: > {code}Caused by: org.infinispan.CacheException: Type of data read is > unknown. Id=-2147482348 is not amongst known reader indexes. > at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222){code} > Full stacktrace: https://gist.github.com/galderz/770679223e02f5b211f8 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3311) Unmarshalling error switching from 5.2 to 5.3

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-3311: -------------------------------------- Summary: Unmarshalling error switching from 5.2 to 5.3 Key: ISPN-3311 URL: https://issues.jboss.org/browse/ISPN-3311 Project: Infinispan Issue Type: Bug Affects Versions: 5.3.0.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 6.0.0.Alpha2, 6.0.0.Final Error: {code}Caused by: org.infinispan.CacheException: Type of data read is unknown. Id=-2147482348 is not amongst known reader indexes. at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222){code} Full stacktrace: https://gist.github.com/galderz/770679223e02f5b211f8 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3234) Upgrade to JCache 0.8

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3234?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3234: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/1961 > Upgrade to JCache 0.8 > --------------------- > > Key: ISPN-3234 > URL: https://issues.jboss.org/browse/ISPN-3234 > Project: Infinispan > Issue Type: Component Upgrade > Components: JCache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > When next JCache version is released, upgrade and re-enable the following TCK tests which have been disabled in ISPN-3213: > {code}org.jsr107.tck.CacheStatisticsTest#testCacheStatistics > org.jsr107.tck.CacheStatisticsTest#testCacheStatisticsInvokeEntryProcessorGet > org.jsr107.tck.CacheStatisticsTest#testCacheStatisticsInvokeEntryProcessorCreate > org.jsr107.tck.CacheStatisticsTest#testCacheStatisticsInvokeEntryProcessorRemove > org.jsr107.tck.CacheStatisticsTest#testIterateAndRemove > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3234) Upgrade to JCache 0.8

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3234?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3234: ----------------------------------- Fix Version/s: 6.0.0.Alpha1 > Upgrade to JCache 0.8 > --------------------- > > Key: ISPN-3234 > URL: https://issues.jboss.org/browse/ISPN-3234 > Project: Infinispan > Issue Type: Component Upgrade > Components: JCache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > When next JCache version is released, upgrade and re-enable the following TCK tests which have been disabled in ISPN-3213: > {code}org.jsr107.tck.CacheStatisticsTest#testCacheStatistics > org.jsr107.tck.CacheStatisticsTest#testCacheStatisticsInvokeEntryProcessorGet > org.jsr107.tck.CacheStatisticsTest#testCacheStatisticsInvokeEntryProcessorCreate > org.jsr107.tck.CacheStatisticsTest#testCacheStatisticsInvokeEntryProcessorRemove > org.jsr107.tck.CacheStatisticsTest#testIterateAndRemove > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3234) Upgrade to JCache 0.8

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3234?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3234: ----------------------------------- Summary: Upgrade to JCache 0.8 (was: Upgrade to JCache 0.x) > Upgrade to JCache 0.8 > --------------------- > > Key: ISPN-3234 > URL: https://issues.jboss.org/browse/ISPN-3234 > Project: Infinispan > Issue Type: Component Upgrade > Components: JCache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > When next JCache version is released, upgrade and re-enable the following TCK tests which have been disabled in ISPN-3213: > {code}org.jsr107.tck.CacheStatisticsTest#testCacheStatistics > org.jsr107.tck.CacheStatisticsTest#testCacheStatisticsInvokeEntryProcessorGet > org.jsr107.tck.CacheStatisticsTest#testCacheStatisticsInvokeEntryProcessorCreate > org.jsr107.tck.CacheStatisticsTest#testCacheStatisticsInvokeEntryProcessorRemove > org.jsr107.tck.CacheStatisticsTest#testIterateAndRemove > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3289) PutForExternalRead should only write the value on the originator once

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3289?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3289: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > PutForExternalRead should only write the value on the originator once > --------------------------------------------------------------------- > > Key: ISPN-3289 > URL: https://issues.jboss.org/browse/ISPN-3289 > Project: Infinispan > Issue Type: Bug > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 6.0.0.Final > > > putForExternalRead behaves as an asynchronous, non-transactional write operation even in tx caches, and as such it uses lock delegation. > Let's say we have a cluster with two nodes: [A, B], and a key k with owners(k) = [A, B]. > If B is the originator of a PFER(k, v) operation, the command is first executed locally on B, then it is invoked asynchronously on the primary owner A, and A invokes it asynchronously on B (because of the FORCE_ASNCHRONOUS flag). > For regular non-tx write operations, the entry k=v is only written to the data container on B during the second invocation. For PFER, however, the entry is written twice: once during each execution. > This causes random failures in {{PutForExternalRead*Test.testNoOpWhenKeyPresent}}, because the test assumes that the PFER finished once the entry was written once on each owner. > Arguably the fact that the primary owner forwards the PFER command asynchronously is also a problem, because the put command will write the value on B without holding a lock on A, the primary owner. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3308) Change the tests' JGroups rejection policy to Discard

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3308?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-3308. --------------------------------- Resolution: Done > Change the tests' JGroups rejection policy to Discard > ----------------------------------------------------- > > Key: ISPN-3308 > URL: https://issues.jboss.org/browse/ISPN-3308 > Project: Infinispan > Issue Type: Task > Components: Test Suite > Affects Versions: 5.3.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 6.0.0.Alpha1 > > > The test suite uses the Run rejection policy for the Incoming and OOB thread pools, which can cause deadlocks: > https://github.com/infinispan/infinispan/pull/1921#issuecomment-19980504 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3170) create a Metadata store

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3170?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3170: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > create a Metadata store > ----------------------- > > Key: ISPN-3170 > URL: https://issues.jboss.org/browse/ISPN-3170 > Project: Infinispan > Issue Type: Sub-task > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Blocker > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > See #3: https://community.jboss.org/wiki/QueryingDesignInInfinispan > This is intended as a general purpose internal component to allow sharing information between the nodes in the cluster. > E.g.: > - protobuf files, once uploaded to a node, would need to be made available to all the nodes in the cluster > - indexing information. An index is to be defined on onde node but this information (what's indexed) needs to be made available to all the nodes in the cluster -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3310) Refactor the common cache API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3310?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3310: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1960 > Refactor the common cache API > ----------------------------- > > Key: ISPN-3310 > URL: https://issues.jboss.org/browse/ISPN-3310 > Project: Infinispan > Issue Type: Sub-task > Components: Core API > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 6.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2013