November 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3681) enhance the documentation of the new persistence API

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3681: ----------------------------------- Summary: enhance the documentation of the new persistence API Key: ISPN-3681 URL: https://issues.jboss.org/browse/ISPN-3681 Project: Infinispan Issue Type: Enhancement Reporter: Mircea Markus Assignee: Mircea Markus -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3681) enhance the documentation of the new persistence API

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3681?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3681: -------------------------------- Priority: Minor (was: Major) > enhance the documentation of the new persistence API > ---------------------------------------------------- > > Key: ISPN-3681 > URL: https://issues.jboss.org/browse/ISPN-3681 > Project: Infinispan > Issue Type: Enhancement > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Minor > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3681) enhance the documentation of the new persistence API

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3681?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3681: -------------------------------- Fix Version/s: 6.0.0.CR2 > enhance the documentation of the new persistence API > ---------------------------------------------------- > > Key: ISPN-3681 > URL: https://issues.jboss.org/browse/ISPN-3681 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 6.0.0.CR1 > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Minor > Fix For: 6.0.0.CR2 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3681) enhance the documentation of the new persistence API

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3681?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3681: -------------------------------- Affects Version/s: 6.0.0.CR1 > enhance the documentation of the new persistence API > ---------------------------------------------------- > > Key: ISPN-3681 > URL: https://issues.jboss.org/browse/ISPN-3681 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 6.0.0.CR1 > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Minor > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3524) Add RHQ support for registering protobuf descriptors

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3524?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-3524: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan-server/pull/179 > Add RHQ support for registering protobuf descriptors > ---------------------------------------------------- > > Key: ISPN-3524 > URL: https://issues.jboss.org/browse/ISPN-3524 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Affects Versions: 6.0.0.Alpha4 > Reporter: Adrian Nistor > Assignee: William Burns > Fix For: 6.0.0.Final > > > This is the RHQ counterpart of ISPN-3172. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3635) Out of data read after write on node losing ownership

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3635?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3635: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Out of data read after write on node losing ownership > ----------------------------------------------------- > > Key: ISPN-3635 > URL: https://issues.jboss.org/browse/ISPN-3635 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache, State transfer > Affects Versions: 5.3.0.Final > Reporter: Radim Vansa > Assignee: Pedro Ruivo > Priority: Critical > Labels: 620 > Fix For: 6.0.0.Final > > > In a situation where a node is losing ownership of an entry (during a state transfer), when the node does a write (and commits that), the change is propagated only to the new owners, the entry is not written locally. However, when it executes read for this key afterwards, it gets the old value as this is directly retrieved from the data container. > This bug was observed in transactional mode, but might not be limited to it. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3454) Hot Rod client doesn't retry operation on RemoteException

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3454?page=com.atlassian.jira.plugin.... ] Work on ISPN-3454 started by Galder Zamarreño. > Hot Rod client doesn't retry operation on RemoteException > --------------------------------------------------------- > > Key: ISPN-3454 > URL: https://issues.jboss.org/browse/ISPN-3454 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Alpha3 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Critical > Labels: 620 > Fix For: 6.0.0.CR2, 6.0.0.Final > > > This is a client-side problem. > In a resilience test with 4 nodes where 1 is killed, I'm getting a lot of these: > {code} > 08:30:55,198 ERROR [org.jboss.smartfrog.jdg.loaddriver.DriverThread] (DriverThread-369) Error doing: PUT key399869 to node node04, took 493 ms > org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[821188] returned server error (status=0x85): org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node01/default, see cause for remote stack trace > at org.infinispan.client.hotrod.impl.protocol.Codec10.checkForErrorsInResponseStatus(Codec10.java:143) > at org.infinispan.client.hotrod.impl.protocol.Codec10.readHeader(Codec10.java:99) > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56) > at org.infinispan.client.hotrod.impl.operations.AbstractKeyValueOperation.sendPutOperation(AbstractKeyValueOperation.java:50) > at org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:30) > at org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:19) > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:46) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:209) > at org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:79) > at org.jboss.qa.jdg.adapter.Infinispan60Adapter$HotRodRemoteCacheAdapter.put(Infinispan60Adapter.java:269) > at org.jboss.smartfrog.jdg.loaddriver.DriverThreadImpl.makeRequest(DriverThreadImpl.java:265) > at org.jboss.smartfrog.jdg.loaddriver.DriverThreadImpl.run(DriverThreadImpl.java:378) > {code} > Isn't this a recoverable problem that shouldn't be left to user to handle ? > source: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/RESILIENCE... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3270) Hotrod clients removeWithVersion doesn't work with replicated cache

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3270?page=com.atlassian.jira.plugin.... ] Work on ISPN-3270 started by Galder Zamarreño. > Hotrod clients removeWithVersion doesn't work with replicated cache > ------------------------------------------------------------------- > > Key: ISPN-3270 > URL: https://issues.jboss.org/browse/ISPN-3270 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 6.0.0.Beta1 > Reporter: Jakub Markos > Assignee: Galder Zamarreño > Priority: Critical > Labels: 620 > Fix For: 6.0.0.Final > > Attachments: server-trace-logs.zip > > > I have a cluster of 2 latest infinispan servers (6.0.0-SNAPSHOT) with the following container configuration: > {code:xml}<cache-container name="default" default-cache="default" listener-executor="infinispan-listener"> > <transport stack="udp" executor="infinispan-transport" lock-timeout="240000"/> > <replicated-cache name="default" start="EAGER" mode="SYNC" batching="false" remote-timeout="60000"> > <transaction mode="NONE"/> > <state-transfer enabled="true" timeout="60000"/> > </replicated-cache> > </cache-container> > {code} > Running this code: > {code} remoteCache = remoteCacheManager.getCache(); > remoteCache.clear(); > assertFalse(remoteCache.removeWithVersion("aKey", 12321212l)); > remoteCache.put("aKey", "aValue"); > VersionedValue valueBinary = remoteCache.getVersioned("aKey"); > System.out.println("value = " + valueBinary.getValue()); > System.out.println("version = " + valueBinary.getVersion()); > System.out.println(remoteCache.removeWithVersion("aKey",valueBinary.getVersion())); > valueBinary = remoteCache.getVersioned("aKey"); > System.out.println("value = " + valueBinary.getValue()); > System.out.println("version = " + valueBinary.getVersion()); > {code} > results most of the time in (and the other times the removeWithVersion returns false) > {quote} > value = aValue > version = 281483566645249 > true > value = aValue > version = 281483566645249 > {quote} > The command works with distributed/local cache. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3680) Inconsistent way to use the column id in the JdbcBinaryCacheStore

