October 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7118) Change cluster listener to use JGroups non OOB thread

by William Burns (JIRA)

William Burns created ISPN-7118: ----------------------------------- Summary: Change cluster listener to use JGroups non OOB thread Key: ISPN-7118 URL: https://issues.jboss.org/browse/ISPN-7118 Project: Infinispan Issue Type: Feature Request Components: Core, Listeners Reporter: William Burns Assignee: William Burns Currently listeners use dist exec to send events to clustered listeners. This is done while holding onto the lock which increases response time. We could instead send this on a JGroups non OOB thread and not wait for the response. This would allow the write operation to complete much quicker. However this can cause a missed event if the primary crashes after replying to the originator that it completed but before it transmitted the event to the various cluster listeners. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6241) Old version of commons-logging drags old version of servlet-api through infinispan-spring

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6241?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6241: ---------------------------------- Status: Open (was: New) > Old version of commons-logging drags old version of servlet-api through infinispan-spring > ----------------------------------------------------------------------------------------- > > Key: ISPN-6241 > URL: https://issues.jboss.org/browse/ISPN-6241 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Affects Versions: 8.1.1.Final > Reporter: B Bozhanov > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta1, 8.2.5.Final > > > infinispan-spring 8.1.1. has a dependency on an old version of commons-logging (1.1) which in turn has a "compile" dependency on servlet-api 2.3, so in maven the old servlet api is dragged into the build and then conflicts arise when deployed on a servlet container. > The dependency on commons-logging should be updated (1.2 has a "provided" dependency on the servlet-api) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6241) Old version of commons-logging drags old version of servlet-api through infinispan-spring

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6241?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6241: ---------------------------------- Component/s: Spring Integration > Old version of commons-logging drags old version of servlet-api through infinispan-spring > ----------------------------------------------------------------------------------------- > > Key: ISPN-6241 > URL: https://issues.jboss.org/browse/ISPN-6241 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Affects Versions: 8.1.1.Final > Reporter: B Bozhanov > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta1, 8.2.5.Final > > > infinispan-spring 8.1.1. has a dependency on an old version of commons-logging (1.1) which in turn has a "compile" dependency on servlet-api 2.3, so in maven the old servlet api is dragged into the build and then conflicts arise when deployed on a servlet container. > The dependency on commons-logging should be updated (1.2 has a "provided" dependency on the servlet-api) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6241) Old version of commons-logging drags old version of servlet-api through infinispan-spring

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6241?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6241: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4616 > Old version of commons-logging drags old version of servlet-api through infinispan-spring > ----------------------------------------------------------------------------------------- > > Key: ISPN-6241 > URL: https://issues.jboss.org/browse/ISPN-6241 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Affects Versions: 8.1.1.Final > Reporter: B Bozhanov > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta1, 8.2.5.Final > > > infinispan-spring 8.1.1. has a dependency on an old version of commons-logging (1.1) which in turn has a "compile" dependency on servlet-api 2.3, so in maven the old servlet api is dragged into the build and then conflicts arise when deployed on a servlet container. > The dependency on commons-logging should be updated (1.2 has a "provided" dependency on the servlet-api) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6241) Old version of commons-logging drags old version of servlet-api through infinispan-spring

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6241?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6241: ---------------------------------- Fix Version/s: 9.0.0.Beta1 8.2.5.Final > Old version of commons-logging drags old version of servlet-api through infinispan-spring > ----------------------------------------------------------------------------------------- > > Key: ISPN-6241 > URL: https://issues.jboss.org/browse/ISPN-6241 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.1.Final > Reporter: B Bozhanov > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta1, 8.2.5.Final > > > infinispan-spring 8.1.1. has a dependency on an old version of commons-logging (1.1) which in turn has a "compile" dependency on servlet-api 2.3, so in maven the old servlet api is dragged into the build and then conflicts arise when deployed on a servlet container. > The dependency on commons-logging should be updated (1.2 has a "provided" dependency on the servlet-api) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6241) Old version of commons-logging drags old version of servlet-api through infinispan-spring

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6241?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-6241: ------------------------------------- Assignee: Tristan Tarrant > Old version of commons-logging drags old version of servlet-api through infinispan-spring > ----------------------------------------------------------------------------------------- > > Key: ISPN-6241 > URL: https://issues.jboss.org/browse/ISPN-6241 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.1.Final > Reporter: B Bozhanov > Assignee: Tristan Tarrant > > infinispan-spring 8.1.1. has a dependency on an old version of commons-logging (1.1) which in turn has a "compile" dependency on servlet-api 2.3, so in maven the old servlet api is dragged into the build and then conflicts arise when deployed on a servlet container. > The dependency on commons-logging should be updated (1.2 has a "provided" dependency on the servlet-api) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7114) Consistency checker

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7114?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-7114: ------------------------------------- Assignee: Ryan Emerson > Consistency checker > ------------------- > > Key: ISPN-7114 > URL: https://issues.jboss.org/browse/ISPN-7114 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Tristan Tarrant > Assignee: Ryan Emerson > > We should implement a consistency checker that can either be run on demand via management (e.g. JMX) or triggered by a merge or a topology change caused by abrupt leavers. It should perform per-segment analysis of each key/value pair between primary and backup. The design should incorporate pluggable repair strategies (e.g. latest wins, primary wins, discard, degrade segment, custom) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7117) ContinuousQuery.addContinuousQueryListener should fail if cache is async

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7117?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-7117: -------------------------------- Status: Open (was: New) > ContinuousQuery.addContinuousQueryListener should fail if cache is async > ------------------------------------------------------------------------ > > Key: ISPN-7117 > URL: https://issues.jboss.org/browse/ISPN-7117 > Project: Infinispan > Issue Type: Bug > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Beta1, 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7117) ContinuousQuery.addContinuousQueryListener should fail if cache is async

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-7117: ----------------------------------- Summary: ContinuousQuery.addContinuousQueryListener should fail if cache is async Key: ISPN-7117 URL: https://issues.jboss.org/browse/ISPN-7117 Project: Infinispan Issue Type: Bug Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 9.0.0.Beta1, 9.0.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7116) Test methods that use a TestNg dataProvider are duplicated in JUnit reports

