February 2017 - infinispan-issues

[JBoss JIRA] (ISPN-7480) JDBC cache store doesn't work on Sybase

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7480?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7480: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR2 Resolution: Done > JDBC cache store doesn't work on Sybase > --------------------------------------- > > Key: ISPN-7480 > URL: https://issues.jboss.org/browse/ISPN-7480 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.0.0.CR1 > Reporter: Jiří Holuša > Assignee: Jiří Holuša > Fix For: 9.0.0.CR2 > > > When running JDBC cache store with Sybase, I get > {code} > Caused by: java.sql.SQLException: Incorrect syntax near the keyword 'FROM'. > {code} > This is caused by a typo in SybaseTableManager, PR with the fix coming soon. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7483) Use @deprecated javadoc with @Deprecated annotation

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7483?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7483: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR2 Resolution: Done > Use @deprecated javadoc with @Deprecated annotation > --------------------------------------------------- > > Key: ISPN-7483 > URL: https://issues.jboss.org/browse/ISPN-7483 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.CR1 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.CR2, 9.0.0.Final > > > Some APIs use {{@deprecated}} javadoc without annotating the method/class as {{@Deprecated}}, or even use {{@Deprecated}} (with capital D) in javadoc which probably does not work at all. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5021) Nodes that finish the rebalance later can see outdated values

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-5021?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-5021: ------------------------------ Fix Version/s: 9.0.0.Final > Nodes that finish the rebalance later can see outdated values > ------------------------------------------------------------- > > Key: ISPN-5021 > URL: https://issues.jboss.org/browse/ISPN-5021 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.2.Final > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Critical > Labels: consistency, testsuite_stability > Fix For: 9.0.0.Final > > > Copied from [ISPN-4444|https://issues.jboss.org/browse/ISPN-4444?focusedCommentId=1302...] > If the CH_UPDATE command is delayed on the old owner, the new owners might update the key without the old owner knowing, and a locality check on the old owner won't help. > I remember one thing that struck me when reading the Raft algorithm was that they install configuration changes symmetrically, in 3 phases. We might need to do the same for our rebalance: > 1. T0: read_ch=old, write_ch=old > 2. start a rebalance > 3. T1: read_ch=old, write_ch=old+new > 4. new owners have all the data > 5. T2: read_ch=new, write_ch=old+new > 6. remove old cache entries and ignore further writes > 7. T3: read_ch=new, write_ch=new -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5021) Nodes that finish the rebalance later can see outdated values

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-5021?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-5021: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/4827https://github.com/infi... (was: https://github.com/infinispan/infinispan/pull/4827) > Nodes that finish the rebalance later can see outdated values > ------------------------------------------------------------- > > Key: ISPN-5021 > URL: https://issues.jboss.org/browse/ISPN-5021 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.2.Final > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Critical > Labels: consistency, testsuite_stability > Fix For: 9.0.0.Final > > > Copied from [ISPN-4444|https://issues.jboss.org/browse/ISPN-4444?focusedCommentId=1302...] > If the CH_UPDATE command is delayed on the old owner, the new owners might update the key without the old owner knowing, and a locality check on the old owner won't help. > I remember one thing that struck me when reading the Raft algorithm was that they install configuration changes symmetrically, in 3 phases. We might need to do the same for our rebalance: > 1. T0: read_ch=old, write_ch=old > 2. start a rebalance > 3. T1: read_ch=old, write_ch=old+new > 4. new owners have all the data > 5. T2: read_ch=new, write_ch=old+new > 6. remove old cache entries and ignore further writes > 7. T3: read_ch=new, write_ch=new -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5021) Nodes that finish the rebalance later can see outdated values

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-5021?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-5021: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/4827, https://github.com/infinispan/infinispan/pull/4862 (was: https://github.com/infinispan/infinispan/pull/4827https://github.com/infi...) > Nodes that finish the rebalance later can see outdated values > ------------------------------------------------------------- > > Key: ISPN-5021 > URL: https://issues.jboss.org/browse/ISPN-5021 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.2.Final > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Critical > Labels: consistency, testsuite_stability > Fix For: 9.0.0.Final > > > Copied from [ISPN-4444|https://issues.jboss.org/browse/ISPN-4444?focusedCommentId=1302...] > If the CH_UPDATE command is delayed on the old owner, the new owners might update the key without the old owner knowing, and a locality check on the old owner won't help. > I remember one thing that struck me when reading the Raft algorithm was that they install configuration changes symmetrically, in 3 phases. We might need to do the same for our rebalance: > 1. T0: read_ch=old, write_ch=old > 2. start a rebalance > 3. T1: read_ch=old, write_ch=old+new > 4. new owners have all the data > 5. T2: read_ch=new, write_ch=old+new > 6. remove old cache entries and ignore further writes > 7. T3: read_ch=new, write_ch=new -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7483) Use @deprecated javadoc with @Deprecated annotation

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-7483?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-7483: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4865 > Use @deprecated javadoc with @Deprecated annotation > --------------------------------------------------- > > Key: ISPN-7483 > URL: https://issues.jboss.org/browse/ISPN-7483 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.CR1 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Final > > > Some APIs use {{@deprecated}} javadoc without annotating the method/class as {{@Deprecated}}, or even use {{@Deprecated}} (with capital D) in javadoc which probably does not work at all. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7483) Use @deprecated javadoc with @Deprecated annotation

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-7483?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-7483: ------------------------------ Status: Open (was: New) > Use @deprecated javadoc with @Deprecated annotation > --------------------------------------------------- > > Key: ISPN-7483 > URL: https://issues.jboss.org/browse/ISPN-7483 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.CR1 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Final > > > Some APIs use {{@deprecated}} javadoc without annotating the method/class as {{@Deprecated}}, or even use {{@Deprecated}} (with capital D) in javadoc which probably does not work at all. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7483) Use @deprecated javadoc with @Deprecated annotation

