December 2016 - infinispan-issues

[JBoss JIRA] (ISPN-7264) Administration console - BULK_READ permission is not set in identity/role

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7264?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7264. -------------------------------- Resolution: Partially Completed A temporary workaround is now in place, however additional changes on the server side are required. > Administration console - BULK_READ permission is not set in identity/role > ------------------------------------------------------------------------- > > Key: ISPN-7264 > URL: https://issues.jboss.org/browse/ISPN-7264 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > It appears that BULK_READ permission is nor properly wired/transferred into API invocations. When attempting to access schema names we get the following exceptions in the server: > [Server:server-two] 11:51:44,982 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 33) WFLYCTL0013: Operation ("get-proto-schema-names") failed - address: ([ > [Server:server-two] ("subsystem" => "datagrid-infinispan"), > [Server:server-two] ("cache-container" => "clustered") > [Server:server-two] ]) - failure description: "DGISPN0118: Failed to invoke operation: ISPN000287: Unauthorized access: subject 'Subject with principal(s): [vladimir@ManagementRealm, InetAddressPrincipal <127.0.0.1/127.0.0.1>]' lacks 'BULK_READ' permission" > However, we have set this permission for the role identity/role making invocations (i.e vladimir in the example above) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7264) Administration console - BULK_READ permission is not set in identity/role

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7264?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7264: ------------------------------- Status: Open (was: New) > Administration console - BULK_READ permission is not set in identity/role > ------------------------------------------------------------------------- > > Key: ISPN-7264 > URL: https://issues.jboss.org/browse/ISPN-7264 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > It appears that BULK_READ permission is nor properly wired/transferred into API invocations. When attempting to access schema names we get the following exceptions in the server: > [Server:server-two] 11:51:44,982 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 33) WFLYCTL0013: Operation ("get-proto-schema-names") failed - address: ([ > [Server:server-two] ("subsystem" => "datagrid-infinispan"), > [Server:server-two] ("cache-container" => "clustered") > [Server:server-two] ]) - failure description: "DGISPN0118: Failed to invoke operation: ISPN000287: Unauthorized access: subject 'Subject with principal(s): [vladimir@ManagementRealm, InetAddressPrincipal <127.0.0.1/127.0.0.1>]' lacks 'BULK_READ' permission" > However, we have set this permission for the role identity/role making invocations (i.e vladimir in the example above) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7264) Administration console - BULK_READ permission is not set in identity/role

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7264?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7264: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/160 > Administration console - BULK_READ permission is not set in identity/role > ------------------------------------------------------------------------- > > Key: ISPN-7264 > URL: https://issues.jboss.org/browse/ISPN-7264 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > It appears that BULK_READ permission is nor properly wired/transferred into API invocations. When attempting to access schema names we get the following exceptions in the server: > [Server:server-two] 11:51:44,982 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 33) WFLYCTL0013: Operation ("get-proto-schema-names") failed - address: ([ > [Server:server-two] ("subsystem" => "datagrid-infinispan"), > [Server:server-two] ("cache-container" => "clustered") > [Server:server-two] ]) - failure description: "DGISPN0118: Failed to invoke operation: ISPN000287: Unauthorized access: subject 'Subject with principal(s): [vladimir@ManagementRealm, InetAddressPrincipal <127.0.0.1/127.0.0.1>]' lacks 'BULK_READ' permission" > However, we have set this permission for the role identity/role making invocations (i.e vladimir in the example above) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5424) SemaphoreCompletionService improvements

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5424?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5424: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Beta2) Resolution: Done > SemaphoreCompletionService improvements > --------------------------------------- > > Key: ISPN-5424 > URL: https://issues.jboss.org/browse/ISPN-5424 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Final, 9.0.0.Beta1 > > > Turns out the {{CompletionService}} features aren't that necessary, and it makes the use of {{Runnable}} more cumbersome. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7209) Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-7209?page=com.atlassian.jira.plugin.... ] Jiří Holuša commented on ISPN-7209: ----------------------------------- [~ryanemerson] Great work, thanks! I :) > Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-7209 > URL: https://issues.jboss.org/browse/ISPN-7209 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.0.0.Alpha4 > Reporter: Jiří Holuša > Assignee: Ryan Emerson > > Given following scenario: > 1) store entry to ISPN server via Hot Rod (e.g. with RemoteCache) > 2) have the server configured to use JdbcStringBasedStore > 3) used database is MariaDB 10 > Following exception is thrown: > {code} > ERROR [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore] (HotRodServerHandler-3-2) ISPN008024: Error while storing string key to database; key: '9A09AJAAAAAAAAA==': java.sql.BatchUpdateException: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=' > {code} > Note that his doesn't happen when stored via, for example, Memcached client. Also this issue doesn't appear in library mode, doesn't appear in any with any other database (including MySQL, which is very similar to MariaDB). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7209) Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7209?page=com.atlassian.jira.plugin.... ] Ryan Emerson commented on ISPN-7209: ------------------------------------ [~jholusa] haha it's very strange. A workaround for when using the MariaDB driver, is to explicitly set the collation and character set of either the database, table involved, or the table column used to store the string key before infinispan starts interacting with the DB. I believe different collation and character combos can be combined, however forcing utf8 seems to cause the least amount of problems: character-set-server=utf8mb4 collation-server=utf8mb4_unicode_ci > Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-7209 > URL: https://issues.jboss.org/browse/ISPN-7209 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.0.0.Alpha4 > Reporter: Jiří Holuša > Assignee: Ryan Emerson > > Given following scenario: > 1) store entry to ISPN server via Hot Rod (e.g. with RemoteCache) > 2) have the server configured to use JdbcStringBasedStore > 3) used database is MariaDB 10 > Following exception is thrown: > {code} > ERROR [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore] (HotRodServerHandler-3-2) ISPN008024: Error while storing string key to database; key: '9A09AJAAAAAAAAA==': java.sql.BatchUpdateException: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=' > {code} > Note that his doesn't happen when stored via, for example, Memcached client. Also this issue doesn't appear in library mode, doesn't appear in any with any other database (including MySQL, which is very similar to MariaDB). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6936) Propagate exceptions from functional invocation

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6936?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6936: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Beta2) Resolution: Done > Propagate exceptions from functional invocation > ----------------------------------------------- > > Key: ISPN-6936 > URL: https://issues.jboss.org/browse/ISPN-6936 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Beta1 > > > When a function passed to functional API throws an exception, this should be rethrown on caller side without being wrapped into {{RemoteException}}s, and it should not be logged by Infinispan on the way to caller. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7080) NPE in CacheNotifierImpl by LIRS eviction listener