by Nicolas Filotto (JIRA)

[ https://issues.jboss.org/browse/ISPN-3680?page=com.atlassian.jira.plugin.... ] Nicolas Filotto commented on ISPN-3680: --------------------------------------- Already provided in the "Git Pull Request" field > Inconsistent way to use the column id in the JdbcBinaryCacheStore > ----------------------------------------------------------------- > > Key: ISPN-3680 > URL: https://issues.jboss.org/browse/ISPN-3680 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.2.7.Final, 5.3.0.Final, 6.0.0.CR1 > Reporter: Nicolas Filotto > Assignee: Mircea Markus > > I met some issues with (at least) H2 and JdbcBinaryCacheStore that prevent to modify a value in the cache store which is quite annoying. After a deeper look, I realized that it was due to the method {{JdbcBinaryCacheStore.loadBucket(Integer keyHashCode)}} that uses {{setInt}} instead of {{setString}} like in updateBucket and insertBucket to set the id as parameter to the query. With HSQLDB and MySQL, it works normally but with H2, the result of the query is always empty so it always tries to add a new entry which of course fails because of the integrity constraint on the primary key (aka the id). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3318) Migrate data from one cache store to another

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3318?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3318: ----------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/2005, https://github.com/infinispan/infinispan/pull/2103 (was: https://github.com/infinispan/infinispan/pull/2005) > Migrate data from one cache store to another > -------------------------------------------- > > Key: ISPN-3318 > URL: https://issues.jboss.org/browse/ISPN-3318 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > Find a generic way to transfer data from one cache store to another, which could involve different Infinispan versions. This is handy to migrate file cache store based users to single file cache store (ISPN-2806). > Ideally, this should be added as a recipe for rolling upgrades. -- 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, 5 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 November 2013