January 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6049) Calls to reflection API fail with enabled security manager; need to be run in privileged block

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-6049?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-6049: --------------------------------- Fix Version/s: (was: 8.2.0.Final) > Calls to reflection API fail with enabled security manager; need to be run in privileged block > ---------------------------------------------------------------------------------------------- > > Key: ISPN-6049 > URL: https://issues.jboss.org/browse/ISPN-6049 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.2.0.Beta1, 8.1.1.Final > > > Problematic are the calls that are originating in the unprivileged user code. For example: > org.infinispan.distribution.group.GroupManagerImpl.GroupMetadataImpl#getGroup > org.infinispan.distribution.group.GroupManagerImpl#createGroupMetadata > e.g. call stacks > https://gist.github.com/rhusar/e2ae371f852d926c5e13 > https://gist.github.com/rhusar/7411f9dc963bc9233eae > https://gist.github.com/rhusar/782743a551c8eef927a0 (security) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6114) Management console - node view - performance and caching activities are not calculated properly

by Roman Macor (JIRA)

Roman Macor created ISPN-6114: --------------------------------- Summary: Management console - node view - performance and caching activities are not calculated properly Key: ISPN-6114 URL: https://issues.jboss.org/browse/ISPN-6114 Project: Infinispan Issue Type: Bug Components: Console Reporter: Roman Macor Assignee: Vladimir Blagojevic Clusters tab -> click on cluster -> click on node After doing operations on cache that is deployed on node the statistics (e.g. #PUTS) still display 0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6049) Calls to reflection API fail with enabled security manager; need to be run in privileged block

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6049?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6049: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Beta1 Resolution: Done > Calls to reflection API fail with enabled security manager; need to be run in privileged block > ---------------------------------------------------------------------------------------------- > > Key: ISPN-6049 > URL: https://issues.jboss.org/browse/ISPN-6049 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.2.0.Beta1, 8.2.0.Final, 8.1.1.Final > > > Problematic are the calls that are originating in the unprivileged user code. For example: > org.infinispan.distribution.group.GroupManagerImpl.GroupMetadataImpl#getGroup > org.infinispan.distribution.group.GroupManagerImpl#createGroupMetadata > e.g. call stacks > https://gist.github.com/rhusar/e2ae371f852d926c5e13 > https://gist.github.com/rhusar/7411f9dc963bc9233eae > https://gist.github.com/rhusar/782743a551c8eef927a0 (security) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6108) A stopped Node is displayed in all server groups

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-6108?page=com.atlassian.jira.plugin.... ] Martin Gencur closed ISPN-6108. ------------------------------- Resolution: Duplicate Issue Oops. This is a duplicate of ISPN-6080 > A stopped Node is displayed in all server groups > ------------------------------------------------ > > Key: ISPN-6108 > URL: https://issues.jboss.org/browse/ISPN-6108 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Martin Gencur > Assignee: Vladimir Blagojevic > Priority: Minor > Attachments: other-server-group-cluster-view.png > > > The "View nodes" page displays stopped nodes no matter which cluster/server group they're defined in. When I start the node and it is running, it is displayed correctly in just a single server group view. > Attaching a screenshot for server called "server-two" which is in the "main-server-group": > {code} > <server name="server-two" group="main-server-group" auto-start="false"> > {code} > The node is displayed in the view for "other-server-group" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6105) Too many warnings logged for total order commands

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6105?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6105: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Final Resolution: Done > Too many warnings logged for total order commands > ------------------------------------------------- > > Key: ISPN-6105 > URL: https://issues.jboss.org/browse/ISPN-6105 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.Beta1, 8.2.0.Final > > > {{RetryPrepareException}} is harmless, on the same level as {{OutdatedTopologyException}}, so it should be logged at debug level instead of warning. > Tx commands received before the initial topology also result in a {{NullPointerException}} that is logged at the error level, because they try to access the transaction table before it finished initializing. Non-TO tx commands avoid this by calling {{isCommandSentBeforeFirstTopology(commandTopologyId)}}, TO tx commands can do the same. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5932) Remove ClusterRegistry

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5932?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5932: -------------------------------- Description: ClusterRegistry can be replaced by InternalCacheRegistry. ClusterRegistry and ScopedKey should be removed. Do we still keep package org.infinispan.registry.* public in the javadocs? (was: ClusterRegistry can be replaced by InternalCacheRegistry or it can be removed entirely after query module is modified to use pre-declared indexed classes.) > Remove ClusterRegistry > ---------------------- > > Key: ISPN-5932 > URL: https://issues.jboss.org/browse/ISPN-5932 > Project: Infinispan > Issue Type: Task > Components: Core, Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > ClusterRegistry can be replaced by InternalCacheRegistry. ClusterRegistry and ScopedKey should be removed. Do we still keep package org.infinispan.registry.* public in the javadocs? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5932) Remove ClusterRegistry

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5932?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5932: -------------------------------- Status: Open (was: New) > Remove ClusterRegistry > ---------------------- > > Key: ISPN-5932 > URL: https://issues.jboss.org/browse/ISPN-5932 > Project: Infinispan > Issue Type: Task > Components: Core, Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > ClusterRegistry can be replaced by InternalCacheRegistry. ClusterRegistry and ScopedKey should be removed. Do we still keep package org.infinispan.registry.* public in the javadocs? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3747) ProtobufMetadataRegistry should be persistent

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3747?page=com.atlassian.jira.plugin.... ] Adrian Nistor resolved ISPN-3747. --------------------------------- Resolution: Duplicate Issue > ProtobufMetadataRegistry should be persistent > --------------------------------------------- > > Key: ISPN-3747 > URL: https://issues.jboss.org/browse/ISPN-3747 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6035) Caches created via InternalCacheRegistry should be optionally searchable

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6035?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6035: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3904 > Caches created via InternalCacheRegistry should be optionally searchable > ------------------------------------------------------------------------ > > Key: ISPN-6035 > URL: https://issues.jboss.org/browse/ISPN-6035 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Adrian Nistor > Fix For: 8.2.0.Beta1, 8.2.0.Final > > > Add a SEARCHABLE flag to InternalCacheRegistry.Flag enum and use it when filtering caches that need the search components created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6035) Caches created via InternalCacheRegistry should be optionally searchable

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6035?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-6035: ------------------------------------- Assignee: Tristan Tarrant > Caches created via InternalCacheRegistry should be optionally searchable > ------------------------------------------------------------------------ > > Key: ISPN-6035 > URL: https://issues.jboss.org/browse/ISPN-6035 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Adrian Nistor > Assignee: Tristan Tarrant > Fix For: 8.2.0.Beta1, 8.2.0.Final > > > Add a SEARCHABLE flag to InternalCacheRegistry.Flag enum and use it when filtering caches that need the search components created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2016