[JBoss JIRA] (ISPN-7160) RemoteSpringSessionTest random failures
by Dan Berindei (JIRA)
Dan Berindei created ISPN-7160:
----------------------------------
Summary: RemoteSpringSessionTest random failures
Key: ISPN-7160
URL: https://issues.jboss.org/browse/ISPN-7160
Project: Infinispan
Issue Type: Bug
Components: Spring Integration
Reporter: Dan Berindei
Assignee: Sebastian Łaskawiec
Priority: Critical
Fix For: 9.0.0.Beta1
{{RemoteSpringSessionTest}} and {{EmbeddedSpringSessionTest}} use the default cache jmx configuration, so they try to register the same JMX object names. If they run in parallel, one of them will fail to start the cache manager:
{noformat}
org.infinispan.jmx.JmxDomainConflictException: ISPN000034: There's already a JMX MBean instance type=CacheManager,name="DefaultCacheManager" already registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element
at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:53)
at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79)
at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73)
at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37)
at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41)
at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:661)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:235)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:147)
at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.beforeclass(RemoteSpringSessionTest.java:29)
{noformat}
If the cache manager was not created, teardown also fails with a NPE:
{noformat}
java.lang.NullPointerException
at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.afterClass(RemoteSpringSessionTest.java:41)
{noformat}
The test should use the {{TestCacheManagerFactory}} methods to create the cache manager, which will set a unique JMX domain name for each instance.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months
[JBoss JIRA] (ISPN-7160) RemoteSpringSessionTest random failures
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-7160?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-7160:
-------------------------------
Status: Open (was: New)
> RemoteSpringSessionTest random failures
> ---------------------------------------
>
> Key: ISPN-7160
> URL: https://issues.jboss.org/browse/ISPN-7160
> Project: Infinispan
> Issue Type: Bug
> Components: Spring Integration
> Reporter: Dan Berindei
> Assignee: Sebastian Łaskawiec
> Priority: Critical
> Labels: testsuite_stability
> Fix For: 9.0.0.Beta1
>
>
> {{RemoteSpringSessionTest}} and {{EmbeddedSpringSessionTest}} use the default cache jmx configuration, so they try to register the same JMX object names. If they run in parallel, one of them will fail to start the cache manager:
> {noformat}
> org.infinispan.jmx.JmxDomainConflictException: ISPN000034: There's already a JMX MBean instance type=CacheManager,name="DefaultCacheManager" already registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element
> at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:53)
> at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79)
> at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73)
> at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37)
> at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41)
> at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:661)
> at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:235)
> at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:147)
> at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.beforeclass(RemoteSpringSessionTest.java:29)
> {noformat}
> If the cache manager was not created, teardown also fails with a NPE:
> {noformat}
> java.lang.NullPointerException
> at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.afterClass(RemoteSpringSessionTest.java:41)
> {noformat}
> The test should use the {{TestCacheManagerFactory}} methods to create the cache manager, which will set a unique JMX domain name for each instance.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months
[JBoss JIRA] (ISPN-7159) CompleteShutdownDistRetryTest.testRetryAfterCompleteShutdown random failures
by Dan Berindei (JIRA)
Dan Berindei created ISPN-7159:
----------------------------------
Summary: CompleteShutdownDistRetryTest.testRetryAfterCompleteShutdown random failures
Key: ISPN-7159
URL: https://issues.jboss.org/browse/ISPN-7159
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Server
Affects Versions: 9.0.0.Alpha4
Reporter: Dan Berindei
Priority: Critical
Fix For: 9.0.0.Beta1
{noformat}
java.lang.AssertionError: expected:<two> but was:<null>
at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:101)
at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:108)
at org.infinispan.client.hotrod.retry.CompleteShutdownDistRetryTest.testRetryAfterCompleteShutdown(CompleteShutdownDistRetryTest.java:58)
{noformat}
I think the problem is that killing node 0 can make node 2's key move from node 2 to node 1, and then it's lost after node 1 is also killed.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months
[JBoss JIRA] (ISPN-7148) Unable to create/edit Cache Configurations when Security is not enabled
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7148?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7148:
--------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/137
> Unable to create/edit Cache Configurations when Security is not enabled
> -----------------------------------------------------------------------
>
> Key: ISPN-7148
> URL: https://issues.jboss.org/browse/ISPN-7148
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Alpha4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
>
> Unable to create/edit cache configurations/templates as the security/authorization DMR is not created when required:
> "WFLYCTL0175: Resource [
> ("profile" => "clustered"),
> ("subsystem" => "datagrid-infinispan"),
> ("cache-container" => "clustered"),
> ("configurations" => "CONFIGURATIONS"),
> ("distributed-cache-configuration" => "asdasdad"),
> ("security" => "SECURITY")
> ] does not exist; a resource at address [
> ("profile" => "clustered"),
> ("subsystem" => "datagrid-infinispan"),
> ("cache-container" => "clustered"),
> ("configurations" => "CONFIGURATIONS"),
> ("distributed-cache-configuration" => "asdasdad"),
> ("security" => "SECURITY"),
> ("authorization" => "AUTHORIZATION")
> ] cannot be created until all ancestor resources have been added"
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months
[JBoss JIRA] (ISPN-7148) Unable to create/edit Cache Configurations when Security is not enabled
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7148?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7148:
--------------------------------------
Status: Open (was: New)
> Unable to create/edit Cache Configurations when Security is not enabled
> -----------------------------------------------------------------------
>
> Key: ISPN-7148
> URL: https://issues.jboss.org/browse/ISPN-7148
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Alpha4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
>
> Unable to create/edit cache configurations/templates as the security/authorization DMR is not created when required:
> "WFLYCTL0175: Resource [
> ("profile" => "clustered"),
> ("subsystem" => "datagrid-infinispan"),
> ("cache-container" => "clustered"),
> ("configurations" => "CONFIGURATIONS"),
> ("distributed-cache-configuration" => "asdasdad"),
> ("security" => "SECURITY")
> ] does not exist; a resource at address [
> ("profile" => "clustered"),
> ("subsystem" => "datagrid-infinispan"),
> ("cache-container" => "clustered"),
> ("configurations" => "CONFIGURATIONS"),
> ("distributed-cache-configuration" => "asdasdad"),
> ("security" => "SECURITY"),
> ("authorization" => "AUTHORIZATION")
> ] cannot be created until all ancestor resources have been added"
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months
[JBoss JIRA] (ISPN-3702) Too many threads for cleaning up infinispan transactions
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3702?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3702:
-----------------------------------------------
Petr Jurak <pjurak(a)redhat.com> changed the Status of [bug 1378875|https://bugzilla.redhat.com/show_bug.cgi?id=1378875] from NEW to ASSIGNED
> Too many threads for cleaning up infinispan transactions
> --------------------------------------------------------
>
> Key: ISPN-3702
> URL: https://issues.jboss.org/browse/ISPN-3702
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Transactions
> Affects Versions: 5.3.0.Final
> Environment: Mac and Linux
> Reporter: Prasanth Pallamreddy
> Assignee: Pedro Ruivo
> Fix For: 9.0.0.Alpha2, 8.2.2.Final
>
>
> When using multiple transactional caches, we are seeing that each cache has a dedicated cleanup thread. While this is not an issue for small number of caches, when the number of caches is high as in our case (~100), we see around a 100 threads dedicated for cleanup like the following.
> "TxCleanupService,{default}_{XXX},user-mac-54275" daemon prio=5 tid=0x00007fa0f50d3800 nid=0x10f03 waiting on condition [0x00000001a5a5d000]
> "TxCleanupService,{default}_{XXX},user-mac-54275" daemon prio=5 tid=0x00007fa0f507e800 nid=0x10e03 waiting on condition [0x00000001a595a000]
> "TxCleanupService,{default}_{XXX},user-mac-54275" daemon prio=5 tid=0x00007fa0f507e000 nid=0x10d03 waiting on condition [0x00000001a5857000]
> "TxCleanupService,{default}_{XXX},user-mac-54275" daemon prio=5 tid=0x00007fa0f5817800 nid=0x10c03 waiting on condition [0x00000001a5754000]
> ...
> Looking at the source code for
> https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
> if (!totalOrder) {
> // Periodically run a task to cleanup the transaction table from completed transactions.
> ThreadFactory tf = new ThreadFactory() {
> @Override
> public Thread newThread(Runnable r) {
> String address = rpcManager != null ? rpcManager.getTransport().getAddress().toString() : "local";
> Thread th = new Thread(r, "TxCleanupService," + cacheName + "," + address);
> th.setDaemon(true);
> return th;
> }
> };
> executorService = Executors.newSingleThreadScheduledExecutor(tf);
> This code can benefit from drawing the threads from a dedicated pool which is bounded.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months
[JBoss JIRA] (ISPN-7155) Failures in CI from functional tests
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-7155?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-7155:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.0.0.Beta1
Resolution: Done
> Failures in CI from functional tests
> ------------------------------------
>
> Key: ISPN-7155
> URL: https://issues.jboss.org/browse/ISPN-7155
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.0.Alpha4
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 9.0.0.Beta1
>
>
> These tests are often failing in CI:
> FunctionalNonTxBackupOwnerBecomingPrimaryOwnerTest
> FunctionalNonTxJoinerBecomingBackupOwnerTest
> FunctionalCachestoreReadOnlyTest
> FunctionalInMemoryReadOnlyTest
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months
[JBoss JIRA] (ISPN-7158) EmbeddedApplicationPublishedBridgeTest.testEventBridge random failures
by Dan Berindei (JIRA)
Dan Berindei created ISPN-7158:
----------------------------------
Summary: EmbeddedApplicationPublishedBridgeTest.testEventBridge random failures
Key: ISPN-7158
URL: https://issues.jboss.org/browse/ISPN-7158
Project: Infinispan
Issue Type: Bug
Components: Spring Integration
Reporter: Dan Berindei
Assignee: Sebastian Łaskawiec
Priority: Critical
Fix For: 9.0.0.Beta1
{{TimeUnit.SECONDS.sleep(1)}} doesn't guarantee that the thread actually sleeps for a full second. And if it wakes up a millisecond too early, the entry is not expired by the time of the check:
{noformat}
java.lang.AssertionError: expected [null] but found [org.springframework.cache.support.SimpleValueWrapper@7bbbe232]
at org.testng.Assert.fail(Assert.java:94)
at org.testng.Assert.failNotSame(Assert.java:490)
at org.testng.Assert.assertNull(Assert.java:426)
at org.testng.Assert.assertNull(Assert.java:415)
at org.infinispan.spring.session.InfinispanApplicationPublishedBridgeTCK.testEventBridge(InfinispanApplicationPublishedBridgeTCK.java:58)
at org.infinispan.spring.session.EmbeddedApplicationPublishedBridgeTest.testEventBridge(EmbeddedApplicationPublishedBridgeTest.java:59)
{noformat}
The test should use a {{TimeService}} to guarantee that the entry expires without having to wait so long.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months