February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-6192) Short-term memory leak caused by RPCs that complete prior to their timeout

by Paul Ferraro (JIRA)

Paul Ferraro created ISPN-6192: ---------------------------------- Summary: Short-term memory leak caused by RPCs that complete prior to their timeout Key: ISPN-6192 URL: https://issues.jboss.org/browse/ISPN-6192 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 8.1.1.Final, 8.2.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Blocker The CommandAwareRpcDispatcher uses the timeout executor to trigger the cancellation of an async rpc after some timeout. However, in the event that the command executes prior to the timeout (i.e. most of the time), the task remains in the timeout executor's queue. Consequently, the reference to the RspListFuture/SingleResponseFuture will remain in the executor's queue unnecessarily for the duration of the timeout. Using ScheduledThreadPoolExecutor.setRemoveOnCancelPolicy(true) should fix the problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6183) Initial state transfer fails with unexpected timeout

by Vladimir Dzhuvinov (JIRA)

[ https://issues.jboss.org/browse/ISPN-6183?page=com.atlassian.jira.plugin.... ] Vladimir Dzhuvinov commented on ISPN-6183: ------------------------------------------ Additional JGroups settings passed in as properties: -Djava.net.preferIPv4Stack=true -Djgroups.fd_sock.start_port=7900 -Djgroups.tcp.port=7800 > Initial state transfer fails with unexpected timeout > ---------------------------------------------------- > > Key: ISPN-6183 > URL: https://issues.jboss.org/browse/ISPN-6183 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 7.2.5.Final > Environment: Java 7 on AWS EC2 > Reporter: Vladimir Dzhuvinov > Attachments: default-jgroups-s3ping.xml, state-transfer-timeout-stack-trace.txt > > > Hi guys, > I would like to report a somewhat odd issue with initial state transfer. It was observed in two instances - an Infinispan 7.2.5 cluster with 2 nodes and an Infinispan 7.2.5 cluster with 6 nodes. The two clusters had been running for 2 weeks, the smaller for dev purposes with very light load - about a dozen cached objects. Upon adding an extra node an initial state transfer exception was encountered with both clusters, after about 4 minutes which is the default timeout setting for such situations. Several attempts were made to add a new node, incl. one with increased timeout (10 mins), but state transfer would still not complete, and throw an exception: > {code:java} > "message": "Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.Exception on object of type StateTransferManagerImpl", > "name": "org.infinispan.commons.CacheException", > "cause": { > "commonElementCount": 25, > "localizedMessage": "Initial state transfer timed out for cache authzStore.codeMap on ip-10-180-242-223-40643", > "message": "Initial state transfer timed out for cache authzStore.codeMap on ip-10-180-242-223-40643", > "name": "org.infinispan.commons.CacheException", > "extendedStackTrace": [ > { > "class": "org.infinispan.statetransfer.StateTransferManagerImpl", > "method": "waitForInitialStateTransferToComplete", > "file": "StateTransferManagerImpl.java", > "line": 222, > "exact": false, > "location": "StateTransferManagerImpl.class", > "version": "?" > }, > {code} > The JMX console reported "stateTransferInProgress=true" and "joinComplete=true". > The original clusters where then shut down and started again together with the new node, after which the clusters were successfully formed. > Attached is the exception stack trace and the JGroups config (based on the stock S3 ping). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5868) Infinispan Server CLI container command doesn't work

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-5868?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-5868: -------------------------------- Status: Open (was: New) > Infinispan Server CLI container command doesn't work > ---------------------------------------------------- > > Key: ISPN-5868 > URL: https://issues.jboss.org/browse/ISPN-5868 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.1.Final > Reporter: Karl von Randow > Assignee: Martin Gencur > > The Infinispan Server CLI has a "container" command which doesn't appear to work anymore under 8.0.1. I _suspect_ it's because the Infinispan subsystem was renamed from "infinispan" to "datagrid-infinispan", however I can't find where that change should be made! It appears it should be in the CLI Connection implementation, but I can't for the life of me find the HTTP Connection that I believe is being used in this case. > If someone can point me to the right class I'd be happy to change and test the fix. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5868) Infinispan Server CLI container command doesn't work

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-5868?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-5868: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3990 > Infinispan Server CLI container command doesn't work > ---------------------------------------------------- > > Key: ISPN-5868 > URL: https://issues.jboss.org/browse/ISPN-5868 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.1.Final > Reporter: Karl von Randow > Assignee: Martin Gencur > > The Infinispan Server CLI has a "container" command which doesn't appear to work anymore under 8.0.1. I _suspect_ it's because the Infinispan subsystem was renamed from "infinispan" to "datagrid-infinispan", however I can't find where that change should be made! It appears it should be in the CLI Connection implementation, but I can't for the life of me find the HTTP Connection that I believe is being used in this case. > If someone can point me to the right class I'd be happy to change and test the fix. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5868) Infinispan Server CLI container command doesn't work

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-5868?page=com.atlassian.jira.plugin.... ] Martin Gencur reassigned ISPN-5868: ----------------------------------- Assignee: Martin Gencur (was: Tristan Tarrant) > Infinispan Server CLI container command doesn't work > ---------------------------------------------------- > > Key: ISPN-5868 > URL: https://issues.jboss.org/browse/ISPN-5868 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.1.Final > Reporter: Karl von Randow > Assignee: Martin Gencur > > The Infinispan Server CLI has a "container" command which doesn't appear to work anymore under 8.0.1. I _suspect_ it's because the Infinispan subsystem was renamed from "infinispan" to "datagrid-infinispan", however I can't find where that change should be made! It appears it should be in the CLI Connection implementation, but I can't for the life of me find the HTTP Connection that I believe is being used in this case. > If someone can point me to the right class I'd be happy to change and test the fix. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5784) [CLI] Cant connect to infinispan server via CLI

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-5784?page=com.atlassian.jira.plugin.... ] Martin Gencur closed ISPN-5784. ------------------------------- Resolution: Duplicate Issue Duplicates ISPN-5868 > [CLI] Cant connect to infinispan server via CLI > ----------------------------------------------- > > Key: ISPN-5784 > URL: https://issues.jboss.org/browse/ISPN-5784 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Final, 8.0.1.Final > Reporter: Vitalii Chepeliuk > Priority: Blocker > > *container* command does not show all available containers > [disconnected /] connect > [standalone@localhost:9990 /] container > [standalone@localhost:9990 /] > [standalone@localhost:9990 /] cd subsystem=datagrid-infinispan/cache-container=local > [standalone@localhost:9990 cache-container=local] > alias connection-info encoding ls roles unset > abort container end module rollback upgrade > batch create evict patch run-batch version > begin data-source get put set xa-data-source > cache deny grant pwd shutdown : > cd deploy help quit site > clear deployment-info history read-attribute start > clearcache deployment-overlay if read-operation stats > command echo info reload try > connect echo-dmr jdbc-driver-info replace undeploy > *cache* command shows no resources registered > [standalone@localhost:9990 cache-container=local] cache default > WFLYCTL0030: No resource definition is registered for address [ > ("subsystem" => "infinispan"), > ("cache-container" => "local") > ] > [standalone@localhost:9990 cache-container=local] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6128) Expose ProtoBuf Manager through DMR

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6128?page=com.atlassian.jira.plugin.... ] Adrian Nistor resolved ISPN-6128. --------------------------------- Resolution: Done > Expose ProtoBuf Manager through DMR > ----------------------------------- > > Key: ISPN-6128 > URL: https://issues.jboss.org/browse/ISPN-6128 > Project: Infinispan > Issue Type: Task > Components: Remote Querying, Server > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Fix For: 8.2.0.CR1, 8.2.0.Final > > > The ProtoBuf Manager should be exposed through the DMR as a child resource under cache-container nodes. The resource should expose a number of operations to list, get, set, remove installed schemas. > Example: > .../cache-container=container/protobuf-schemas=PROTOBUF-SCHEMAS > :list-schemas() > :get-schema(name=myschema) > :remove-schema(name=myschema) > :set-schema(name=myschema, schema-source=...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6191) Provide Externalizers for (Double|Long|Int)SummaryStatistics

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6191?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6191: -------------------------------- Status: Open (was: New) > Provide Externalizers for (Double|Long|Int)SummaryStatistics > ------------------------------------------------------------ > > Key: ISPN-6191 > URL: https://issues.jboss.org/browse/ISPN-6191 > Project: Infinispan > Issue Type: Enhancement > Reporter: William Burns > Assignee: William Burns > > The summary statistics classes are used directly by the new streams. Unfortunately they aren't Serializable by default, which can cause issues when using these methods in a distributed cache. > The summaryStatistics methods on the (Double|Long|Int)Stream use a hack of forcing an iterator to get these results, but this cannot be applied with the Collectors methods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6047) Deadlock when a prepare command is retried

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-6047?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-6047: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3988 > Deadlock when a prepare command is retried > ------------------------------------------ > > Key: ISPN-6047 > URL: https://issues.jboss.org/browse/ISPN-6047 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Fix For: 8.2.0.CR1 > > > Looks like the ISPN-5623 fix went too far, and now I found a test failure with the opposite behaviour: > 1. Remote prepare for {{txA}} acquires lock {{K}} > 2. Remote prepare for {{txB}} blocks waiting for lock {{K}} > 3. The topology changes, and the {{txA}} prepare is retried > 4. The {{txA}} prepare times out, because it waits for pending transaction {{txB}} to finish. > So we have to make {{txA}} somehow know that it already has the lock after it received an {{UnsureResponse}} for the prepare command, and skip waiting for pending transactions. > I found the problem in a random failure of {{DistributedFourNodesMapReduceTest}} on a local branch, but I'm not sure if my local changes (making SyncCHF the default CH factory) made it more likely. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6191) Provide Externalizers for (Double|Long|Int)SummaryStatistics

by William Burns (JIRA)

William Burns created ISPN-6191: ----------------------------------- Summary: Provide Externalizers for (Double|Long|Int)SummaryStatistics Key: ISPN-6191 URL: https://issues.jboss.org/browse/ISPN-6191 Project: Infinispan Issue Type: Enhancement Reporter: William Burns Assignee: William Burns The summary statistics classes are used directly by the new streams. Unfortunately they aren't Serializable by default, which can cause issues when using these methods in a distributed cache. The summaryStatistics methods on the (Double|Long|Int)Stream use a hack of forcing an iterator to get these results, but this cannot be applied with the Collectors methods. -- 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 February 2016