March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6365) Update indexless query to use Stream

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6365: ----------------------------------- Summary: Update indexless query to use Stream Key: ISPN-6365 URL: https://issues.jboss.org/browse/ISPN-6365 Project: Infinispan Issue Type: Bug Components: Embedded Querying Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 9.0.0.Final, 9.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6365) Update indexless query to use Stream

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6365?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6365: -------------------------------- Status: Open (was: New) > Update indexless query to use Stream > ------------------------------------ > > Key: ISPN-6365 > URL: https://issues.jboss.org/browse/ISPN-6365 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6352) ClusterExecutor.submitConsumer swallows exceptions thrown by the consumer

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6352?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6352: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ClusterExecutor.submitConsumer swallows exceptions thrown by the consumer > ------------------------------------------------------------------------- > > Key: ISPN-6352 > URL: https://issues.jboss.org/browse/ISPN-6352 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: William Burns > Fix For: 9.0.0.Final, 8.2.1.Final > > > When the remote/local function throws an exception, the {{TriConsumer}} receives the exception as a parameter and can handle it. When the {{TriConsumer}} throws an exception, however, that exception is hidden from the caller. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6361) ClusteredCacheConfigurationIT.testQueueFlushIntervalMemcached random failures

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6361?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6361: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ClusteredCacheConfigurationIT.testQueueFlushIntervalMemcached random failures > ----------------------------------------------------------------------------- > > Key: ISPN-6361 > URL: https://issues.jboss.org/browse/ISPN-6361 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 9.0.0.Alpha1, 8.2.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6362) Infinispan Query DSL parser failure with inheritance

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6362?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6362: -------------------------------- Status: Open (was: New) > Infinispan Query DSL parser failure with inheritance > ---------------------------------------------------- > > Key: ISPN-6362 > URL: https://issues.jboss.org/browse/ISPN-6362 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > > As exemplified in the forum, the native DSL fails to build a query for a class who inherits an indexed field. An equivalent Hibernate Search query works -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6364) Report test failures on the fly in modules using JUnit

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6364?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6364: ------------------------------- Status: Open (was: New) > Report test failures on the fly in modules using JUnit > ------------------------------------------------------ > > Key: ISPN-6364 > URL: https://issues.jboss.org/browse/ISPN-6364 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core, Test Suite - Query, Test Suite - Server > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Alpha1 > > > Modules using TestNG for testing use {{UnitTestTestNGListener}} to report test start/finish during the build, making it possible to scan visually for test failures (or just progress). > Modules using JUnit should have this functionality as well. The {{server/integration/testsuite}} module already has a {{RunListener}} that reports the start of a test, it should report failures as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6364) Report test failures on the fly in modules using JUnit

by Dan Berindei (JIRA)

Dan Berindei created ISPN-6364: ---------------------------------- Summary: Report test failures on the fly in modules using JUnit Key: ISPN-6364 URL: https://issues.jboss.org/browse/ISPN-6364 Project: Infinispan Issue Type: Bug Components: Test Suite - Core, Test Suite - Query, Test Suite - Server Affects Versions: 8.2.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.0.0.Alpha1 Modules using TestNG for testing use {{UnitTestTestNGListener}} to report test start/finish during the build, making it possible to scan visually for test failures (or just progress). Modules using JUnit should have this functionality as well. The {{server/integration/testsuite}} module already has a {{RunListener}} that reports the start of a test, it should report failures as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6357) Deadlock during server start

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6357?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-6357: ------------------------------------ The fix for ISPN-6195 was incomplete. Because {{CacheNotFoundResponse.isSuccessful()}} returns {{false}}, {{ClusterTopologyManagerImpl.addResponseValue()}} still throws an exception if one of the other nodes hasn't started the Infinispan {{ForkChannel}} yet. > Deadlock during server start > ---------------------------- > > Key: ISPN-6357 > URL: https://issues.jboss.org/browse/ISPN-6357 > Project: Infinispan > Issue Type: Bug > Components: Core, Server > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Dan Berindei > Priority: Critical > Attachments: s0.txt, s1.txt, server1.txt, server2.txt > > > This happens frequently when starting servers in parallel, the more servers, the easier to reproduce. > Attached the stack trace of server1 and server2 after hanging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6357) Deadlock during server start

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6357?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6357: ------------------------------- Status: Open (was: New) > Deadlock during server start > ---------------------------- > > Key: ISPN-6357 > URL: https://issues.jboss.org/browse/ISPN-6357 > Project: Infinispan > Issue Type: Bug > Components: Core, Server > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Dan Berindei > Priority: Critical > Attachments: s0.txt, s1.txt, server1.txt, server2.txt > > > This happens frequently when starting servers in parallel, the more servers, the easier to reproduce. > Attached the stack trace of server1 and server2 after hanging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6322) Infinispan can miss incoming commands with JGroupsChannelLookup

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6322?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6322: ------------------------------- Status: Open (was: New) > Infinispan can miss incoming commands with JGroupsChannelLookup > --------------------------------------------------------------- > > Key: ISPN-6322 > URL: https://issues.jboss.org/browse/ISPN-6322 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.0.CR1, 8.1.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Alpha1 > > > Normally, the JGroupsTransport startup sequence goes like this: > # Create the {{Channel}} > # Create the {{CommandAwareRpcDispatcher}} and install it as an {{UpHandler}} > # Connect the channel > This way, every {{RequestCorrelator}} message received by the channel is passed up to {{CommandAwareRpcDispatcher}}, which executes the appropriate command. > When using a {{JGroupsChannelLookup}}, the lookup implementation is allowed to return a {{Channel}} instance that is already connected ({{shouldConnect() == false}}). That means there is now a window where the channel doesn't have an {{UpHandler}}, and messages sent to this node are discarded. > Normally a node only receives commands after it sent a join request to the coordinator. There are however a few exceptions: > # On startup, {[LocalTopologyManagerImpl}} sends the join request to the JGroups coordinator, which may not have the {{UpHandler}} yet. This seems to be responsible for the recent hanging in {{ConcurrentStartTest}}. We have a workaround here, to use a smaller timeout on the {{CacheTopologyControlCommand(JOIN)}} command, and retry it on {{TimeoutException}}. > # When a node becomes coordinator, {{ClusterTopologyManagerImpl}} broadcasts a {{GET_STATUS}} request to all cluster members, and expects a response from each of them. The same workaround with a smaller timeout and retries might work here. > # In replicated mode, write commands are broadcasted to all cluster members. There is some commented out code in {{RpcManagerImpl.invokeRemotelyAsync()}} that might fix it by only waiting for responses from the cache topology members. > We should consider deprecating {{JGroupsChannelLookup.shouldConnect()}} and requiring that the channel is only connected by {{JGroupsTransport}}. Assuming that works with {{ForkChannel}}, of course. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2016