September 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4720) Values data reverts in Compatibilty mode in Infinispan 6.0.2

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4720?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4720: ------------------------------------ Looks like the problem is caused by a concurrent activation from the cache store: remote-thread-0: receive PrepareCommand(gtx, ReplaceCommand(key, oldValue, newValue)) remote-thread-0: the key doesn't exist in the data container, read the old value from the store remote-thread-0: send PrepareCommand response OOB-2: receive ClusteredGet(key) OOB-2: the key still doesn't exist in the data container, read the old value from the store and set the isLoaded flag remote-thread-0: receive CommitCommand(gtx) remote-thread-0: commit key=newValue to the data container and the store remote-thread-0: send CommitCommand response OOB-2: commit key=oldValue to the data container because of the isLoaded flag This has already been fixed on the 7.0 stream since 7.0.0.Alpha3, with ISPN-3797. > Values data reverts in Compatibilty mode in Infinispan 6.0.2 > ------------------------------------------------------------ > > Key: ISPN-4720 > URL: https://issues.jboss.org/browse/ISPN-4720 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.2.Final > Environment: Linux 3.15.8-200.fc20.x86_64 > Reporter: Prashant Thakur > Assignee: Dan Berindei > Priority: Critical > Labels: Infinispan > Attachments: distributed_cache_configuration.xml, tc1.zip, tc2.out, tc3.out, tc4.out > > > 1) The owners of the keys are Node1 and Node4 > 0911 10:56:56,552 TRACE [org.infinispan.interceptors.distribution.TxDistributionInterceptor] [remote-thread-0] (TxDistributionInterceptor.java:362) - Not doing a remote get for key 1029 since entry is mapped to current node (blrsrv42-19390), or is in L1. Owners are [blrsrv29-4565, blrsrv42-19390] > 2. The request for update came to Node2 a non-owner. > 0911 10:56:56,388 TRACE [org.infinispan.statetransfer.StateTransferInterceptor] [HotRodServerWorker-2] (StateTransferInterceptor.java:203) - handleNonTxWriteCommand for command ReplaceCommand{key=1029, oldValue=TestData{id=1029, field1=XXXXXX}, newValue=TestData{id=1029, field1=cyyy}, metadata=EmbeddedMetadata{version=NumericVersion{version=844433520066561}}, flags=[OPERATION_HOTROD], successful=true, valueMatcher=MATCH_EXPECTED} > 3. The updates are happening in Node1 and overwritten again with old data present in OOB Thread. Because of which the Node1, reverts back to the old data. > 4. While doing a get from Node 1 we again receive the old value -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4737) Noisy exceptions in Hot Rod client when node goes down

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4737?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4737: ----------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Noisy exceptions in Hot Rod client when node goes down > ------------------------------------------------------ > > Key: ISPN-4737 > URL: https://issues.jboss.org/browse/ISPN-4737 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 7.0.0.Beta2 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.CR2, 7.0.0.Final > > Attachments: hr-client.log > > > When a node goes down, the Hot Rod client prints some noisy exceptions such as: > {code} > 11:30:27,846 ERROR [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (main) ISPN004017: Could not fetch transport: org.infinispan.client.hotrod.exceptions.TransportException:: Could not connect to server: /127.0.0.1:11322 > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:76) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:35) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:16) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1220) [commons-pool-1.6.redhat-6.jar:1.6.redhat-6] > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.borrowTransportFromPool(TcpTransportFactory.java:322) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.getTransport(TcpTransportFactory.java:216) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.operations.AbstractKeyOperation.getTransport(AbstractKeyOperation.java:40) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:48) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:237) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:79) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at com.example.Main.main(Main.java:41) [:] > Caused by: java.net.ConnectException: Connection refused > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [rt.jar:1.7.0_65] > at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739) [rt.jar:1.7.0_65] > at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:117) [rt.jar:1.7.0_65] > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:66) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > ... 10 more > 11:30:27,851 WARN [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (main) ISPN004022: Unable to invalidate transport for server: /127.0.0.1:11322 > 11:30:27,855 ERROR [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (main) ISPN004017: Could not fetch transport: org.infinispan.client.hotrod.exceptions.TransportException:: Could not connect to server: /127.0.0.1:11322 > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:76) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:35) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:16) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1220) [commons-pool-1.6.redhat-6.jar:1.6.redhat-6] > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.borrowTransportFromPool(TcpTransportFactory.java:322) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.getTransport(TcpTransportFactory.java:216) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.operations.AbstractKeyOperation.getTransport(AbstractKeyOperation.java:40) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:48) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:237) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:79) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > at com.example.Main.main(Main.java:41) [:] > Caused by: java.net.ConnectException: Connection refused > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [rt.jar:1.7.0_65] > at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739) [rt.jar:1.7.0_65] > at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:117) [rt.jar:1.7.0_65] > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:66) [infinispan-client-hotrod-6.1.1.ER2-redhat-1.jar:6.1.1.ER2-redhat-1] > ... 10 more > {code} > This does not cause malfunctioning but pollutes client logs. Hot Rod clients recover fine from nodes going down and eventually these exceptions disappear. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4752) Implement native getAll/putAll operations in Hot Rod 2.0

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-4752: -------------------------------------- Summary: Implement native getAll/putAll operations in Hot Rod 2.0 Key: ISPN-4752 URL: https://issues.jboss.org/browse/ISPN-4752 Project: Infinispan Issue Type: Feature Request Components: Remote Protocols Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 7.0.0.CR1, 7.0.0.Final To help make RemoteCache.getAll() and RemoteCache.putAll() operations more efficient. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3836) TxCleanupService can cause TCCL leak

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3836?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3836: ------------------------------- Assignee: Ion Savin (was: Dan Berindei) > TxCleanupService can cause TCCL leak > ------------------------------------ > > Key: ISPN-3836 > URL: https://issues.jboss.org/browse/ISPN-3836 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Brent Douglas > Assignee: Ion Savin > > Looks to me like this should be using infinispan's classloader rather than the TCCL when creating a thread. > https://issues.jboss.org/browse/WFLY-2605 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4357) Use a specific cache for managing protofiles

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4357?page=com.atlassian.jira.plugin.... ] Work on ISPN-4357 started by Adrian Nistor. ------------------------------------------- > Use a specific cache for managing protofiles > -------------------------------------------- > > Key: ISPN-4357 > URL: https://issues.jboss.org/browse/ISPN-4357 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: Adrian Nistor > Labels: 64QueryBlockers > Fix For: 7.0.0.CR1 > > > Portofile defining schema should be held in a separate cache. This would allow users to manage schema from a hotrod client. Security should be considered as well. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4357) Use a specific cache for managing protofiles

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4357?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4357: -------------------------------- Fix Version/s: 7.0.0.CR1 > Use a specific cache for managing protofiles > -------------------------------------------- > > Key: ISPN-4357 > URL: https://issues.jboss.org/browse/ISPN-4357 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: Adrian Nistor > Labels: 64QueryBlockers > Fix For: 7.0.0.CR1 > > > Portofile defining schema should be held in a separate cache. This would allow users to manage schema from a hotrod client. Security should be considered as well. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4751) Hibernate search, infinispan and Amazon S3 - IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4751?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-4751: --------------------------------------- [~mircea.markus] that's a complex question since {{infinispan-cachestore-cloud}} was removed from the maintained codebase since before the 6 release. [~lance.java] thanks for opening the issue. This is the right place, however between versions 5 and 6 the Infinispan core team moved some CacheStore implementations from the main repository https://github.com/infinispan/infinispan into other repositories of the Infinispan organization, as it wasn't feasible to maintain them all at the same time. I'm afraid noone is in charge of maintaining https://github.com/infinispan/infinispan-cachestore-cloud : your best bet is to try fixing the issue and send a patch, we'll be happy to integrate it and make a new release. I hope it won't be too complex, you might have luck just by upgrading the jclouds dependency: AFAIK it's still using a very old one and it's very likely that someone fixed this already. > Hibernate search, infinispan and Amazon S3 - IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer) > ------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-4751 > URL: https://issues.jboss.org/browse/ISPN-4751 > Project: Infinispan > Issue Type: Bug > Reporter: Lance Ess > Assignee: Mircea Markus > > I'm trying to use hibernate-search to host a Lucene index on Amazon S3 but I'm getting the following exception: > {code} > Exception in thread "LuceneIndexesData-CloudCacheStore-0" java.lang.IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer) > at org.infinispan.loaders.bucket.Bucket.setBucketId(Bucket.java:84) > at org.infinispan.loaders.cloud.CloudCacheStore.readFromBlob(CloudCacheStore.java:450) > at org.infinispan.loaders.cloud.CloudCacheStore.scanBlobForExpiredEntries(CloudCacheStore.java:292) > at org.infinispan.loaders.cloud.CloudCacheStore.purge(CloudCacheStore.java:284) > at org.infinispan.loaders.cloud.CloudCacheStore.purgeInternal(CloudCacheStore.java:336) > at org.infinispan.loaders.AbstractCacheStore$2.run(AbstractCacheStore.java:111) > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > {code} > The documentation for persisting Lucene indexes on Amazon-S3 is a little sparse but I think I'm on the right track. I'm trying to start infinispan embedded within my application so I've specified a path to the infinispan XML as follows in my hibernate.cfg.xml > {code:xml} > <property name="hibernate.search.default.directory_provider">infinispan</property> > <property name="hibernate.search.infinispan.configuration_resourcename">infinispan-amazons3.xml</property> > <property name="hibernate.search.infinispan.chunk_size">300000000</property> > {code} > And my infinispan-amazons3.xml is: > {code:xml} > <infinispan> > <default> > <loaders> > <cloudStore xmlns="urn:infinispan:config:cloud:5.3" > cloudService="aws-s3" > identity="user" > password="password" > bucketPrefix="bucket"> > </cloudStore> > </loaders> > </default> > </infinispan> > {code} > I'm using the following versions (maven pom.xml) > {code} > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-search</artifactId> > <version>4.4.4.Final</version> > </dependency> > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-search-infinispan</artifactId> > <version>4.4.4.Final</version> > </dependency> > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-cachestore-cloud</artifactId> > <version>5.3.0.Final</version> > </dependency> > <dependency> > <groupId>org.jclouds.provider</groupId> > <artifactId>aws-s3</artifactId> > <version>1.4.1</version> > </dependency> > {code} > I initially thought this was related to ISPN-1909 but my version is after the fix for that issue (5.1.3.CR1, 5.1.3.FINAL) > FYI here's my maven dependency tree (grepped for infinispan) > {code} > $ mvn dependency:tree | grep infinispan > [INFO] +- org.hibernate:hibernate-search-infinispan:jar:4.4.4.Final:compile > [INFO] | \- org.infinispan:infinispan-lucene-directory:jar:5.3.0.Final:compile > [INFO] +- org.infinispan:infinispan-cachestore-cloud:jar:5.3.0.Final:compile > [INFO] | \- org.infinispan:infinispan-core:jar:5.3.0.Final:compile > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4385) Document installation process for OSGi containers

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4385?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4385: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.CR1 Resolution: Done > Document installation process for OSGi containers > ------------------------------------------------- > > Key: ISPN-4385 > URL: https://issues.jboss.org/browse/ISPN-4385 > Project: Infinispan > Issue Type: Task > Reporter: Ion Savin > Assignee: Ion Savin > 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-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: ------------------------------- Fix Version/s: 7.0.0.CR1 > 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.CR1, 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-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: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2014