[JBoss JIRA] (ISPN-7190) Administration console - when adding new cache, base configuration shouldn't show existing caches
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7190?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic edited comment on ISPN-7190 at 11/13/16 8:16 AM:
---------------------------------------------------------------------
[~rmacor] Are you possibly looking at the wrong branch or release? Or perhaps not clearing cache? I have just fresh checked out master branch of https://github.com/infinispan/infinispan-management-console master branch, cleaned up my cache, and this issue is not present. There are some conflicts potentially with the old non-Typescript dist layout so make sure you get a clean fresh directory where you will checkout the above-mentioned master branch.
Another that something is not right in your build is the fact that translation file is not loaded properly. That is why you have capital letters with underscores in the modal titles. Please double check. [~pzapataf]
was (Author: vblagojevic):
[~rmacor] Are you possibly looking at the wrong branch or release? Or perhaps not clearing cache? I have just fresh checked out master branch of https://github.com/infinispan/infinispan-management-console master branch, cleaned up my cache, and this issue is not present. There are some conflicts potentially with the old non-Typescript dist layout so make sure you get a clean fresh directory where you will checkout the above-mentioned master branch. Here is my screenshot !Screen Shot 2016-11-13 at 8.05.40 AM.png|thumbnail!
Another that something is not right in your build is the fact that translation file is not loaded properly. That is why you have capital letters with underscores in the modal titles. Please double check. [~pzapataf]
> Administration console - when adding new cache, base configuration shouldn't show existing caches
> -------------------------------------------------------------------------------------------------
>
> Key: ISPN-7190
> URL: https://issues.jboss.org/browse/ISPN-7190
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Alpha4
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Attachments: Screenshot from 2016-11-11.png
>
>
> Click on cache container -> Add cache -> expand "base configuration" drop down
> Result: The drop down offers cache configurations and existing caches
> Expected result: The drop down should only offer cache configurations. ("default" and "memcachedCache" shouldn't be there )
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-7190) Administration console - when adding new cache, base configuration shouldn't show existing caches
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7190?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic edited comment on ISPN-7190 at 11/13/16 8:15 AM:
---------------------------------------------------------------------
[~rmacor] Are you possibly looking at the wrong branch or release? Or perhaps not clearing cache? I have just fresh checked out master branch of https://github.com/infinispan/infinispan-management-console master branch, cleaned up my cache, and this issue is not present. There are some conflicts potentially with the old non-Typescript dist layout so make sure you get a clean fresh directory where you will checkout the above-mentioned master branch. Here is my screenshot !Screen Shot 2016-11-13 at 8.05.40 AM.png|thumbnail!
Another that something is not right in your build is the fact that translation file is not loaded properly. That is why you have capital letters with underscores in the modal titles. Please double check. [~pzapataf]
was (Author: vblagojevic):
[~rmacor] Are you possibly looking at the wrong branch or release? Or perhaps not clearing cache? I have just fresh checked out master branch of https://github.com/infinispan/infinispan-management-console master branch, cleaned up my cache, and this issue is not present. There are some conflicts potentially with the old non-Typescript dist layout so make sure you get a clean fresh directory where you will checkout the above-mentioned master branch. Here is my screenshot !Screen Shot 2016-11-13 at 8.05.40 AM.png|thumbnail!
Another that something is not right in your build is the fact that translation file is not loaded properly. That is why you have capital letters with underscores in the modal titles. Please double check. [~pzapataf]
> Administration console - when adding new cache, base configuration shouldn't show existing caches
> -------------------------------------------------------------------------------------------------
>
> Key: ISPN-7190
> URL: https://issues.jboss.org/browse/ISPN-7190
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Alpha4
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Attachments: Screenshot from 2016-11-11.png
>
>
> Click on cache container -> Add cache -> expand "base configuration" drop down
> Result: The drop down offers cache configurations and existing caches
> Expected result: The drop down should only offer cache configurations. ("default" and "memcachedCache" shouldn't be there )
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-7190) Administration console - when adding new cache, base configuration shouldn't show existing caches
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7190?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-7190:
-------------------------------------------
[~rmacor] Are you possibly looking at the wrong branch or release? Or perhaps not clearing cache? I have just fresh checked out master branch of https://github.com/infinispan/infinispan-management-console master branch, cleaned up my cache, and this issue is not present. There are some conflicts potentially with the old non-Typescript dist layout so make sure you get a clean fresh directory where you will checkout the above-mentioned master branch. Here is my screenshot !Screen Shot 2016-11-13 at 8.05.40 AM.png|thumbnail!
Another that something is not right in your build is the fact that translation file is not loaded properly. That is why you have capital letters with underscores in the modal titles. Please double check. [~pzapataf]
> Administration console - when adding new cache, base configuration shouldn't show existing caches
> -------------------------------------------------------------------------------------------------
>
> Key: ISPN-7190
> URL: https://issues.jboss.org/browse/ISPN-7190
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Alpha4
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Attachments: Screenshot from 2016-11-11.png
>
>
> Click on cache container -> Add cache -> expand "base configuration" drop down
> Result: The drop down offers cache configurations and existing caches
> Expected result: The drop down should only offer cache configurations. ("default" and "memcachedCache" shouldn't be there )
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-7192) Replace RemoteCache.getRemoteCacheManager() with method that returns RemoteCacheContainer
by Paul Ferraro (JIRA)
Paul Ferraro created ISPN-7192:
----------------------------------
Summary: Replace RemoteCache.getRemoteCacheManager() with method that returns RemoteCacheContainer
Key: ISPN-7192
URL: https://issues.jboss.org/browse/ISPN-7192
Project: Infinispan
Issue Type: Enhancement
Components: Remote Protocols
Affects Versions: 9.0.0.Alpha4
Reporter: Paul Ferraro
org.infinispan.Cache already has a getCacheManager() method that returns an interface. Let's generalize this to BasicCache such that RemoteCache has an analogous method that returns RemoteCacheContainer.
However, the naming is really inconsistent. Should we name these:
BasicCache.getCacheManager()::BasicCacheContainer
Cache.getCacheManager()::EmbeddedCacheManager
RemoteCache.getCacheManager()::RemoteCacheContainer
or:
BasicCache.getCacheContainer()::BasicCacheContainer
Cache.getCacheContainer()::EmbeddedCacheManager
RemoteCache.getCacheContainer()::RemoteCacheContainer
It would be great if we could standardize the "cache manager" vs "cache container" naming convention. Given that "cache container" seems more prevalent in the API, I suggest going with that convention. This is complicated by the fact that org.infinispan.manager.CacheContainer already exists, but is not particularly useful.
1. Creating a new org.infinispan.CacheContainer (in the same package as Cache, maybe extending org.infinispan.manager.CacheContainer) with some API refinements. e.g. getName()::String, getDefaultCacheName()::String, remove cruft, etc.
2. Deprecate EmbeddedCacheManager and have it extend this new CacheContainer interface and deprecate it.
That way we can have:
BasicCache.getCacheContainer()::BasicCacheContainer
Cache.getCacheContainer()::org.infinispan.CacheContainer
RemoteCache.getCacheContainer()::RemoteCacheContainer
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-7141) LimitedExecutorTest.testConcurrencyLimit random failures
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-7141?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-7141:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> LimitedExecutorTest.testConcurrencyLimit random failures
> --------------------------------------------------------
>
> Key: ISPN-7141
> URL: https://issues.jboss.org/browse/ISPN-7141
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Labels: testsuite_stability
> Fix For: 9.0.0.Beta1
>
>
> The test reuses a single executor for all test methods, and it is limited to 1 thread. It can take some time between the completion of the {{CompletableFuture}} that the test waits for and the executor thread being actually releases, and that can make the next test method throw a {{RejectedExecutionException}}.
> {noformat}
> 20:37:37,952 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.executors.LimitedExecutorTest.testConcurrencyLimit
> java.util.concurrent.RejectedExecutionException: Task org.infinispan.executors.LimitedExecutor$Runner@5bda0b48 rejected from java.util.concurrent.ThreadPoolExecutor@34d8a229[Running, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 1]
> at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) ~[?:1.8.0_101]
> at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) ~[?:1.8.0_101]
> at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369) ~[?:1.8.0_101]
> at org.infinispan.executors.LimitedExecutor.tryExecute(LimitedExecutor.java:117) ~[classes/:?]
> at org.infinispan.executors.LimitedExecutor.executeInternal(LimitedExecutor.java:92) ~[classes/:?]
> at org.infinispan.executors.LimitedExecutor.execute(LimitedExecutor.java:82) ~[classes/:?]
> at org.infinispan.executors.LimitedExecutorTest.testConcurrencyLimit(LimitedExecutorTest.java:51) ~[test-classes/:?]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month