September 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4733) Investigate potential issues with System.nanoTime() overflow

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4733?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-4733: -------------------------------- Status: Open (was: New) > Investigate potential issues with System.nanoTime() overflow > ------------------------------------------------------------ > > Key: ISPN-4733 > URL: https://issues.jboss.org/browse/ISPN-4733 > Project: Infinispan > Issue Type: Task > Components: Core, Test Suite - Core > Affects Versions: 7.0.0.Beta2 > Reporter: Dan Berindei > Assignee: William Burns > Labels: hackathon > Fix For: 7.0.0.CR1 > > > {{System.nanoTime()}} can overflow, so it's not ok to compare two {{System.nanoTime()}} return values directly. Instead, we always have to work with the difference between return values. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4748) Source code always recompiled (no incremental compilation)

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4748?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4748: ------------------------------- Summary: Source code always recompiled (no incremental compilation) (was: Source codo always recompiled (no incremental compilation)) > Source code always recompiled (no incremental compilation) > ---------------------------------------------------------- > > Key: ISPN-4748 > URL: https://issues.jboss.org/browse/ISPN-4748 > Project: Infinispan > Issue Type: Task > Affects Versions: 7.0.0.Beta2 > Reporter: Ion Savin > Assignee: Ion Savin > Fix For: 7.0.0.Final > > > Incremental compilation is broken. > Running: > {noformat} > $ mvn -DskipTests clean install > $ mvn test > {noformat} > will have the source code recompiled on the second call. > The source of the problem is an issue in the 3.x maven-compiler-plugin which is confused by the package-info.java source files (details here: https://jira.codehaus.org/browse/MCOMPILER-205) > Solving this problem could improve the build time slightly. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4731) Update classpath to ensure Weld loads Guava instead of Google Collections

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-4731?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-4731: ------------------------------------------- Another attempt: https://github.com/infinispan/infinispan/pull/2896 > Update classpath to ensure Weld loads Guava instead of Google Collections > ------------------------------------------------------------------------- > > Key: ISPN-4731 > URL: https://issues.jboss.org/browse/ISPN-4731 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration, Integration > Affects Versions: 7.0.0.Beta2 > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Labels: maven > Fix For: 7.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4731) Update classpath to ensure Weld loads Guava instead of Google Collections

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-4731?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reopened ISPN-4731: --------------------------------------- Unfortunately it didn't work... trying another way > Update classpath to ensure Weld loads Guava instead of Google Collections > ------------------------------------------------------------------------- > > Key: ISPN-4731 > URL: https://issues.jboss.org/browse/ISPN-4731 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration, Integration > Affects Versions: 7.0.0.Beta2 > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Labels: maven > Fix For: 7.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4742) Custom Transport is overwrite in configuration parser

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4742?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4742: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated. Thanks! > Custom Transport is overwrite in configuration parser > ----------------------------------------------------- > > Key: ISPN-4742 > URL: https://issues.jboss.org/browse/ISPN-4742 > Project: Infinispan > Issue Type: Bug > Affects Versions: 7.0.0.Beta2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.0.0.CR1 > > > The transport attribute is overwrite with the default transport in the parser. Fix it and add a test case -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4749) Enable unit tests in secure-embedded-cache quickstart

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-4749?page=com.atlassian.jira.plugin.... ] Jiří Holuša updated ISPN-4749: ------------------------------ Git Pull Request: https://github.com/jboss-developer/jboss-jdg-quickstarts/pull/52 > Enable unit tests in secure-embedded-cache quickstart > ----------------------------------------------------- > > Key: ISPN-4749 > URL: https://issues.jboss.org/browse/ISPN-4749 > Project: Infinispan > Issue Type: Enhancement > Components: Demos and Tutorials > Reporter: Jiří Holuša > Assignee: Jiří Holuša > Priority: Minor > > In secure-embedded-cache quickstart there is also possibility to run unit tests for those feature. Unfortunately, the test is annotated @Ignore which cannot be changed from command line and thus the test will never get run even by mvn test. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4749) Enable unit tests in secure-embedded-cache quickstart

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-4749?page=com.atlassian.jira.plugin.... ] Jiří Holuša updated ISPN-4749: ------------------------------ Priority: Minor (was: Optional) > Enable unit tests in secure-embedded-cache quickstart > ----------------------------------------------------- > > Key: ISPN-4749 > URL: https://issues.jboss.org/browse/ISPN-4749 > Project: Infinispan > Issue Type: Enhancement > Components: Demos and Tutorials > Reporter: Jiří Holuša > Assignee: Jiří Holuša > Priority: Minor > > In secure-embedded-cache quickstart there is also possibility to run unit tests for those feature. Unfortunately, the test is annotated @Ignore which cannot be changed from command line and thus the test will never get run even by mvn test. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4749) Enable unit tests in secure-embedded-cache quickstart

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-4749: --------------------------------- Summary: Enable unit tests in secure-embedded-cache quickstart Key: ISPN-4749 URL: https://issues.jboss.org/browse/ISPN-4749 Project: Infinispan Issue Type: Enhancement Components: Demos and Tutorials Reporter: Jiří Holuša Assignee: Jiří Holuša Priority: Optional In secure-embedded-cache quickstart there is also possibility to run unit tests for those feature. Unfortunately, the test is annotated @Ignore which cannot be changed from command line and thus the test will never get run even by mvn test. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4697) Single cache operation generates two sequential synchronous calls to the indexing engine

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4697?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4697: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated. Thanks! > Single cache operation generates two sequential synchronous calls to the indexing engine > ---------------------------------------------------------------------------------------- > > Key: ISPN-4697 > URL: https://issues.jboss.org/browse/ISPN-4697 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.0.0.Beta1 > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 7.0.0.CR1 > > > For a similar reason as explained in ISPN-4650, the method > {{org.infinispan.query.backend.QueryInterceptor.processPutKeyValueCommand(PutKeyValueCommand, InvocationContext, Object, TransactionContext)}} > is likely to invoke a {{removeFromIndexes}} first and then an {{updateIndexes}}. > When using transactions, the {{transactionContext}} will enqueue both operations for execution in the same call to the backend, but when no transaction is in progress, this will generate two sequential and independent calls to the backend. > When the backend happens to be the {{InfinispanIndexManager}}, this implies we're generating two sequential synchronous RPCs rather than bacthing the two operations in a single Update statement: the first call is completely redundant in most cases, and can be incorporated in the second call for all remaining edge cases. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4697) Single cache operation generates two sequential synchronous calls to the indexing engine

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4697?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4697: -------------------------------- Fix Version/s: 7.0.0.CR1 > Single cache operation generates two sequential synchronous calls to the indexing engine > ---------------------------------------------------------------------------------------- > > Key: ISPN-4697 > URL: https://issues.jboss.org/browse/ISPN-4697 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.0.0.Beta1 > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 7.0.0.CR1 > > > For a similar reason as explained in ISPN-4650, the method > {{org.infinispan.query.backend.QueryInterceptor.processPutKeyValueCommand(PutKeyValueCommand, InvocationContext, Object, TransactionContext)}} > is likely to invoke a {{removeFromIndexes}} first and then an {{updateIndexes}}. > When using transactions, the {{transactionContext}} will enqueue both operations for execution in the same call to the backend, but when no transaction is in progress, this will generate two sequential and independent calls to the backend. > When the backend happens to be the {{InfinispanIndexManager}}, this implies we're generating two sequential synchronous RPCs rather than bacthing the two operations in a single Update statement: the first call is completely redundant in most cases, and can be incorporated in the second call for all remaining edge cases. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 September 2014