August 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6931) Cache container screen not shown if Connector removed

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6931?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6931: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/122 > Cache container screen not shown if Connector removed > ----------------------------------------------------- > > Key: ISPN-6931 > URL: https://issues.jboss.org/browse/ISPN-6931 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Alpha4, 8.2.3.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > If a connector, such as the Memcached connector, is removed then the Cache Containers screen is unable to load. This is due to the cluster-model.service.js trying to access an attribute of an undefined connector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6931) Cache container screen not shown if Connector removed

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-6931: ---------------------------------- Summary: Cache container screen not shown if Connector removed Key: ISPN-6931 URL: https://issues.jboss.org/browse/ISPN-6931 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 8.2.3.Final, 9.0.0.Alpha4 Reporter: Ryan Emerson Assignee: Ryan Emerson If a connector, such as the Memcached connector, is removed then the Cache Containers screen is unable to load. This is due to the cluster-model.service.js trying to access an attribute of an undefined connector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-445) Ensure that locks time out

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-445?page=com.atlassian.jira.plugin.s... ] Pedro Ruivo closed ISPN-445. ---------------------------- Resolution: Won't Fix It won't be done for the following reasons: * could make the stored data inconsistency if a thread advances without a lock. * locks in JDK does not allow to steal them from other threads. * full_xa + recovery allows a sysadmin to force a transaction rollback, releasing any locks. > Ensure that locks time out > -------------------------- > > Key: ISPN-445 > URL: https://issues.jboss.org/browse/ISPN-445 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Philippe Van Dyck > > When a lock is acquired, no mechanism ensure that it is reclaimed later. > So if for whatever reason the thread owning the lock is stuck in an endless loop or waiting for some resource, the entry is locked. This kind of situation could happen in cache stores trying to contact a remote storage. > The risk is quite high that other entries may be locked as well if you use lock stripping (default : TRUE) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6929) cloud.xml does not have kubernetes jgroups stack

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6929?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec closed ISPN-6929. ------------------------------------- Resolution: Cannot Reproduce Bug > cloud.xml does not have kubernetes jgroups stack > ------------------------------------------------- > > Key: ISPN-6929 > URL: https://issues.jboss.org/browse/ISPN-6929 > Project: Infinispan > Issue Type: Bug > Components: Cloud Integrations > Affects Versions: 9.0.0.Alpha4 > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-1947?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-1947: ----------------------------------------- Assignee: Sebastian Łaskawiec > Automate staging repository step in release script > -------------------------------------------------- > > Key: ISPN-1947 > URL: https://issues.jboss.org/browse/ISPN-1947 > Project: Infinispan > Issue Type: Task > Components: Build process > Reporter: Sanne Grinovero > Assignee: Sebastian Łaskawiec > Priority: Optional > > The Nexus staging plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) > https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-1947?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-1947: -------------------------------------- Priority: Critical (was: Optional) > Automate staging repository step in release script > -------------------------------------------------- > > Key: ISPN-1947 > URL: https://issues.jboss.org/browse/ISPN-1947 > Project: Infinispan > Issue Type: Task > Components: Build process > Reporter: Sanne Grinovero > Assignee: Sebastian Łaskawiec > Priority: Critical > > The Nexus staging plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) > https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4800) Server Web Management Interface

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4800?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4800: ------------------------------------- Assignee: Vladimir Blagojevic (was: Tristan Tarrant) > Server Web Management Interface > ------------------------------- > > Key: ISPN-4800 > URL: https://issues.jboss.org/browse/ISPN-4800 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Vladimir Blagojevic > > Implement a new web-based management interface capable of managing multiple clusters, nodes, caches. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3159) Implementing SERIALIZABLE isolation level based on GMU

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3159?page=com.atlassian.jira.plugin.... ] Work on ISPN-3159 stopped by Tristan Tarrant. --------------------------------------------- > Implementing SERIALIZABLE isolation level based on GMU > ------------------------------------------------------ > > Key: ISPN-3159 > URL: https://issues.jboss.org/browse/ISPN-3159 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > Implementation based in GMU, a Cloud-TM project research (www.cloudtm.eu). > GMU is a muti-version scheme that provides Update Serializability. It allows the read-only transaction to proceed without blocking, but they can observe an old value (but always a consistent value). > This scheme relies in Vector Clock to manage the snapshots to read and the transaction dependencies in each node in the cluster. > Also, it is a genuine scheme, i.e., only the nodes involved in the transaction (that contains data read or write) are involved in the transaction commit. > A paper describing GMU can be found here: http://ieeexplore.ieee.org/xpl/articleDetails.jsp?reload=true&arnumber=62... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1947?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-1947: ---------------------------------- Description: The Nexus staging plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven... was: The following plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) {code:xml} <plugin> <groupId>org.sonatype.plugins</groupId> <artifactId>nexus-maven-plugin</artifactId> <configuration> <nexusUrl>https://repository.jboss.org/nexus</nexusUrl> <automatic>true</automatic> </configuration> </plugin> {code} Goals are described at: https://repository.sonatype.org/content/sites/maven-sites/nexus-maven-plu... > Automate staging repository step in release script > -------------------------------------------------- > > Key: ISPN-1947 > URL: https://issues.jboss.org/browse/ISPN-1947 > Project: Infinispan > Issue Type: Task > Components: Build process > Reporter: Sanne Grinovero > Priority: Optional > > The Nexus staging plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) > https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1947?page=com.atlassian.jira.plugin.... ] Work on ISPN-1947 stopped by Tristan Tarrant. --------------------------------------------- > Automate staging repository step in release script > -------------------------------------------------- > > Key: ISPN-1947 > URL: https://issues.jboss.org/browse/ISPN-1947 > Project: Infinispan > Issue Type: Task > Components: Build process > Reporter: Sanne Grinovero > Priority: Optional > > The following plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) > {code:xml} > <plugin> > <groupId>org.sonatype.plugins</groupId> > <artifactId>nexus-maven-plugin</artifactId> > <configuration> > <nexusUrl>https://repository.jboss.org/nexus</nexusUrl> > <automatic>true</automatic> > </configuration> > </plugin> > {code} > Goals are described at: https://repository.sonatype.org/content/sites/maven-sites/nexus-maven-plu... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2016