Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: 8.0.0.Beta-CR1
Component/s: Clustering
Labels:
None

Blocked:
False
Blocked Reason:
None
Ready:
False
Target Release:

8.0.0.GA
Steps to Reproduce:
Hide

Issue is intermittent - hit on RHEL 9, Oracle JDK 17:

git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/messaging-testsuite.git cd messaging-testsuite/scripts/ git checkout master groovy -DEAP_ZIP_URL=file:///<path-to-zip>/jboss-eap-8.0.0.Beta-CR1.zip PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean install -B -Dartemis.version=2.21.0 -Deap7.org.jboss.qa.hornetq.apps.clients.version=8.1669154014-SNAPSHOT -Dmaven.test.failure.ignore=true -Dsurefire.failIfNoSpecifiedTests=false -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true -Dtest=CliReloadTest#reloadServerTestWaitForFullReload
Show
Issue is intermittent - hit on RHEL 9, Oracle JDK 17: git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/messaging-testsuite.git cd messaging-testsuite/scripts/ git checkout master groovy -DEAP_ZIP_URL=file: ///<path-to-zip>/jboss-eap-8.0.0.Beta-CR1.zip PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean install -B -Dartemis.version=2.21.0 -Deap7.org.jboss.qa.hornetq.apps.clients.version=8.1669154014-SNAPSHOT -Dmaven.test.failure.ignore= true -Dsurefire.failIfNoSpecifiedTests= false -Dmaven.wagon.http.ssl.insecure= true -Dmaven.wagon.http.ssl.allowall= true -Dtest=CliReloadTest#reloadServerTestWaitForFullReload

SFDC Cases Counter:
SFDC Cases Links:

Description

During reload of server it can happen that following ERROR is logged:

22:58:12,503 ERROR [org.infinispan.CLUSTER] (ServerService Thread Pool -- 38) ISPN000081: Problem closing channel `ejb`; setting it to null: java.lang.NullPointerException: Cannot invoke "Object.getClass()" because "p" is null
        at org.jgroups@4.2.21.Final-redhat-00001//org.jgroups.jmx.JmxConfigurator.unregisterChannel(JmxConfigurator.java:144)
        at org.infinispan@13.0.10.Final-redhat-00001//org.infinispan.remoting.transport.jgroups.JGroupsTransport.unregisterMBeansIfNeeded(JGroupsTransport.java:864)
        at org.infinispan@13.0.10.Final-redhat-00001//org.infinispan.remoting.transport.jgroups.JGroupsTransport.stop(JGroupsTransport.java:828)
        at org.infinispan@13.0.10.Final-redhat-00001//org.infinispan.remoting.transport.jgroups.CorePackageImpl$1.stop(CorePackageImpl.java:46)
        at org.infinispan@13.0.10.Final-redhat-00001//org.infinispan.remoting.transport.jgroups.CorePackageImpl$1.stop(CorePackageImpl.java:27)
        at org.infinispan@13.0.10.Final-redhat-00001//org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeStop(BasicComponentRegistryImpl.java:678)
        at org.infinispan@13.0.10.Final-redhat-00001//org.infinispan.factories.impl.BasicComponentRegistryImpl.doStopWrapper(BasicComponentRegistryImpl.java:674)
        at org.infinispan@13.0.10.Final-redhat-00001//org.infinispan.factories.impl.BasicComponentRegistryImpl.stopWrapper(BasicComponentRegistryImpl.java:662)
        at org.infinispan@13.0.10.Final-redhat-00001//org.infinispan.factories.impl.BasicComponentRegistryImpl.stop(BasicComponentRegistryImpl.java:529)
        at org.infinispan@13.0.10.Final-redhat-00001//org.infinispan.factories.AbstractComponentRegistry.internalStop(AbstractComponentRegistry.java:374)
        at org.infinispan@13.0.10.Final-redhat-00001//org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:308)
        at org.infinispan@13.0.10.Final-redhat-00001//org.infinispan.manager.DefaultCacheManager.internalStop(DefaultCacheManager.java:875)
        at org.infinispan@13.0.10.Final-redhat-00001//org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:848)
        at org.jboss.as.clustering.infinispan@8.0.0.Beta-redhat-00003//org.jboss.as.clustering.infinispan.subsystem.CacheContainerServiceConfigurator.accept(CacheContainerServiceConfigurator.java:130)
        at org.jboss.as.clustering.infinispan@8.0.0.Beta-redhat-00003//org.jboss.as.clustering.infinispan.subsystem.CacheContainerServiceConfigurator.accept(CacheContainerServiceConfigurator.java:78)
        at org.wildfly.clustering.service@8.0.0.Beta-redhat-00003//org.wildfly.clustering.service.FunctionalService.stop(FunctionalService.java:73)
        at org.wildfly.clustering.service@8.0.0.Beta-redhat-00003//org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$stop$1(AsyncServiceConfigurator.java:142)
        at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
        at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)

Expectation is that no WARN/ERROR logs will occur during reload. Besides the error log the issue appears to be harmless.

Test scenario:
Start server in standalone-full-ha.xml profile and reload 100 times. Always wait for the EAP server to get to running state before reloading the server again.

Pass Criteria: Check there are no exceptions from :reload operation calls.

Customer impact: Customers utilizing log monitoring will get "false alarm" during reloading of the server. This issue affects user experience.

Attachments

Activity

People

Assignee:: Unassigned

Reporter:: Miroslav Novak

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2022/11/30 8:23 AM

Updated:: 2023/04/13 7:09 AM

Resolved:: 2023/04/13 7:09 AM