by ted won (JIRA)

[ https://issues.jboss.org/browse/ISPN-7080?page=com.atlassian.jira.plugin.... ] ted won updated ISPN-7080: -------------------------- SourceForge Reference: (was: https://c.na7.visual.force.com/apex/Case_View?sbstr=01709143) > NPE in CacheNotifierImpl by LIRS eviction listener > --------------------------------------------------- > > Key: ISPN-7080 > URL: https://issues.jboss.org/browse/ISPN-7080 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.Alpha4 > Environment: * Infinispan branch: Upstream master > Reporter: ted won > Assignee: William Burns > Labels: core, eviction, lirs > Fix For: 9.0.0.Beta1 > > > The LIRSEvictionFunctionalTest.testSimpleEvictionMaxEntries unit test method in core module fails and throws NPE in CacheNotifierImpl.notifyCacheEntriesEvicted method when trying to reinsert the first keys again. > https://github.com/infinispan/infinispan/blob/master/core/src/test/java/o... > It reproduces only with LIRS eviction strategy and eviction listener. > However, LRU and UNORDERED eviction strategies are working properly. > It makes impossible the use of eviction listeners with LIRS eviction strategy. > It's able to reproduce by: > - inserting 20 keys - values in a 10 sized cache ( keys from key-1 to key-20), > - and then reinsert the first 10 keys (key-1 to key-10) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4340) Automatically setup shared indexes when indexing is enabled

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4340?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4340: ---------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Automatically setup shared indexes when indexing is enabled > ----------------------------------------------------------- > > Key: ISPN-4340 > URL: https://issues.jboss.org/browse/ISPN-4340 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Labels: 64QueryBlockers > Fix For: 9.0.0.Beta2 > > > - on replicated Caches, we should create a default index on a FSDirectory and provide some appropriate default tuning, for example enabling NRT. > - distributed Caches will need the Infinispan Directory (shared) and a master/slave backend (Infinispan IndexManager, while NRT is not compatible in this case) > We want to keep the properties configuration structure as well as an "advanced tuning" and override capabilities of the default choices. > Some more common options like sync/async indexing should probably be promoted to be controlled by the XML elements and configuration DSL excplicitly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3835: ---------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Index Update command is processed before the registry listener is triggered > --------------------------------------------------------------------------- > > Key: ISPN-3835 > URL: https://issues.jboss.org/browse/ISPN-3835 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Priority: Critical > Labels: 64QueryBlockers > Fix For: 9.0.0.Beta2 > > > When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet. > Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event. > This leads to index update commands to be lost (with a stacktrace logged) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 December 2016