November 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3748) Add additional server functionality around Remote Query

by William Burns (JIRA)

William Burns created ISPN-3748: ----------------------------------- Summary: Add additional server functionality around Remote Query Key: ISPN-3748 URL: https://issues.jboss.org/browse/ISPN-3748 Project: Infinispan Issue Type: Enhancement Components: Server Affects Versions: 6.0.0.Final Reporter: William Burns Assignee: Mircea Markus ISPN-3587 added very minimal support for remote query in the server. There are quite a few changes that are hoped will go into remote query in infinispan. # ISPN-3480 should make deployments easier (currently we are limited to URL only - could use string passing the protoc contents instead). # persistence (allow for added definitions to persist between restarts) # preload (allow for xml definition in server) More info on some of these can be found here [1] as well [1] https://community.jboss.org/message/844268?et=watches.email.thread#844268 -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3747) ProtobufMetadataRegistry should be persistent

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-3747: ----------------------------------- Summary: ProtobufMetadataRegistry should be persistent Key: ISPN-3747 URL: https://issues.jboss.org/browse/ISPN-3747 Project: Infinispan Issue Type: Feature Request Components: Querying Affects Versions: 6.0.0.Final Reporter: Adrian Nistor Assignee: Adrian Nistor -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3612) JON server plugin, unreachable NaN cache statistics values, even after Get Live Value

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3612?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-3612: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan-server/pull/195 > JON server plugin, unreachable NaN cache statistics values, even after Get Live Value > ------------------------------------------------------------------------------------- > > Key: ISPN-3612 > URL: https://issues.jboss.org/browse/ISPN-3612 > Project: Infinispan > Issue Type: Bug > Reporter: Mircea Markus > Assignee: William Burns > Priority: Critical > Labels: 620 > Fix For: 6.1.0.Final > > -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3745) Forwarded Prepare/Commit executed after transaction finished

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-3745?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-3745: ------------------------------ Summary: Forwarded Prepare/Commit executed after transaction finished (was: Forwarded Prepare/Commit executed after transaction has finished) > Forwarded Prepare/Commit executed after transaction finished > ------------------------------------------------------------ > > Key: ISPN-3745 > URL: https://issues.jboss.org/browse/ISPN-3745 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 6.0.0.Final > Reporter: Radim Vansa > Assignee: Mircea Markus > Priority: Critical > > Replicated TX cache, nodes A, B, C > 0. A and B have topology 2, C already got topology 3 > 1. A sends prepare with topology 2 to B and C, both apply the prepare and respond > 2. C forwards prepare to B with topology 3 > 3. A sends commit with topology 2 to B and C, both commit and respond > 4. again, C forwards prepare to B with topology 3 > 5. A and B get updated topology id > 6. A executes another transaction on the same entry > 7. prepare and commit from first transaction with topology 3 arrive at B - B overwrites (or removes) the entry again > Result: on B we have inconsistent state -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3746) infinispan-client-hotrod - OSGi MANIFEST.MF should have optional resolution for Apache Avro

by Claus Ibsen (JIRA)