by Radim Vansa (JIRA)

Radim Vansa created ISPN-7483: --------------------------------- Summary: Use @deprecated javadoc with @Deprecated annotation Key: ISPN-7483 URL: https://issues.jboss.org/browse/ISPN-7483 Project: Infinispan Issue Type: Bug Affects Versions: 9.0.0.CR1 Reporter: Radim Vansa Assignee: Radim Vansa Fix For: 9.0.0.Final Some APIs use {{@deprecated}} javadoc without annotating the method/class as {{@Deprecated}}, or even use {{@Deprecated}} (with capital D) in javadoc which probably does not work at all. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7482) While migrating to resteasy-jaxrs-2.1.0.GA.jar to resteasy-jaxrs-2.3.1.GA. jar by using jetty 6.1.11 getting exception like : org.jboss.resteasy.plugins.providers.jaxb.JAXBMarshalException: A valid XmlRegistry could not be located

by Mahendra B (JIRA)

Mahendra B created ISPN-7482: -------------------------------- Summary: While migrating to resteasy-jaxrs-2.1.0.GA.jar to resteasy-jaxrs-2.3.1.GA. jar by using jetty 6.1.11 getting exception like : org.jboss.resteasy.plugins.providers.jaxb.JAXBMarshalException: A valid XmlRegistry could not be located Key: ISPN-7482 URL: https://issues.jboss.org/browse/ISPN-7482 Project: Infinispan Issue Type: Enhancement Components: Marshalling Reporter: Mahendra B Priority: Critical -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7481) ProtobufMetadataManagerDMROperationsIT interferes randomly with other server tests

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7481?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-7481: -------------------------------- Status: Open (was: New) > ProtobufMetadataManagerDMROperationsIT interferes randomly with other server tests > ---------------------------------------------------------------------------------- > > Key: ISPN-7481 > URL: https://issues.jboss.org/browse/ISPN-7481 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.CR1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.CR2 > > > It populates the protobuf metadata cache with garbage preventing other tests to run correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2017