November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-7008) IllegalLifeCycleStateException from BlockingRunnable.isReady() escapes to originator

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-7008?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7008: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > IllegalLifeCycleStateException from BlockingRunnable.isReady() escapes to originator > ------------------------------------------------------------------------------------ > > Key: ISPN-7008 > URL: https://issues.jboss.org/browse/ISPN-7008 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.4.Final, 9.0.0.Alpha4 > Reporter: Dan Berindei > Priority: Major > Fix For: 9.4.3.Final > > > The ISPN-5539 fix caught {{IllegalLifecycleStateException}} in {{BlockingRunnable.run()}} and sent a {{CacheNotFoundResponse}} to the originator instead. However, exceptions thrown from {{BlockingRunnable.isReady()}} are not caught, and are instead sent back to the originator. An example stack trace is available in the WFLY-7029 description. > In this case, the exception was thrown directly when the inbound invocation handler tried to submit the command to the remote commands executor. But I see a related problem in {{BlockingTaskAwareExecutorServiceImpl.ControllerThread.run()}}, which stops with the first exception from {{isReady()}}. For {{IllegalLifecycleStateException}} it's probably ok, but for other exceptions it should continue processing new tasks. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6968) Clarify Query DSL error message regarding number format

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6968?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6968: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Clarify Query DSL error message regarding number format > ------------------------------------------------------- > > Key: ISPN-6968 > URL: https://issues.jboss.org/browse/ISPN-6968 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 8.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.3.Final > > > The query: > {code} > Query query = queryFactory.from(User.class) > .select(property("name"), count("age")) > .having("age").gte(2.3) > .toBuilder().groupBy("name") > .build(); > List<Object[]> list = query.list(); > {code} > will result in an error: > {code} > org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=13 returned server error (status=0x85): org.hibernate.hql.ParsingException: ISPN028505: Invalid numeric literal '2.3' > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:343) > {code} > This is a bit confusing because it does not clearly state that an integer is expected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6965) Throw UnsupportedOperation exceptions in RemoteCache for unimplemented methods of ConcurrentMap

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6965?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6965: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Throw UnsupportedOperation exceptions in RemoteCache for unimplemented methods of ConcurrentMap > ----------------------------------------------------------------------------------------------- > > Key: ISPN-6965 > URL: https://issues.jboss.org/browse/ISPN-6965 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Sanne Grinovero > Priority: Major > Fix For: 9.4.3.Final > > > The {{RemoteCache}} class inherits several methods from {{ConcurrentMap}} which are not overriden and won't work as expected, or are not safe for concurrent usage. > These should at least throw an exception, and ideally be documented as not-implemented in the javadocs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6960) Add xor logic operator to query DSL

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6960?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6960: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Add xor logic operator to query DSL > ----------------------------------- > > Key: ISPN-6960 > URL: https://issues.jboss.org/browse/ISPN-6960 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7159) CompleteShutdownDistRetryTest.testRetryAfterCompleteShutdown random failures

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-7159?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7159: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > CompleteShutdownDistRetryTest.testRetryAfterCompleteShutdown random failures > ---------------------------------------------------------------------------- > > Key: ISPN-7159 > URL: https://issues.jboss.org/browse/ISPN-7159 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.0.0.Alpha4 > Reporter: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 9.4.3.Final > > > {noformat} > java.lang.AssertionError: expected:<two> but was:<null> > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:101) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:108) > at org.infinispan.client.hotrod.retry.CompleteShutdownDistRetryTest.testRetryAfterCompleteShutdown(CompleteShutdownDistRetryTest.java:58) > {noformat} > I think the problem is that killing node 0 can make node 2's key move from node 2 to node 1, and then it's lost after node 1 is also killed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7139) Consistent prefix in property names of Hot Rod client configurations

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-7139?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7139: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Consistent prefix in property names of Hot Rod client configurations > -------------------------------------------------------------------- > > Key: ISPN-7139 > URL: https://issues.jboss.org/browse/ISPN-7139 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Remote Protocols > Reporter: Sanne Grinovero > Priority: Major > Fix For: 9.4.3.Final > > > Most Hot Rod configuration properties use the prefix {{infinispan.client.hotrod.}} which makes it easy to recognize them. > Some properties don't use the prefix though, such as all those related to connection pooling, e.g. {{maxActive}}, {{maxTotal}}, .. > This makes it hard to read Hot Rod specific configuration properties from alternative sources. In particular we'd like to embed such properties in an Hibernate configuration file (for Hibernate OGM) but the fact that some properties need special handling forces us to keep a list of these to have special care, rather than being able to use a prefix like it is done in most such cases. > It should be easy to prefix all the properties, and deprecate the names. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7117) ContinuousQuery.addContinuousQueryListener should fail if cache is async

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-7117?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7117: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > ContinuousQuery.addContinuousQueryListener should fail if cache is async > ------------------------------------------------------------------------ > > Key: ISPN-7117 > URL: https://issues.jboss.org/browse/ISPN-7117 > Project: Infinispan > Issue Type: Bug > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7061) Allow using HOST header for routing in to REST interface

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-7061?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7061: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Allow using HOST header for routing in to REST interface > -------------------------------------------------------- > > Key: ISPN-7061 > URL: https://issues.jboss.org/browse/ISPN-7061 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Sebastian Łaskawiec > Priority: Major > Fix For: 9.4.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7057) Refactor StatsChannelHandler to support null transport

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-7057?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7057: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Refactor StatsChannelHandler to support null transport > ------------------------------------------------------ > > Key: ISPN-7057 > URL: https://issues.jboss.org/browse/ISPN-7057 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Sebastian Łaskawiec > Priority: Major > Fix For: 9.4.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7470) Distributed executor does not fail over unless future.get() is called

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-7470?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7470: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Distributed executor does not fail over unless future.get() is called > --------------------------------------------------------------------- > > Key: ISPN-7470 > URL: https://issues.jboss.org/browse/ISPN-7470 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.6.Final, 9.0.0.CR1 > Reporter: Dan Berindei > Assignee: William Burns > Priority: Major > Fix For: 9.4.3.Final > > > After ISPN-6392, {{DistributedExecutorService.submit(...)}} nominally returns a {{CompletableFuture}}. However, it doesn't behave like a regular {{CompletableFuture}}, because it doesn't run the failure policy until the user calls {{future.get()}}. > {{future.isComplete()}} will return {{true}} before running the failure policy, and {{future.whenComplete(callback)}} will also execute the callback before running the failure policy. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 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 2018