January 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9915) JDBC publish Flowable should explicitly rollback connection

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9915?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9915: ------------------------------- Status: Open (was: New) > JDBC publish Flowable should explicitly rollback connection > ----------------------------------------------------------- > > Key: ISPN-9915 > URL: https://issues.jboss.org/browse/ISPN-9915 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.7.Final > > > The Flowable for the JDBC store publisher sets `autoCommit(false)` in order for pagination to work as expected, however we never explicitly call commit or rollback on the connection, therefore the exact behaviour is determined by the underlying connection pool. Instead we should explicitly call rollback() on the connection after the publisher has finished, because the operation is read only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9905) Rest store should retrieve created and lastUsed TS from server

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9905?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9905: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6594 > Rest store should retrieve created and lastUsed TS from server > -------------------------------------------------------------- > > Key: ISPN-9905 > URL: https://issues.jboss.org/browse/ISPN-9905 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores, REST > Affects Versions: 10.0.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > Currently the rest store simply sets the created and lastUsed entries to the current time of the node loading an entry, instead we should retrieve this value from the server if fetchMetadata is true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9905) Rest store should retrieve created and lastUsed TS from server

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9905?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9905: ------------------------------- Status: Open (was: New) > Rest store should retrieve created and lastUsed TS from server > -------------------------------------------------------------- > > Key: ISPN-9905 > URL: https://issues.jboss.org/browse/ISPN-9905 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores, REST > Affects Versions: 10.0.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > Currently the rest store simply sets the created and lastUsed entries to the current time of the node loading an entry, instead we should retrieve this value from the server if fetchMetadata is true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9657) Multimap jar is not OSGi compliant

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-9657?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reopened ISPN-9657: ------------------------------------ Not fully resolved > Multimap jar is not OSGi compliant > ---------------------------------- > > Key: ISPN-9657 > URL: https://issues.jboss.org/browse/ISPN-9657 > Project: Infinispan > Issue Type: Bug > Components: Multimap > Affects Versions: 9.4.0.Final > Reporter: Alain Picard > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1, 10.0.0.Final, 9.4.7.Final > > > Due to issues related to using the embedded jar (see [here|https://developer.jboss.org/message/986042#986042], when switching to individual jars, the multimap jar (infinispan-multimap-9.4.0.Final.jar) doesn't provide a valid OSGi manifest. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9657) Multimap jar is not OSGi compliant

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9657?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9657: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6637, https://github.com/infinispan/infinispan/pull/6638 (was: https://github.com/infinispan/infinispan/pull/6637) > Multimap jar is not OSGi compliant > ---------------------------------- > > Key: ISPN-9657 > URL: https://issues.jboss.org/browse/ISPN-9657 > Project: Infinispan > Issue Type: Bug > Components: Multimap > Affects Versions: 9.4.0.Final > Reporter: Alain Picard > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.7.Final > > > Due to issues related to using the embedded jar (see [here|https://developer.jboss.org/message/986042#986042], when switching to individual jars, the multimap jar (infinispan-multimap-9.4.0.Final.jar) doesn't provide a valid OSGi manifest. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9657) Multimap jar is not OSGi compliant

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9657?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9657: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6637 > Multimap jar is not OSGi compliant > ---------------------------------- > > Key: ISPN-9657 > URL: https://issues.jboss.org/browse/ISPN-9657 > Project: Infinispan > Issue Type: Bug > Components: Multimap > Affects Versions: 9.4.0.Final > Reporter: Alain Picard > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.7.Final > > > Due to issues related to using the embedded jar (see [here|https://developer.jboss.org/message/986042#986042], when switching to individual jars, the multimap jar (infinispan-multimap-9.4.0.Final.jar) doesn't provide a valid OSGi manifest. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9657) Multimap jar is not OSGi compliant

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9657?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9657: ------------------------------- Status: Open (was: New) > Multimap jar is not OSGi compliant > ---------------------------------- > > Key: ISPN-9657 > URL: https://issues.jboss.org/browse/ISPN-9657 > Project: Infinispan > Issue Type: Bug > Components: Multimap > Affects Versions: 9.4.0.Final > Reporter: Alain Picard > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.7.Final > > > Due to issues related to using the embedded jar (see [here|https://developer.jboss.org/message/986042#986042], when switching to individual jars, the multimap jar (infinispan-multimap-9.4.0.Final.jar) doesn't provide a valid OSGi manifest. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9801) ClusterTopologyManagerImpl hangs when restarting a node with FORK

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9801?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-9801: ------------------------------------- Master is integrated, just need PR for 9.4. > ClusterTopologyManagerImpl hangs when restarting a node with FORK > ----------------------------------------------------------------- > > Key: ISPN-9801 > URL: https://issues.jboss.org/browse/ISPN-9801 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Alpha1, 9.4.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.7.Final > > > When a server is restarted with `kill -9` or similar, both the old node and the new one can be in the JGroups view for a while. Normally this shouldn't be a problem, but sometimes the new node doesn't receive the {{HeartBeatCommand}} and the coordinator cannot process any new view updates. > {noformat} > 14:29:19,981 INFO (jgroups-12,Test-NodeA:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|4] (5) [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:19,982 TRACE (transport-thread-Test-NodeA-p4-t14:[ViewHandling]) [ClusterTopologyManagerImpl] Updating cluster members for all the caches. New list is [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:19,982 TRACE (transport-thread-Test-NodeA-p4-t14:[ViewHandling]) [JGroupsTransport] Test-NodeA sending request 9 to all: org.infinispan.topology.HeartBeatCommand@1163beb6 > 14:29:19,986 TRACE (jgroups-6,Test-NodeA:[]) [JGroupsTransport] Test-NodeA received response for request 9 from Test-NodeC: SuccessfulResponse(null) > 14:29:19,987 TRACE (jgroups-9,Test-NodeA:[]) [JGroupsTransport] Test-NodeA received response for request 9 from Test-NodeD: SuccessfulResponse(null) > 14:29:20,032 TRACE (jgroups-6,Test-NodeE:[]) [TCP_NIO2] Test-NodeE: received message batch of 1 messages from Test-NodeA > 14:29:20,032 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: message Test-NodeA::39 was added to queue (not yet server) > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: received Test-NodeA#38 > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: delivering Test-NodeA#38 > # not actually delivered :) > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [MFC] Test-NodeA used 5 credits, 1999995 remaining > 14:29:20,149 INFO (ForkThread-1,ForkChannelRestartTest:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|4] (5) [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:21,119 DEBUG (testng-Test-1:[]) [ForkChannelRestartTest] Stopping channel Test-NodeB > 14:29:23,319 INFO (VERIFY_SUSPECT.TimerThread-32,Test-NodeA:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|5] (4) [Test-NodeA, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:23,320 TRACE (remote-thread-Test-NodeA-p2-t1:[]) [MultiTargetRequest] Target Test-NodeB of request 9 left the cluster view > {noformat} > So far, it looks like it's a JGroups bug similar to JGRP-2294, but we need to investigate further. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9915) JDBC publish Flowable should explicitly rollback connection

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9915?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9915: ------------------------------- Sprint: Sprint 10.0.0.Beta1 > JDBC publish Flowable should explicitly rollback connection > ----------------------------------------------------------- > > Key: ISPN-9915 > URL: https://issues.jboss.org/browse/ISPN-9915 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.7.Final > > > The Flowable for the JDBC store publisher sets `autoCommit(false)` in order for pagination to work as expected, however we never explicitly call commit or rollback on the connection, therefore the exact behaviour is determined by the underlying connection pool. Instead we should explicitly call rollback() on the connection after the publisher has finished, because the operation is read only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9915) JDBC publish Flowable should explicitly rollback connection

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-9915: ---------------------------------- Summary: JDBC publish Flowable should explicitly rollback connection Key: ISPN-9915 URL: https://issues.jboss.org/browse/ISPN-9915 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 9.4.6.Final, 10.0.0.Alpha3 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.Beta1, 9.4.7.Final The Flowable for the JDBC store publisher sets `autoCommit(false)` in order for pagination to work as expected, however we never explicitly call commit or rollback on the connection, therefore the exact behaviour is determined by the underlying connection pool. Instead we should explicitly call rollback() on the connection after the publisher has finished, because the operation is read only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 January 2019