by Alan Field (JIRA)

[ https://issues.jboss.org/browse/ISPN-7116?page=com.atlassian.jira.plugin.... ] Alan Field updated ISPN-7116: ----------------------------- Description: TestNg test methods that use a `dataProvider` are reported as multiple duplicate test cases in the surefire results reports: {noformat} <testcase name="testDistExecPutGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.424"/> <testcase name="testDistExecPutGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.015"/> <testcase name="testEmbeddedScriptRemoteExecution" classname="org.infinispan.client.hotrod.ExecTest" time="0.132"/> <testcase name="testEmbeddedScriptRemoteExecution" classname="org.infinispan.client.hotrod.ExecTest" time="0.086"/> <testcase name="testExecPutConstantGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.016"/> <testcase name="testExecPutConstantGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.009"/> <testcase name="testExecReturnNull" classname="org.infinispan.client.hotrod.ExecTest" time="0.015"/> <testcase name="testExecReturnNull" classname="org.infinispan.client.hotrod.ExecTest" time="0.008"/> <testcase name="testLocalExecPutGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.022"/> <testcase name="testLocalExecPutGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.013"/> <testcase name="testLocalExecPutGetWithListener" classname="org.infinispan.client.hotrod.ExecTest" time="0.037"/> <testcase name="testLocalExecPutGetWithListener" classname="org.infinispan.client.hotrod.ExecTest" time="0.025"/> <testcase name="testRemoteScriptRemoteExecution" classname="org.infinispan.client.hotrod.ExecTest" time="0.074"/> <testcase name="testRemoteScriptRemoteExecution" classname="org.infinispan.client.hotrod.ExecTest" time="0.06"/> <testcase name="testRemovingNonExistentScript" classname="org.infinispan.client.hotrod.ExecTest" time="0.002"/> {noformat} The {{name}} property should include the parameters passed to the method to differentiate the results. was: TestNg test methods that use a `dataProvider` are reported as multiple duplicate test cases in the surefire results reports: {noformat} <testcase name="testDistExecPutGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.424"/> <testcase name="testDistExecPutGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.015"/> <testcase name="testEmbeddedScriptRemoteExecution" classname="org.infinispan.client.hotrod.ExecTest" time="0.132"/> <testcase name="testEmbeddedScriptRemoteExecution" classname="org.infinispan.client.hotrod.ExecTest" time="0.086"/> <testcase name="testExecPutConstantGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.016"/> <testcase name="testExecPutConstantGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.009"/> <testcase name="testExecReturnNull" classname="org.infinispan.client.hotrod.ExecTest" time="0.015"/> <testcase name="testExecReturnNull" classname="org.infinispan.client.hotrod.ExecTest" time="0.008"/> <testcase name="testLocalExecPutGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.022"/> <testcase name="testLocalExecPutGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.013"/> <testcase name="testLocalExecPutGetWithListener" classname="org.infinispan.client.hotrod.ExecTest" time="0.037"/> <testcase name="testLocalExecPutGetWithListener" classname="org.infinispan.client.hotrod.ExecTest" time="0.025"/> <testcase name="testRemoteScriptRemoteExecution" classname="org.infinispan.client.hotrod.ExecTest" time="0.074"/> <testcase name="testRemoteScriptRemoteExecution" classname="org.infinispan.client.hotrod.ExecTest" time="0.06"/> <testcase name="testRemovingNonExistentScript" classname="org.infinispan.client.hotrod.ExecTest" time="0.002"/> {noformat} The {{name}} property should include the parameter to differentiate the results. > Test methods that use a TestNg dataProvider are duplicated in JUnit reports > --------------------------------------------------------------------------- > > Key: ISPN-7116 > URL: https://issues.jboss.org/browse/ISPN-7116 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite - Core > Reporter: Alan Field > Assignee: Alan Field > > TestNg test methods that use a `dataProvider` are reported as multiple duplicate test cases in the surefire results reports: > {noformat} > <testcase name="testDistExecPutGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.424"/> > <testcase name="testDistExecPutGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.015"/> > <testcase name="testEmbeddedScriptRemoteExecution" classname="org.infinispan.client.hotrod.ExecTest" time="0.132"/> > <testcase name="testEmbeddedScriptRemoteExecution" classname="org.infinispan.client.hotrod.ExecTest" time="0.086"/> > <testcase name="testExecPutConstantGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.016"/> > <testcase name="testExecPutConstantGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.009"/> > <testcase name="testExecReturnNull" classname="org.infinispan.client.hotrod.ExecTest" time="0.015"/> > <testcase name="testExecReturnNull" classname="org.infinispan.client.hotrod.ExecTest" time="0.008"/> > <testcase name="testLocalExecPutGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.022"/> > <testcase name="testLocalExecPutGet" classname="org.infinispan.client.hotrod.ExecTest" time="0.013"/> > <testcase name="testLocalExecPutGetWithListener" classname="org.infinispan.client.hotrod.ExecTest" time="0.037"/> > <testcase name="testLocalExecPutGetWithListener" classname="org.infinispan.client.hotrod.ExecTest" time="0.025"/> > <testcase name="testRemoteScriptRemoteExecution" classname="org.infinispan.client.hotrod.ExecTest" time="0.074"/> > <testcase name="testRemoteScriptRemoteExecution" classname="org.infinispan.client.hotrod.ExecTest" time="0.06"/> > <testcase name="testRemovingNonExistentScript" classname="org.infinispan.client.hotrod.ExecTest" time="0.002"/> > {noformat} > The {{name}} property should include the parameters passed to the method to differentiate the results. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2016