March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5806) Add transaction support for Functional API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5806?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5806: ---------------------------------- Fix Version/s: (was: 8.2.0.Final) > Add transaction support for Functional API > ------------------------------------------ > > Key: ISPN-5806 > URL: https://issues.jboss.org/browse/ISPN-5806 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > A local cache with batching enabled produces this: > {code:java} > java.lang.IllegalArgumentException: Cannot create a transactional > context without a valid Transaction instance. > at org.infinispan.context.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:69) > at org.infinispan.context.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:63) > at org.infinispan.functional.impl.ReadWriteMapImpl.eval(ReadWriteMapImpl.java:56) > at org.infinispan.lucene.impl.FileListOperations.addFileName(FileListOperations.java:60) > (<-- experimental uncommitted code here) > {code} > For single operations that carry no transaction context, don't try to start a transaction and create a transactional context. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6323) Cluster startup hangs indefinitely in client-server mode

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/ISPN-6323?page=com.atlassian.jira.plugin.... ] Bela Ban commented on ISPN-6323: -------------------------------- Note that the NPE shown in {{UNICAST3}} is from delivering the message to the application (Infinispan). > Cluster startup hangs indefinitely in client-server mode > -------------------------------------------------------- > > Key: ISPN-6323 > URL: https://issues.jboss.org/browse/ISPN-6323 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.0.CR1 > Reporter: Matej Čimbora > Assignee: Pedro Ruivo > Priority: Blocker > > The issue was reliably reproduced on a cluster of 64 nodes with default clustered.xml configuration. The nodes receive a view and hang. Coordinator's log is cluttered with CacheNotFoundResponse & JGroups NPE's (included below). Other nodes just receive replication timeout while getting rebalancing status. > Thread dump (coordinator): https://gist.github.com/mcimbora/b65914bcd8141427fbf4 > Exceptions (coordinator): https://gist.github.com/mcimbora/0dd9a5b53344c1cdb18b > Exceptions(other nodes): https://gist.github.com/mcimbora/49d8b9f1b983d17ca5b1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6319) Ignore TransportException when closing the RemoteIterator

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6319?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6319: ------------------------------------ Status: Open (was: New) > Ignore TransportException when closing the RemoteIterator > --------------------------------------------------------- > > Key: ISPN-6319 > URL: https://issues.jboss.org/browse/ISPN-6319 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 8.2.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.0.Final > > > If right after finishing an iteration but before closing the iterator the server goes down, the RemoteIterator should not throw an exception but rather log a warn. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6319) Ignore TransportException when closing the RemoteIterator

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6319?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6319: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4076 > Ignore TransportException when closing the RemoteIterator > --------------------------------------------------------- > > Key: ISPN-6319 > URL: https://issues.jboss.org/browse/ISPN-6319 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 8.2.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.0.Final > > > If right after finishing an iteration but before closing the iterator the server goes down, the RemoteIterator should not throw an exception but rather log a warn. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6323) Cluster startup hangs indefinitely in client-server mode

by Matej Čimbora (JIRA)

Matej Čimbora created ISPN-6323: ----------------------------------- Summary: Cluster startup hangs indefinitely in client-server mode Key: ISPN-6323 URL: https://issues.jboss.org/browse/ISPN-6323 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 8.2.0.CR1 Reporter: Matej Čimbora Assignee: Pedro Ruivo Priority: Blocker The issue was reliably reproduced on a cluster of 64 nodes with default clustered.xml configuration. The nodes receive a view and hang. Coordinator's log is cluttered with CacheNotFoundResponse & JGroups NPE's (included below). Other nodes just receive replication timeout while getting rebalancing status. Thread dump (coordinator): https://gist.github.com/mcimbora/b65914bcd8141427fbf4 Exceptions (coordinator): https://gist.github.com/mcimbora/0dd9a5b53344c1cdb18b Exceptions(other nodes): https://gist.github.com/mcimbora/49d8b9f1b983d17ca5b1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6320) Improve stability of ClientEventsOOMTest

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6320?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6320: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done integrated. Thanks [~sebastian.laskawiec]! > Improve stability of ClientEventsOOMTest > ---------------------------------------- > > Key: ISPN-6320 > URL: https://issues.jboss.org/browse/ISPN-6320 > Project: Infinispan > Issue Type: Bug > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Trivial > Fix For: 8.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6311) Disable ExecTest.testRemoteMapReduceWithStreams until it is fixed

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6311?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6311: -------------------------------- Summary: Disable ExecTest.testRemoteMapReduceWithStreams until it is fixed (was: ExecTest.testRemoteMapReduceWithStreams test is failing) > Disable ExecTest.testRemoteMapReduceWithStreams until it is fixed > ----------------------------------------------------------------- > > Key: ISPN-6311 > URL: https://issues.jboss.org/browse/ISPN-6311 > Project: Infinispan > Issue Type: Task > Components: Tasks > Reporter: Anna Manukyan > Assignee: Anna Manukyan > Fix For: 8.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Dan Berindei (JIRA)

