April 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9097) java.lang.ClassNotFoundException: org.infinispan.query.Search

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9097?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9097: ------------------------------------ Component/s: Remote Protocols > java.lang.ClassNotFoundException: org.infinispan.query.Search > ------------------------------------------------------------- > > Key: ISPN-9097 > URL: https://issues.jboss.org/browse/ISPN-9097 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.2.1.Final > Reporter: Sergey Chernolyas > Assignee: Gustavo Fernandes > > Then I call > {code:java} > RemoteCacheManager remoteCacheManager = new RemoteCacheManager(builder.build(true)); > remoteCacheManager.administration().reindexCache("pojocache"); > {code} > I take exception: > _______________ > Apr 22, 2018 10:55:01 AM org.infinispan.client.hotrod.impl.protocol.Codec20 checkForErrorsInResponseStatus > WARN: ISPN004005: Error received from the server: java.lang.NoClassDefFoundError: org/infinispan/query/Search > java.lang.ClassNotFoundException: org.infinispan.query.Search from [Module "org.infinispan.server" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /home/osboxes/java/infinispan-server-9.2.1.Final/modules,/home/osboxes/java/infinispan-server-9.2.1.Final/modules/system/layers/base))] > Exception in thread "main" org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=8 returned server error (status=0x85): java.lang.NoClassDefFoundError: org/infinispan/query/Search > java.lang.ClassNotFoundException: org.infinispan.query.Search from [Module "org.infinispan.server" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /home/osboxes/java/infinispan-server-9.2.1.Final/modules,/home/osboxes/java/infinispan-server-9.2.1.Final/modules/system/layers/base))] > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:383) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:177) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:163) > at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:85) > at org.infinispan.client.hotrod.impl.transport.netty.HintedReplayingDecoder.callDecode(HintedReplayingDecoder.java:98) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) > at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) > at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) > at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1414) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:945) > at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:806) > at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:404) > at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:304) > at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Process finished with exit code 1 > _____ > I used remote Infinispan. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9101) EncryptProtocolIT.testEncryptProtocolRegistered random failures

by Dan Berindei (JIRA)

Dan Berindei created ISPN-9101: ---------------------------------- Summary: EncryptProtocolIT.testEncryptProtocolRegistered random failures Key: ISPN-9101 URL: https://issues.jboss.org/browse/ISPN-9101 Project: Infinispan Issue Type: Bug Components: Test Suite - Server Affects Versions: 9.2.1.Final Reporter: Dan Berindei Priority: Critical Fix For: 9.3.0.Beta1 {noformat} java.lang.RuntimeException: Could not retrieve HotRod host at org.infinispan.server.test.security.jgroups.encrypt.EncryptProtocolIT.testEncryptProtocolRegistered(EncryptProtocolIT.java:63) Caused by: java.lang.IllegalArgumentException: Could not retrieve attribute HostName on MBean jboss.datagrid-infinispan:type=Server,name=HotRod,component=Transport at org.infinispan.server.test.security.jgroups.encrypt.EncryptProtocolIT.testEncryptProtocolRegistered(EncryptProtocolIT.java:63) Caused by: javax.management.InstanceNotFoundException: jboss.datagrid-infinispan:type=Server,name=HotRod,component=Transport {noformat} The log shows this exception: {noformat} &amp#27;[0m&amp#27;[31m13:36:29,258 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.datagrid-jgroups.channel.cluster: org.jboss.msc.service.StartException in service jboss.datagrid-jgroups.channel.cluster: java.security.PrivilegedActionException: java.io.IOException: Invalid secret key format at org.infinispan.server.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:79) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) Caused by: java.security.PrivilegedActionException: java.io.IOException: Invalid secret key format at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:623) at org.infinispan.server.jgroups.JChannelFactory.createChannel(JChannelFactory.java:104) at org.infinispan.server.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:77) ... 8 more Caused by: java.io.IOException: Invalid secret key format at com.sun.crypto.provider.JceKeyStore.engineLoad(JceKeyStore.java:856) at java.security.KeyStore.load(KeyStore.java:1445) at org.jgroups.protocols.SYM_ENCRYPT.readSecretKeyFromKeystore(SYM_ENCRYPT.java:97) at org.jgroups.protocols.SYM_ENCRYPT.init(SYM_ENCRYPT.java:78) at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:840) at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:479) at org.jgroups.JChannel.init(JChannel.java:992) at org.jgroups.JChannel.<init>(JChannel.java:148) at org.infinispan.server.jgroups.JChannelFactory.lambda$createChannel$0(JChannelFactory.java:103) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:619) ... 10 more {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7104) Cache remove fails to return value in invalidation mode with cache store

by Vladimir Dzhuvinov (JIRA)