Claus Ibsen created ISPN-3746: --------------------------------- Summary: infinispan-client-hotrod - OSGi MANIFEST.MF should have optional resolution for Apache Avro Key: ISPN-3746 URL: https://issues.jboss.org/browse/ISPN-3746 Project: Infinispan Issue Type: Task Components: Build process Affects Versions: 6.0.0.Final Reporter: Claus Ibsen Assignee: Mircea Markus The MANIFEST.MF of the infinispan-client-hotrod has mandatory imports of Apache Avro. But that should be optional, as end users can decide not to use Avro but the JBoss Marshalling etc. This import {code} Import-Package: javax.net.ssl,net.jcip.annotations;resolution:=optional, org.apache.avro,org.apache.avro.generic,org.apache.avro.io,org.apache.a vro.util,org.apache.commons.pool;version="[1.6,2)",org.apache.commons.p ool.impl;version="[1.6,2)",org.infinispan.commons;version="[6.0,7)",org .infinispan.commons.api;version="[6.0,7)",org.infinispan.commons.config uration;version="[6.0,7)",org.infinispan.commons.executors;version="[6. 0,7)",org.infinispan.commons.hash;version="[6.0,7)",org.infinispan.comm ons.io;version="[6.0,7)",org.infinispan.commons.logging;version="[6.0,7 )",org.infinispan.commons.marshall;version="[6.0,7)",org.infinispan.com mons.marshall.jboss;version="[6.0,7)",org.infinispan.commons.util;versi on="[6.0,7)",org.infinispan.commons.util.concurrent;version="[6.0,7)",o rg.infinispan.protostream;resolution:=optional,org.infinispan.query.dsl ;resolution:=optional,org.infinispan.query.dsl.impl;resolution:=optiona l,org.infinispan.query.remote.client;resolution:=optional,org.jboss.log ging;version="[3.1,4)" {code} Should have ;resolution:=optional for the org.apache.avro packages, so it would be: {code} Import-Package: javax.net.ssl,net.jcip.annotations;resolution:=optional, org.apache.avro,org.apache.avro.generic,org.apache.avro.io,org.apache.a vro.util;resolution:=optional,org.apache.commons.pool;version="[1.6,2)",org.apache.commons.p ool.impl;version="[1.6,2)",org.infinispan.commons;version="[6.0,7)",org .infinispan.commons.api;version="[6.0,7)",org.infinispan.commons.config uration;version="[6.0,7)",org.infinispan.commons.executors;version="[6. 0,7)",org.infinispan.commons.hash;version="[6.0,7)",org.infinispan.comm ons.io;version="[6.0,7)",org.infinispan.commons.logging;version="[6.0,7 )",org.infinispan.commons.marshall;version="[6.0,7)",org.infinispan.com mons.marshall.jboss;version="[6.0,7)",org.infinispan.commons.util;versi on="[6.0,7)",org.infinispan.commons.util.concurrent;version="[6.0,7)",o rg.infinispan.protostream;resolution:=optional,org.infinispan.query.dsl ;resolution:=optional,org.infinispan.query.dsl.impl;resolution:=optiona l,org.infinispan.query.remote.client;resolution:=optional,org.jboss.log ging;version="[3.1,4)" {code} >From the IRC room [14:35:21] <davsclaus> i have an osgi problem with the 6.0 client-hotrod [14:35:32] <davsclaus> it has mandatory osgi imports of apache avro [14:35:35] <davsclaus> and i dont want to use that [14:35:40] <davsclaus> i wanna keep using jboss marshalling [14:35:52] <davsclaus> but with osgi you are fucked as its mandatory import so i cannot ignore that [14:36:28] <davsclaus> would it be possible to log a ticket and get the client fixes so its manifest.mf file has [14:36:28] <davsclaus> org.apache.avro,org.apache.avro.generic,org.apache.avro.io,org.apache.a [14:36:28] <davsclaus> vro.util [14:36:44] <davsclaus> org.apache.avro,org.apache.avro.generic,org.apache.avro.io,org.apache.a [14:36:44] <davsclaus> vro.util;resolution:=optional [14:37:02] <davsclaus> eg i get this osgi validation errors [14:37:02] <davsclaus> [WARNING] No export found to match org.apache.avro.generic (imported by mvn:org.infinispan/infinispan-client-hotrod/6.0.0.Final) [14:37:02] <davsclaus> [WARNING] No export found to match org.apache.avro (imported by mvn:org.infinispan/infinispan-client-hotrod/6.0.0.Final) [14:37:02] <davsclaus> [WARNING] No export found to match org.apache.avro.util (imported by mvn:org.infinispan/infinispan-client-hotrod/6.0.0.Final) [14:37:02] <davsclaus> [WARNING] No export found to match org.apache.avro.io (imported by mvn:org.infinispan/infinispan-client-hotrod/6.0.0.Final) [14:37:11] <davsclaus> yeah unfortunaltey some ppl are stuck on osgi :( [14:43:59] rbenevides is now known as rbenevides|lunch [14:44:20] matt_test__ (~matt(a)twdp-174-109-175-151.nc.res.rr.com) joined the channel. [14:51:20] tenfourty_afk is now known as tenfourty [14:57:03] rachmatowicz (~nrla(a)modemcable117.232-202-24.mc.videotron.ca) joined the channel. [14:59:10] <+galderz> davsclaus, sure, fill one in issues.jboss.org/browse/ISPN -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3745) Forwarded Prepare/Commit executed after transaction has finished

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3745?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3745: ----------------------------------------------- Radim Vansa <rvansa(a)redhat.com> made a comment on [bug 1033087|https://bugzilla.redhat.com/show_bug.cgi?id=1033087] Replicated TX cache, nodes A, B, C 0. A and B have topology 2, C already got topology 3 1. A sends prepare with topology 2 to B and C, both apply the prepare and respond 2. C forwards prepare to B with topology 3 3. A sends commit with topology 2 to B and C, both commit and respond 4. again, C forwards prepare to B with topology 3 5. A and B get updated topology id 6. A executes another transaction on the same entry 7. prepare and commit from first transaction with topology 3 arrive at B - B overwrites (or removes) the entry again Result: on B we have inconsistent state > Forwarded Prepare/Commit executed after transaction has finished > ---------------------------------------------------------------- > > Key: ISPN-3745 > URL: https://issues.jboss.org/browse/ISPN-3745 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 6.0.0.Final > Reporter: Radim Vansa > Assignee: Mircea Markus > Priority: Critical > > Replicated TX cache, nodes A, B, C > 0. A and B have topology 2, C already got topology 3 > 1. A sends prepare with topology 2 to B and C, both apply the prepare and respond > 2. C forwards prepare to B with topology 3 > 3. A sends commit with topology 2 to B and C, both commit and respond > 4. again, C forwards prepare to B with topology 3 > 5. A and B get updated topology id > 6. A executes another transaction on the same entry > 7. prepare and commit from first transaction with topology 3 arrive at B - B overwrites (or removes) the entry again > Result: on B we have inconsistent state -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3745) Forwarded Prepare/Commit executed after transaction has finished

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3745?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3745: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1033087 > Forwarded Prepare/Commit executed after transaction has finished > ---------------------------------------------------------------- > > Key: ISPN-3745 > URL: https://issues.jboss.org/browse/ISPN-3745 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 6.0.0.Final > Reporter: Radim Vansa > Assignee: Mircea Markus > Priority: Critical > > Replicated TX cache, nodes A, B, C > 0. A and B have topology 2, C already got topology 3 > 1. A sends prepare with topology 2 to B and C, both apply the prepare and respond > 2. C forwards prepare to B with topology 3 > 3. A sends commit with topology 2 to B and C, both commit and respond > 4. again, C forwards prepare to B with topology 3 > 5. A and B get updated topology id > 6. A executes another transaction on the same entry > 7. prepare and commit from first transaction with topology 3 arrive at B - B overwrites (or removes) the entry again > Result: on B we have inconsistent state -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3745) Forwarded Prepare/Commit executed after transaction has finished

by Radim Vansa (JIRA)

Radim Vansa created ISPN-3745: --------------------------------- Summary: Forwarded Prepare/Commit executed after transaction has finished Key: ISPN-3745 URL: https://issues.jboss.org/browse/ISPN-3745 Project: Infinispan Issue Type: Bug Components: Transactions Affects Versions: 6.0.0.Final Reporter: Radim Vansa Assignee: Mircea Markus Priority: Critical Replicated TX cache, nodes A, B, C 0. A and B have topology 2, C already got topology 3 1. A sends prepare with topology 2 to B and C, both apply the prepare and respond 2. C forwards prepare to B with topology 3 3. A sends commit with topology 2 to B and C, both commit and respond 4. again, C forwards prepare to B with topology 3 5. A and B get updated topology id 6. A executes another transaction on the same entry 7. prepare and commit from first transaction with topology 3 arrive at B - B overwrites (or removes) the entry again Result: on B we have inconsistent state -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3691) Make client side Connection refused error TRACE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3691?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3691: ----------------------------------------------- Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug 1028411|https://bugzilla.redhat.com/show_bug.cgi?id=1028411] still in 6.2.0.ER4 > Make client side Connection refused error TRACE > ----------------------------------------------- > > Key: ISPN-3691 > URL: https://issues.jboss.org/browse/ISPN-3691 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 6.0.0.CR1 > Reporter: Michal Linhard > Assignee: Mircea Markus > Priority: Minor > > After solving ISPN-3454, it seems that only remaining client-side error during node crashes is "Connection refused": > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/RESILIENCE... > This has been reported before as ISPN-1794 or ISPN-1119, but actually it seems like it reappeared in different place. > Sorry for not reporting sooner, I got used to ignoring some of the long-open cosmetic low-prio log message issues, that I forgot about this one... > The issue here is that these "Connection refused" problems are retry-able, so the client log shouldn't contain error. > Maybe only some info level message about failing over to different node. But that's actually already reported by the INFO level messages about the topology changes -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2577) Silence SuspectExceptions

by Anuj Shah (JIRA)

[ https://issues.jboss.org/browse/ISPN-2577?page=com.atlassian.jira.plugin.... ] Anuj Shah commented on ISPN-2577: --------------------------------- There's a discussion here: https://community.jboss.org/message/846155 This issue may be more than cosmetic > Silence SuspectExceptions > ------------------------- > > Key: ISPN-2577 > URL: https://issues.jboss.org/browse/ISPN-2577 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.Beta4 > Reporter: Michal Linhard > Assignee: Dan Berindei > Priority: Critical > Fix For: 6.1.0.Final > > > There are lots of SuspectExceptions in resilience test run: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... > We managed to keep these under cover for 5.1.x branch. > This is of course a cosmetic problem, but it polutes the log with unnecessary ERRORs. > Parsed logs here: > http://www.qa.jboss.com/~mlinhard/test_results/run54-parsed/ -- 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

11 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2013