November 2016 - infinispan-issues

[JBoss JIRA] (ISPN-7224) Support synchronous get in Spring's cache abstraction

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7224?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7224: -------------------------------------- Status: Open (was: New) > Support synchronous get in Spring's cache abstraction > ----------------------------------------------------- > > Key: ISPN-7224 > URL: https://issues.jboss.org/browse/ISPN-7224 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Reporter: Stéphane Nicoll > Assignee: Sebastian Łaskawiec > Priority: Critical > > Spring Framework 4.3 has introduced a read-through option See https://jira.spring.io/browse/SPR-9254 for more details. In practice this would require you to compile against 4.3 and implement the additional method. > The code is meant to be backward compatible with previous version, as long as you're guarding the new exception in an inner class, see [this implementation for an example|https://github.com/hazelcast/hazelcast/blob/37ba79c4a8d35617c5f6a...] > Let me know if I can help. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7244) Administration console - creating new cache should only show valid cache types

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7244?page=com.atlassian.jira.plugin.... ] Roman Macor edited comment on ISPN-7244 at 11/30/16 6:59 AM: ------------------------------------------------------------- [~vblagojevic] I would remove them completely. Warning suggests there is some drawback to creating distributed cache in non-clustered cache container, but it's still possible. That doesn't apply here, if the user would try to create non-local cache in spite of the warning, the result is: The user doesn't see any result after clicking create button and there are errors in the server log. was (Author: rmacor): [~vblagojevic] I would remove them completely. Warning suggests there is some drawback to creating distributed cache in non-clustered cache container, but it's still possible. That doesn't apply here, if the user would try to create non-local cache in spite of warning, the result is: The user doesn't see any result after clicking create button and there are errors in the server log. > Administration console - creating new cache should only show valid cache types > ------------------------------------------------------------------------------ > > Key: ISPN-7244 > URL: https://issues.jboss.org/browse/ISPN-7244 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > > This affects only standalone mode. > Start Infinispan in Standalone non clustered mode (cache container without <transport> tag): > - bin/standalone.sh > Creating new cache/template shows all cache types, but only local cache is a valid option here. Choosing another type results in error. > Suggested resolution: > Only local mode for cache and template should be displayed for local cache container. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7244) Administration console - creating new cache should only show valid cache types

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7244?page=com.atlassian.jira.plugin.... ] Roman Macor commented on ISPN-7244: ----------------------------------- [~vblagojevic] I would remove them completely. Warning suggests there is some drawback to creating distributed cache in non-clustered cache container, but it's still possible. That doesn't apply here, if the user would try to create non-local cache in spite of warning, the result is: The user doesn't see any result after clicking create button and there are errors in the server log. > Administration console - creating new cache should only show valid cache types > ------------------------------------------------------------------------------ > > Key: ISPN-7244 > URL: https://issues.jboss.org/browse/ISPN-7244 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > > This affects only standalone mode. > Start Infinispan in Standalone non clustered mode (cache container without <transport> tag): > - bin/standalone.sh > Creating new cache/template shows all cache types, but only local cache is a valid option here. Choosing another type results in error. > Suggested resolution: > Only local mode for cache and template should be displayed for local cache container. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7255) Document ___script_manager and ___schema_manager roles

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7255?page=com.atlassian.jira.plugin.... ] Roman Macor updated ISPN-7255: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4694 > Document ___script_manager and ___schema_manager roles > ------------------------------------------------------ > > Key: ISPN-7255 > URL: https://issues.jboss.org/browse/ISPN-7255 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Query > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Roman Macor > > A user needs to have these roles to access scripts and schemes (when authorization is enabled), but I couldn't find it in documentation anywhere. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7255) Document ___script_manager and ___schema_manager roles

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7255?page=com.atlassian.jira.plugin.... ] Roman Macor updated ISPN-7255: ------------------------------ Status: Open (was: New) > Document ___script_manager and ___schema_manager roles > ------------------------------------------------------ > > Key: ISPN-7255 > URL: https://issues.jboss.org/browse/ISPN-7255 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Query > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Roman Macor > > A user needs to have these roles to access scripts and schemes (when authorization is enabled), but I couldn't find it in documentation anywhere. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7215) Administration console - upload of deployment artifact doesn't work

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7215?page=com.atlassian.jira.plugin.... ] Ryan Emerson commented on ISPN-7215: ------------------------------------ Looking at this now. [~vblagojevic][~rmacor] FYI you can see this issue in upstream much easier if you run `gulp serve:dist`, as this serves the packaged version of the console. > Administration console - upload of deployment artifact doesn't work > ------------------------------------------------------------------- > > Key: ISPN-7215 > URL: https://issues.jboss.org/browse/ISPN-7215 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Ryan Emerson > Attachments: Screen Shot 2016-11-21 at 8.36.46 AM.png, custom-store.jar > > > Click on cache container -> Configuration -> Deployments -> upload -> Browse... -> select file -> click upload > Result: nothing happens -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7255) Document ___script_manager and ___schema_manager roles

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7255?page=com.atlassian.jira.plugin.... ] Roman Macor reassigned ISPN-7255: --------------------------------- Assignee: Roman Macor > Document ___script_manager and ___schema_manager roles > ------------------------------------------------------ > > Key: ISPN-7255 > URL: https://issues.jboss.org/browse/ISPN-7255 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Query > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Roman Macor > > A user needs to have these roles to access scripts and schemes (when authorization is enabled), but I couldn't find it in documentation anywhere. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7066) The default cache configuration should not be applied to other caches

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7066?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7066: ---------------------------------- Fix Version/s: 9.0.0.Final > The default cache configuration should not be applied to other caches > --------------------------------------------------------------------- > > Key: ISPN-7066 > URL: https://issues.jboss.org/browse/ISPN-7066 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 8.2.3.Final, 8.2.4.Final > Reporter: Vladimir Dzhuvinov > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > > Hi guys, > We noticed a weird behaviour of the Infinispan config where caches that are configured with no persistence assume the persistence configuration of the default cache for the cache container. This can potentially lead to some serious errors as data put into the other caches is getting written into the store of the default cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7066) The default cache configuration should not be applied to other caches

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7066?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7066: ---------------------------------- Status: Open (was: New) > The default cache configuration should not be applied to other caches > --------------------------------------------------------------------- > > Key: ISPN-7066 > URL: https://issues.jboss.org/browse/ISPN-7066 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 8.2.3.Final, 8.2.4.Final > Reporter: Vladimir Dzhuvinov > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > > Hi guys, > We noticed a weird behaviour of the Infinispan config where caches that are configured with no persistence assume the persistence configuration of the default cache for the cache container. This can potentially lead to some serious errors as data put into the other caches is getting written into the store of the default cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7248) Administration console - start/stop/remove node actions should not be available in standalone mode

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7248?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7248. -------------------------------- Fix Version/s: 9.0.0.Beta1 Resolution: Done > Administration console - start/stop/remove node actions should not be available in standalone mode > -------------------------------------------------------------------------------------------------- > > Key: ISPN-7248 > URL: https://issues.jboss.org/browse/ISPN-7248 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Beta1 > > > Start the server in standalone mode, with clustered configuration: > bin/standalone.sh -c clustered.xml -> in administration console, click on clusters tab -> cluster -> node > Result: There is an action button with start, stop and remove action. Clicking on actions prompts a confirmation dialog but after confirming, doesn't do anything. > Expected result: Action button shouldn't be there. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2016