April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6493) HotRod OAuth2 SASL support

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-6493: ------------------------------------- Summary: HotRod OAuth2 SASL support Key: ISPN-6493 URL: https://issues.jboss.org/browse/ISPN-6493 Project: Infinispan Issue Type: Enhancement Components: Security, Server Reporter: Tristan Tarrant We could add support for OAuth 2.0 support to both client and server provided we can get Sasl*Factory support -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6492) Remove unused log messages from HR client logger

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-6492?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-6492: ---------------------------------- Status: Open (was: New) > Remove unused log messages from HR client logger > ------------------------------------------------ > > Key: ISPN-6492 > URL: https://issues.jboss.org/browse/ISPN-6492 > Project: Infinispan > Issue Type: Task > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Priority: Minor > > There is couple of unused logger messages in {{org.infinispan.client.hotrod.logging.Log}} which can be removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6492) Remove unused log messages from HR client logger

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-6492?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-6492: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4230 > Remove unused log messages from HR client logger > ------------------------------------------------ > > Key: ISPN-6492 > URL: https://issues.jboss.org/browse/ISPN-6492 > Project: Infinispan > Issue Type: Task > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Priority: Minor > > There is couple of unused logger messages in {{org.infinispan.client.hotrod.logging.Log}} which can be removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6492) Remove unused log messages from HR client logger

by Vojtech Juranek (JIRA)

Vojtech Juranek created ISPN-6492: ------------------------------------- Summary: Remove unused log messages from HR client logger Key: ISPN-6492 URL: https://issues.jboss.org/browse/ISPN-6492 Project: Infinispan Issue Type: Task Reporter: Vojtech Juranek Assignee: Vojtech Juranek Priority: Minor There is couple of unused logger messages in {{org.infinispan.client.hotrod.logging.Log}} which can be removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5009) Upgrade server base to WildFly 9.0.0.Beta2

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5009?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-5009. --------------------------------- Resolution: Out of Date > Upgrade server base to WildFly 9.0.0.Beta2 > ------------------------------------------ > > Key: ISPN-5009 > URL: https://issues.jboss.org/browse/ISPN-5009 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build process, Server > Affects Versions: 7.0.2.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Alpha2 > > > Originally it was meant to upgrade to Wildfly 8.2.0.Final but some issues where found. Upgrade still needed but upgrading to 9.0.0.Beta2 which solves issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6328) Improper configuration of marshalling can lead to com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6328?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6328: ---------------------------------- Fix Version/s: (was: 9.0.0.Alpha2) > Improper configuration of marshalling can lead to com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero) > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-6328 > URL: https://issues.jboss.org/browse/ISPN-6328 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 8.2.0.CR1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > Running queries on a remote cache that was previously populated by an app that did not use protobuf marshalling should be allowed, and all those entities that were not encoded using protobuf should be ignored by the query engine and a warning should be logged instructing the user about the potential issue and how to fix the configuration. > The current behaviour in this case is not user friendly, especially in case of non-indexed query. An error is thrown during query evaluation: "com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero)." which indicates the unmarshalling of the queried entities is not possible. The actual cause of the bad encoding should be explained to the user and no exception should be thrown as if the type of entities does not match the requested type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6297) Move ConcurrentHashSet to infinispan-common

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6297?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6297: ---------------------------------- Fix Version/s: (was: 9.0.0.Alpha2) > Move ConcurrentHashSet to infinispan-common > ------------------------------------------- > > Key: ISPN-6297 > URL: https://issues.jboss.org/browse/ISPN-6297 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6285) SharedReplMassIndexTest hanging during cluster shutdown

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6285?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6285: ---------------------------------- Fix Version/s: (was: 9.0.0.Alpha2) > SharedReplMassIndexTest hanging during cluster shutdown > ------------------------------------------------------- > > Key: ISPN-6285 > URL: https://issues.jboss.org/browse/ISPN-6285 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Query > Affects Versions: 8.2.0.Beta2 > Reporter: Dan Berindei > Labels: testsuite_stability > > No logs for now, just a log from CI showing the query test suite hanging for 2+ hours, and this is the only active thread at the end: > {noformat} > "testng-SharedReplMassIndexTest" #15 prio=5 os_prio=0 tid=0x00007fc4a07ca000 nid=0x7314 waiting on condition [0x00007fc465efb000] > java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000d9d092b8> (a java.util.concurrent.CountDownLatch$Sync) > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) > at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) > at org.hibernate.search.backend.impl.lucene.SyncWorkProcessor.shutdown(SyncWorkProcessor.java:117) > at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueProcessor.close(LuceneBackendQueueProcessor.java:69) > at org.infinispan.query.indexmanager.LocalIndexingBackend.flushAndClose(LocalIndexingBackend.java:48) > at org.infinispan.query.indexmanager.ClusteredSwitchingBackend.closeBackend(ClusteredSwitchingBackend.java:227) > at org.infinispan.query.indexmanager.ClusteredSwitchingBackend.shutdown(ClusteredSwitchingBackend.java:216) > at org.infinispan.query.indexmanager.InfinispanBackendQueueProcessor.close(InfinispanBackendQueueProcessor.java:79) > at org.hibernate.search.indexes.spi.DirectoryBasedIndexManager.destroy(DirectoryBasedIndexManager.java:78) > at org.hibernate.search.indexes.impl.IndexManagerHolder.stop(IndexManagerHolder.java:197) > - locked <0x00000000a3832138> (a org.hibernate.search.indexes.impl.IndexManagerHolder) > at org.hibernate.search.engine.impl.ImmutableSearchFactory.close(ImmutableSearchFactory.java:230) > at org.hibernate.search.engine.impl.MutableSearchFactory.close(MutableSearchFactory.java:137) > at org.infinispan.query.impl.LifecycleManager.cacheStopping(LifecycleManager.java:296) > at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:244) > at org.infinispan.cache.impl.CacheImpl.stop(CacheImpl.java:869) > at org.infinispan.cache.impl.CacheImpl.stop(CacheImpl.java:864) > at org.infinispan.test.TestingUtil.killCaches(TestingUtil.java:798) > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:633) > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:626) > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:622) > at org.infinispan.test.MultipleCacheManagersTest.destroy(MultipleCacheManagersTest.java:87) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138) > at org.testng.internal.TestMethodWorker.invokeAfterClassMethods(TestMethodWorker.java:225) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:114) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:38) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6283) Upgrade to Shade plugin 3.0

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6283?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6283: ---------------------------------- Fix Version/s: (was: 9.0.0.Alpha2) > Upgrade to Shade plugin 3.0 > --------------------------- > > Key: ISPN-6283 > URL: https://issues.jboss.org/browse/ISPN-6283 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Minor > > Since we are blocked with MSHADE-182, we need to wait till Shade plugin 3.0 is released -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4722) CLI remove is not cluster-wide

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4722?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4722: ---------------------------------- Fix Version/s: (was: 9.0.0.Alpha2) > CLI remove is not cluster-wide > ------------------------------ > > Key: ISPN-4722 > URL: https://issues.jboss.org/browse/ISPN-4722 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 6.0.2.Final, 7.0.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Tristan Tarrant > > In CLI, the "remove" command does not delete entries in all nodes of a clustered environment, only the local copy. However, the "put" command does write in all nodes. Is it the expected behavior? See example below: > {code} > node 1 > put k1 v1 > get k1 -> v1 > node 2 > get k1 -> v1 > node 1 > remove k1 > get k1 -> null > node 2 > get k1 -> v1 > {code} > I know that these commands provided by CLI are not used in real world, but they are useful to demonstrate the correct configuration of a JDG cluster. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 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 April 2016