The test which can reproduce the issue is: https://svn.devel.redhat.com/repos/jboss-qa/jdg/jdg-functional-tests/trunk/invm/async-notif/src/test/java/com/jboss/datagrid/test/asyncnotif/clustered/AsyncNotificationTest.java The test failures are: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-jdbc-cache-stores-tomcat7/DATABASE=mysql55,jdk=java16_default,label=RHEL6_x86_64/114/testReport/com.jboss.datagrid.test.asyncnotif.clustered/AsyncNotificationTest/testKeyCRUD1/ http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-jdbc-cache-stores-tomcat7/DATABASE=mysql55,jdk=java16_default,label=RHEL6_x86_64/113/testReport/com.jboss.datagrid.test.asyncnotif.clustered/AsyncNotificationTest/testKeyCRUD1/ The bug may be related to the issue: https://bugzilla.redhat.com/show_bug.cgi?id=879288
Adrian Nistor <anistor> made a comment on jira ISPN-2540 Hi Anna. Could you please post your cache configuration?
Anna Manukyan <amanukya> made a comment on jira ISPN-2540 Hi Adrian, my cache configuration is: {code} GlobalConfiguration glob = new GlobalConfigurationBuilder() .globalJmxStatistics().jmxDomain("AsyncNotifExecutorCache").allowDuplicateDomains(true) .transport().addProperty("configurationFile", "jgroups-tcp.xml"). distributedSyncTimeout(150000). strictPeerToPeer(false). transport(new JGroupsTransport()). asyncListenerExecutor().addProperty("maxThreads", "5"). build(); ConfigurationBuilder c = new ConfigurationBuilder(); c.clustering().cacheMode(CacheMode.INVALIDATION_SYNC); Configuration cnf = c.build(); DefaultCacheManager manager = new DefaultCacheManager(glob); manager.defineConfiguration("testCache", cnf); {code} Best regards, Anna.
Adrian Nistor <anistor> made a comment on jira ISPN-2540 Is it possible that you are unintentionally mixing in the same cluster some nodes that are INVALIDATION_SYNC and DIST_SYNC?
Hi Adrian, thanks for the hint. I guess yes, and the reason is that the cache is not properly stopped during tomcat container undeploy, and the DIST_ASYNC cache from the previous test affects the new Invalidation cache. I run the test separately, and it doesn't fail. As well as the tests doesn't fail for EAP. I'll try to resolve this issue. Best regards, Anna.
Should this be marked invalid then ?
I guess yes. As soon as I'll fix the test on my side, and make sure that it doesn't fail, I'll mark the bug as invalid.
Anna Manukyan <amanukya> updated the status of jira ISPN-2540 to Resolved
Anna Manukyan <amanukya> made a comment on jira ISPN-2540 The problem was in the unsuccessfull undeployment of tomcat container, which caused that the DIST_ASYNC cache created in one test, was harming the INVALIDATION test in another. The tests are fixed.