[JBoss JIRA] (ISPN-10881) Deprecate GlobalJmxStatisticsConfiguration.allowDuplicateDomains
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10881?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10881:
------------------------------------------
Sprint: DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Deprecate GlobalJmxStatisticsConfiguration.allowDuplicateDomains
> ----------------------------------------------------------------
>
> Key: ISPN-10881
> URL: https://issues.redhat.com/browse/ISPN-10881
> Project: Infinispan
> Issue Type: Task
> Components: Configuration, Core
> Affects Versions: 10.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.1.0.Final
>
>
> {{allowDuplicateDomains}} is just a crutch for tests. Applications rarely start more than one cache manager in the same JVM, and when they (e.g. multiple applications in an application server) do it's always a good idea to give each cache manager a unique name.
> Our test suite doesn't really need {{allowDuplicateDomains}} either: {{TestCacheManagerFactory}} adds a UUID to the domain name, unless the test has explicitly set a (presumably unique) domain name.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-10806) Default semantic configurations for the server
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10806?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10806:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Default semantic configurations for the server
> ----------------------------------------------
>
> Key: ISPN-10806
> URL: https://issues.redhat.com/browse/ISPN-10806
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration, Server
> Affects Versions: 10.0.0.CR3
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
>
> org.infinispan.VOLATILE (same as DIST_SYNC)
> org.infinispan.PERSISTENT (VOLATILE + soft index store)
> org.infinispan.INDEXED (PERSISTENT + indexed)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-10807) Don't include Narayana in the server
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10807?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10807:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Don't include Narayana in the server
> ------------------------------------
>
> Key: ISPN-10807
> URL: https://issues.redhat.com/browse/ISPN-10807
> Project: Infinispan
> Issue Type: Feature Request
> Components: Server, Transactions
> Affects Versions: 10.0.0.CR3
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> The Hot Rod tx implementation uses the embedded TM only. Including Narayana in the server distribution is therefore pointless. It should be removed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-10821) Decrease GMS join_timeout and increase xPING num_discovery_runs
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10821?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10821:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Decrease GMS join_timeout and increase xPING num_discovery_runs
> ---------------------------------------------------------------
>
> Key: ISPN-10821
> URL: https://issues.redhat.com/browse/ISPN-10821
> Project: Infinispan
> Issue Type: Task
> Components: Configuration
> Affects Versions: 9.4.16.Final, 10.0.0.CR3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> Our default JGroups configurations have a GMS {{join_timeout="5000"}}, meaning the first node to start will always wait for 5 seconds before becoming coordinator. It should be safe to use the JGroups default of 2 seconds.
> To make it even more safe, we could configure the discovery protocol's {{num_discovery_runs="3"}}, so that it makes multiple attempts to contact existing nodes during those 2 seconds of waiting. {{num_discovery_runs}} is only used for the initial discovery, so there's no danger of creating additional traffic while the node is up.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-10798) JCache annotations attribute cacheResolverFactory is ignored
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10798?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10798:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> JCache annotations attribute cacheResolverFactory is ignored
> ------------------------------------------------------------
>
> Key: ISPN-10798
> URL: https://issues.redhat.com/browse/ISPN-10798
> Project: Infinispan
> Issue Type: Bug
> Components: JCache
> Affects Versions: 9.4.16.Final, 10.0.0.CR3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.1.0.Final
>
>
> The JCache TCK doesn't seem to require support for {{cacheResolverFactory}}, but having it would allow us to have an alternative to the managed interceptors {{InjectedCache*Interceptor}} and to deprecate them.
> We can then move the default interceptors to the jcache-commons module, so they support both embedded and remote caches.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-10804) JCache tck-runner does not run interception tests
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10804?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10804:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> JCache tck-runner does not run interception tests
> -------------------------------------------------
>
> Key: ISPN-10804
> URL: https://issues.redhat.com/browse/ISPN-10804
> Project: Infinispan
> Issue Type: Bug
> Components: JCache, Test Suite
> Affects Versions: 9.4.16.Final, 10.0.0.CR3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.1.0.Final
>
>
> Initially I thought the only way to make the interception TCK tests run was to add a {{@Priority}} annotation, which is not a good idea because even our tests expect to be able to switch between the managed or the managed interceptors.
> But it turns out if we revert ISPN-10721 and unpack the TCK tests in our build output directory, we can override {{beans.xml}} and make the interception tests run.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-10719) JCache: CacheManager.destroyCache should not remove internal caches
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10719?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10719:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> JCache: CacheManager.destroyCache should not remove internal caches
> -------------------------------------------------------------------
>
> Key: ISPN-10719
> URL: https://issues.redhat.com/browse/ISPN-10719
> Project: Infinispan
> Issue Type: Bug
> Components: JCache
> Affects Versions: 10.0.0.CR2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Final
>
>
> {{___protobuf_metadata}} is an internal cache, but it is also exposed to users -- including JCache users, who see it as a predefined cache.
> Some JCache TCK tests try to remove all caches between test methods using
> {{CacheManager.destroyCache()}}. By removing {{___protobuf_metadata}} they break {{ProtobufMetadataManagerImpl}} and don't allow the following tests to create any new caches:
> {noformat}
> [2019-10-01T07:11:13.651Z] [OK: 144, KO: 1, SKIP: 0] Test failed: CacheExpiryTest.testCacheStatisticsRemoveAllNoneExpired
> [2019-10-01T07:11:13.651Z] org.infinispan.commons.CacheConfigurationException: ISPN000436: Cache '___protobuf_metadata' has been requested, but no cache configuration exists with that name and no default cache has been set for this container
> [2019-10-01T07:11:13.651Z] at org.infinispan.configuration.ConfigurationManager.getConfiguration(ConfigurationManager.java:65)
> [2019-10-01T07:11:13.651Z] at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:637)
> [2019-10-01T07:11:13.651Z] at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:626)
> [2019-10-01T07:11:13.651Z] at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:511)
> [2019-10-01T07:11:13.651Z] at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:495)
> [2019-10-01T07:11:13.651Z] at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:488)
> [2019-10-01T07:11:13.651Z] at org.infinispan.query.remote.impl.SecurityActions.lambda$getUnwrappedCache$0(SecurityActions.java:43)
> [2019-10-01T07:11:13.651Z] at org.infinispan.security.Security.doPrivileged(Security.java:47)
> [2019-10-01T07:11:13.651Z] at org.infinispan.query.remote.impl.SecurityActions.doPrivileged(SecurityActions.java:30)
> [2019-10-01T07:11:13.651Z] at org.infinispan.query.remote.impl.SecurityActions.getUnwrappedCache(SecurityActions.java:42)
> [2019-10-01T07:11:13.651Z] at org.infinispan.query.remote.impl.ProtobufMetadataManagerImpl.addCacheDependency(ProtobufMetadataManagerImpl.java:68)
> [2019-10-01T07:11:13.651Z] at org.infinispan.query.remote.impl.LifecycleManager.cacheStarting(LifecycleManager.java:215)
> [2019-10-01T07:11:13.651Z] at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:223)
> [2019-10-01T07:11:13.651Z] at org.infinispan.factories.ComponentRegistry.preStart(ComponentRegistry.java:213)
> [2019-10-01T07:11:13.651Z] at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:238)
> [2019-10-01T07:11:13.651Z] at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:203)
> [2019-10-01T07:11:13.651Z] at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:1082)
> [2019-10-01T07:11:13.651Z] at org.infinispan.cache.impl.AbstractDelegatingCache.start(AbstractDelegatingCache.java:512)
> [2019-10-01T07:11:13.651Z] at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:682)
> [2019-10-01T07:11:13.651Z] at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:626)
> [2019-10-01T07:11:13.651Z] at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:511)
> [2019-10-01T07:11:13.651Z] at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:495)
> [2019-10-01T07:11:13.651Z] at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:488)
> [2019-10-01T07:11:13.651Z] at org.infinispan.jcache.embedded.JCacheManager.create(JCacheManager.java:149)
> [2019-10-01T07:11:13.651Z] at org.infinispan.jcache.AbstractJCacheManager.createCache(AbstractJCacheManager.java:93)
> [2019-10-01T07:11:13.651Z] at org.jsr107.tck.expiry.CacheExpiryTest.testCacheStatisticsRemoveAllNoneExpired(CacheExpiryTest.java:163)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-10774) kill-server Ant task kills clients too
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10774?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10774:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> kill-server Ant task kills clients too
> --------------------------------------
>
> Key: ISPN-10774
> URL: https://issues.redhat.com/browse/ISPN-10774
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.CR3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> {{kill-server}} uses multiple sources to find the pid of the running server(s), among them {{lsof}} to find processes listening on the HotRod port.
> The {{lsof}} command line is imprecise and it also finds clients that have leaked a connection to the server, killing the failsafe fork too early and preventing failsafe from reporting the test results.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-10764) Clustered Graceful Shutdown for server
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10764?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10764:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Clustered Graceful Shutdown for server
> --------------------------------------
>
> Key: ISPN-10764
> URL: https://issues.redhat.com/browse/ISPN-10764
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 10.0.0.CR3
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> * Allow the server to shutdown any other node as well as the whole cluster
> * Add REST APIs for specific node shutdown and clustered shutdown
> * Add corresponding CLI commands
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months