[ https://issues.jboss.org/browse/ISPN-7104?page=com.atlassian.jira.plugin.... ] Vladimir Dzhuvinov commented on ISPN-7104: ------------------------------------------ The bug persists in 9.2.1, our recent tests showed. Out of 1K putIfAbsent ops, it was wrong 539 times. > Cache remove fails to return value in invalidation mode with cache store > ------------------------------------------------------------------------ > > Key: ISPN-7104 > URL: https://issues.jboss.org/browse/ISPN-7104 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.4.Final, 9.2.1.Final > Reporter: Vladimir Dzhuvinov > Assignee: William Burns > Priority: Critical > Attachments: RemoveInInvalidationModeTest.java > > > The cache `remove` method occasionally fails to return the removed value, and returns `null`. > Observed in two node setup in invalidation mode, with a configured cache store (Redis). > Tests reveal that about 40% of the times the method returns `null`, the remaining 60% the removed value is correctly returned. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7104) Cache remove fails to return value in invalidation mode with cache store

by Vladimir Dzhuvinov (JIRA)

[ https://issues.jboss.org/browse/ISPN-7104?page=com.atlassian.jira.plugin.... ] Vladimir Dzhuvinov updated ISPN-7104: ------------------------------------- Affects Version/s: 9.2.1.Final > Cache remove fails to return value in invalidation mode with cache store > ------------------------------------------------------------------------ > > Key: ISPN-7104 > URL: https://issues.jboss.org/browse/ISPN-7104 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.4.Final, 9.2.1.Final > Reporter: Vladimir Dzhuvinov > Assignee: William Burns > Priority: Critical > Attachments: RemoveInInvalidationModeTest.java > > > The cache `remove` method occasionally fails to return the removed value, and returns `null`. > Observed in two node setup in invalidation mode, with a configured cache store (Redis). > Tests reveal that about 40% of the times the method returns `null`, the remaining 60% the removed value is correctly returned. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9100) Make Infinispan build with JDK 10

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-9100: ------------------------------------- Summary: Make Infinispan build with JDK 10 Key: ISPN-9100 URL: https://issues.jboss.org/browse/ISPN-9100 Project: Infinispan Issue Type: Enhancement Components: Build Affects Versions: 9.3.0.Alpha1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.3.0.Beta1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8234) Add support for @Spatial, @Latitude, @Longitude annotations in protobuf schema

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8234?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8234: ---------------------------------- Summary: Add support for @Spatial, @Latitude, @Longitude annotations in protobuf schema (was: Add support for @Spatial, @Lattitude, @Longitude annotations in protobuf schema) > Add support for @Spatial, @Latitude, @Longitude annotations in protobuf schema > ------------------------------------------------------------------------------ > > Key: ISPN-8234 > URL: https://issues.jboss.org/browse/ISPN-8234 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.3.0.Final > > > These annotations must behave identically to their Hibernate Search counterparts defined in org.hibernate.search.annotations package. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9002) LocalModeNoPassivationTest.testValuesWithEvictedEntries random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9002?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-9002: ------------------------------------ [~william.burns] maybe not related to the failure, but the test doesn't set any eviction strategy, and according to the log it should be using {{NONE}}: {noformat} 18:28:12,290 DEBUG (testng-Test:[]) [MemoryConfigurationBuilder] Max entries configured (150) without eviction strategy. Eviction strategy overridden to NONE {noformat} The javadoc of {{NONE}} says "nothing is done by the cache", but the data container iteration always returns only 150 entries out of 300, so maybe the javadoc is wrong? > LocalModeNoPassivationTest.testValuesWithEvictedEntries random failures > ----------------------------------------------------------------------- > > Key: ISPN-9002 > URL: https://issues.jboss.org/browse/ISPN-9002 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.Final > Reporter: Dan Berindei > Assignee: William Burns > Labels: testsuite_stability > Fix For: 9.3.0.Beta1 > > Attachments: LocalModeNoPassivationTest_ISPN-8962_preferavailabilitystrategy_20180327.log.gz > > > {noformat} > 12:59:16,370 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.persistence.LocalModeNoPassivationTest.testValuesWithEvictedEntries > java.lang.AssertionError: Value: 247 was not found! > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.9.9.jar:?] > at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) ~[testng-6.9.9.jar:?] > at org.infinispan.persistence.LocalModePassivationTest.testValuesWithEvictedEntries(LocalModePassivationTest.java:203) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8234) Add support for @Spatial, @Lattitude, @Longitude annotations in protobuf schema

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8234?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8234: ---------------------------------- Sprint: Sprint 9.3.0.Beta1 > Add support for @Spatial, @Lattitude, @Longitude annotations in protobuf schema > ------------------------------------------------------------------------------- > > Key: ISPN-8234 > URL: https://issues.jboss.org/browse/ISPN-8234 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.3.0.Final > > > These annotations must behave identically to their Hibernate Search counterparts defined in org.hibernate.search.annotations package. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8008) Add Fault-tolerance to write-behind stores

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8008?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8008: ---------------------------------- Sprint: Sprint 9.3.0.Beta1 > Add Fault-tolerance to write-behind stores > ------------------------------------------ > > Key: ISPN-8008 > URL: https://issues.jboss.org/browse/ISPN-8008 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > Currently when a store is configured to be write-behind, three attempts are made to write the queued modifications to the store. If all three attempts fail, then this error is simply logged and the modifications are never written to the store. > We should allow users to configure a write-behind store so that: In the event that a write-behind fails, further operations on the cache are not allowed and the modifications which failed to write to the store are queued indefinitely. Once the underlying store becomes available, the queued modifications should be written and then the cache should become available. > To determine whether a store has become available again, the AsyncCacheWriter will have to poll the store's availability. Currently the CacheWriter interface does not allow such behaviour, therefore there are two options: > * Attempt a write and catch an exception if the store is not currently available > * Add a method to return the current status of a store to the CacheWriter interface -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9086) Improve logging of topology updates

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9086?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9086: ------------------------------- Sprint: Sprint 9.3.0.Beta1 > Improve logging of topology updates > ----------------------------------- > > Key: ISPN-9086 > URL: https://issues.jboss.org/browse/ISPN-9086 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.3.0.Beta1 > > > Rebalance confirmations are logged with the event logger, but topology updates aren't. It should be the other way around, because the number of confirmations grows with the cluster size, and the number of topology updates only depends on the number of caches and joiners/leavers. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018