May 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6726) ContinuousQueryListener.resultJoining notifications generated by 'modify' operations contain the old value not the new one

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6726: ----------------------------------- Summary: ContinuousQueryListener.resultJoining notifications generated by 'modify' operations contain the old value not the new one Key: ISPN-6726 URL: https://issues.jboss.org/browse/ISPN-6726 Project: Infinispan Issue Type: Bug Components: Remote Querying Reporter: Adrian Nistor Assignee: Adrian Nistor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6700) Restart required dialog show only after editing distributed cache

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6700?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-6700. -------------------------------- Fix Version/s: 9.0.0.Alpha3 Resolution: Done > Restart required dialog show only after editing distributed cache > ----------------------------------------------------------------- > > Key: ISPN-6700 > URL: https://issues.jboss.org/browse/ISPN-6700 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.2.Final > Reporter: Jiří Holuša > Assignee: Ryan Emerson > Fix For: 9.0.0.Alpha3 > > > Page: Cache configuration page (select cache container -> select cache -> click Configuration) > When editing any property of replicated, local and invalidation cache, for example expiration lifespan. When I change somehow the value, right next to the input box, there appears: " (Undo) Restart needed". Then I click "Apply changes", a confirmation dialog pops up with text: "Update configuration template <cache>?", I click "Update" and it's done. I have to manually search for the option of restarting the cluster. > However, if I do it with distributed cache, after clicking "Update" in confirmation dialog, another dialog pops up with text: "Attributes changed require a restart of the affected servers. If you need to make additional configuration changes right now, consider restarting servers after the last change." with options "Restart now" and "Restart later". > IMHO this should be consistent and the latter option is correct. If restart is needed (as the tooltip says), console should offer it right away. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6705) Container does not restart after clicking "restart now" in Thread Pools tab

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6705?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-6705. -------------------------------- Fix Version/s: 9.0.0.Alpha3 Resolution: Done > Container does not restart after clicking "restart now" in Thread Pools tab > --------------------------------------------------------------------------- > > Key: ISPN-6705 > URL: https://issues.jboss.org/browse/ISPN-6705 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Minor > Fix For: 9.0.0.Alpha3 > > > Container configuration page "Thread pools" tab. > After changing a value e.g. "Async operation" -> "max threads" and -> click "save" -> click "Restart now" the container does not restart -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6723) Move common parser methods to an unversioned class so they can be used by external modules

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6723?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6723: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4384, https://github.com/infinispan/infinispan/pull/4383 > Move common parser methods to an unversioned class so they can be used by external modules > ------------------------------------------------------------------------------------------ > > Key: ISPN-6723 > URL: https://issues.jboss.org/browse/ISPN-6723 > Project: Infinispan > Issue Type: Task > Components: Configuration > Affects Versions: 8.1.4.Final, 8.2.2.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.1.5.Final, 8.2.3.Final > > > Before Infinispan 9, parsers were versioned forcing external modules (such as cachestores) to depend on a specific version. We should move these methods to a "Parser" class to remove this limitation -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6725) Enhance ContinuousQueryListener to receive events for updated results

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6725?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6725: -------------------------------- Status: Open (was: New) > Enhance ContinuousQueryListener to receive events for updated results > --------------------------------------------------------------------- > > Key: ISPN-6725 > URL: https://issues.jboss.org/browse/ISPN-6725 > Project: Infinispan > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final > > > Add method ContinuousQueryListener.resultUpdated(key, value) to receive events whenever a previous match gets updated (and continues to match the filter). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6725) Enhance ContinuousQueryListener to receive events for updated results

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6725: ----------------------------------- Summary: Enhance ContinuousQueryListener to receive events for updated results Key: ISPN-6725 URL: https://issues.jboss.org/browse/ISPN-6725 Project: Infinispan Issue Type: Enhancement Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 9.0.0.Final Add method ContinuousQueryListener.resultUpdated(key, value) to receive events whenever a previous match gets updated (and continues to match the filter). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-201) make JDBC cache store use DB transactions for commit/rollback

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-201?page=com.atlassian.jira.plugin.s... ] Ryan Emerson updated ISPN-201: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4382 > make JDBC cache store use DB transactions for commit/rollback > ------------------------------------------------------------- > > Key: ISPN-201 > URL: https://issues.jboss.org/browse/ISPN-201 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Mircea Markus > Assignee: Ryan Emerson > Labels: modshape > Fix For: 9.0.0.Final > > > current impl of JDBC cache store does not use DB transaction (nor local transactions/Connection.setAutocommit(false)) for storing the modifications created within a transaction. This might leave the store in an inconsistent state one operation fails during commit. This should be changed to either 1. use local transactions or 2. register the driver as an XAResource and rely on the TM to manage the boundaries. I would go for 1, as it would be more consistent with other CStore implementation (different cache store interceptor should be used for managing the 2'nd approach). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6723) Move common parser methods to an unversioned class so they can be used by external modules

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6723?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6723: ---------------------------------- Status: Open (was: New) > Move common parser methods to an unversioned class so they can be used by external modules > ------------------------------------------------------------------------------------------ > > Key: ISPN-6723 > URL: https://issues.jboss.org/browse/ISPN-6723 > Project: Infinispan > Issue Type: Task > Components: Configuration > Affects Versions: 8.1.4.Final, 8.2.2.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.1.5.Final, 8.2.3.Final > > > Before Infinispan 9, parsers were versioned forcing external modules (such as cachestores) to depend on a specific version. We should move these methods to a "Parser" class to remove this limitation -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6724) Modules scripting and infinispan directory provider use the same logging id range

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6724?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6724: -------------------------------- Fix Version/s: 9.0.0.Alpha3 > Modules scripting and infinispan directory provider use the same logging id range > --------------------------------------------------------------------------------- > > Key: ISPN-6724 > URL: https://issues.jboss.org/browse/ISPN-6724 > Project: Infinispan > Issue Type: Bug > Reporter: Adrian Nistor > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6724) Modules scripting and infinispan directory provider use the same logging id range

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6724: ----------------------------------- Summary: Modules scripting and infinispan directory provider use the same logging id range Key: ISPN-6724 URL: https://issues.jboss.org/browse/ISPN-6724 Project: Infinispan Issue Type: Bug Reporter: Adrian Nistor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2016