Dan Berindei created ISPN-6322: ---------------------------------- Summary: 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.1.2.Final, 8.2.0.CR1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 8.2.0.Final 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6321) Adding new cache to newly created cache container throws error

by Martin Gencur (JIRA)

Martin Gencur created ISPN-6321: ----------------------------------- Summary: Adding new cache to newly created cache container throws error Key: ISPN-6321 URL: https://issues.jboss.org/browse/ISPN-6321 Project: Infinispan Issue Type: Bug Components: CLI, Server Affects Versions: 8.2.0.CR1 Reporter: Martin Gencur Steps to reproduce: 1) created new container {code} /profile=clustered/subsystem=datagrid-infinispan/cache-container=local:add(default-cache=localTestCache,statistics=true) {code} 2) create new CONFIGURATIONS object {code} /profile=clustered/subsystem=datagrid-infinispan/cache-container=local/configurations=CONFIGURATIONS:add() {code} 3) create new configuration template {code} /profile=clustered/subsystem=datagrid-infinispan/cache-container=local/configurations=CONFIGURATIONS/local-cache-configuration=localTemplate:add(start=EAGER)" {code} 4) create the cache itself {code} /profile=clustered/subsystem=datagrid-infinispan/cache-container=local/local-cache=localTestCache:add(configuration=localTemplate,start=EAGER)" {code} The resulting error: {code} 17:37:54,942 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 33) WFLYCTL0013: Operation ("add") failed - address: ([ [Server:server-one] ("subsystem" => "datagrid-infinispan"), [Server:server-one] ("cache-container" => "local"), [Server:server-one] ("local-cache" => "localTestCache") [Server:server-one] ]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { [Server:server-one] "Services that were unable to start:" => ["jboss.datagrid-infinispan.local.localTestCache"], [Server:server-one] "Services that may be the cause:" => [ [Server:server-one] "jboss.datagrid-infinispan.local.config.thread-pool.async-operations", [Server:server-one] "jboss.datagrid-infinispan.local.config.thread-pool.expiration", [Server:server-one] "jboss.datagrid-infinispan.local.config.thread-pool.listener", [Server:server-one] "jboss.datagrid-infinispan.local.config.thread-pool.persistence", [Server:server-one] "jboss.datagrid-infinispan.local.config.thread-pool.remote-command", [Server:server-one] "jboss.datagrid-infinispan.local.config.thread-pool.replication-queue", [Server:server-one] "jboss.datagrid-infinispan.local.config.thread-pool.state-transfer", [Server:server-one] "jboss.datagrid-infinispan.local.config.thread-pool.transport" [Server:server-one] ] [Server:server-one] }} {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6318) Cleanup AbstractAuthentication tests

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6318?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6318: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Final Resolution: Done > Cleanup AbstractAuthentication tests > ------------------------------------ > > Key: ISPN-6318 > URL: https://issues.jboss.org/browse/ISPN-6318 > Project: Infinispan > Issue Type: Task > Components: Security, Test Suite - Core > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 8.2.0.Final > > > Test using {{adminCache}} and {{writerCache}} seems to be completely useless as these caches are not secured. Remote these tests from {{AbstractAuthentication}} > Thanks [~dan.berindei] for spotting this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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