[JBoss JIRA] (WFLY-12756) RankedAffinityTestCase fails on OpenJ9
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-12756:
-----------------------------------
Summary: RankedAffinityTestCase fails on OpenJ9
Key: WFLY-12756
URL: https://issues.jboss.org/browse/WFLY-12756
Project: WildFly
Issue Type: Bug
Components: Clustering, Test Suite
Affects Versions: 18.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
{noformat}
java.lang.NoSuchMethodError: org/bouncycastle/util/…
[View More]Arrays.append([Ljava/lang/String;Ljava/lang/String;)[Ljava/lang/String; (loaded from file:/store/repository/org/apache/directory/server/apacheds-all/2.0.0-M24/apacheds-all-2.0.0-M24.jar by jdk.internal.loader.ClassLoaders$AppClassLoader@b33b58fe) called from class org.jboss.as.test.clustering.cluster.affinity.RankedAffinityTestCase (loaded from file:/store/work/tc-work/aa09375132417a7/testsuite/integration/clustering/target/test-classes/ by jdk.internal.loader.ClassLoaders$AppClassLoader@b33b58fe).
at org.jboss.as.test.clustering.cluster.affinity.RankedAffinityTestCase.<init>(RankedAffinityTestCase.java:85)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:217)
at org.jboss.arquillian.junit.Arquillian.access$300(Arquillian.java:54)
at org.jboss.arquillian.junit.Arquillian$6.runReflectiveCall(Arquillian.java:240)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.jboss.arquillian.junit.Arquillian.methodBlock(Arquillian.java:242)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:166)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:350)
at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:177)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:115)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[View Less]
5 years, 4 months
[JBoss JIRA] (WFCORE-4733) Server stops after switching from 'local' DC to 'remote' DC
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFCORE-4733?page=com.atlassian.jira.plugi... ]
Jeff Mesnil reassigned WFCORE-4733:
-----------------------------------
Assignee: Yeray Borges (was: Jeff Mesnil)
> Server stops after switching from 'local' DC to 'remote' DC
> -----------------------------------------------------------
>
> Key: WFCORE-4733
> URL: https://issues.jboss.org/browse/WFCORE-4733
> Project: WildFly Core
> …
[View More] Issue Type: Bug
> Components: Management
> Affects Versions: 10.0.0.Final
> Environment: 2 servers started as DC on two different machines
> Reporter: Joerg Baesner
> Assignee: Yeray Borges
> Priority: Major
>
> Install WildFly on two different machines, add an 'admin' user and start the {{host-master.xml}} configurations on each node, like:
> machineA: (10.10.10.1)
> {noformat}
> $JBOSS_HOME/bin/add-user.sh -u admin -p admin
> $JBOSS_HOME/bin/domain.sh --host-config.xml -Djboss.bind.address.management=10.10.10.1
> {noformat}
> machineB: 10.10.10.2
> {noformat}
> $JBOSS_HOME/bin/add-user.sh -u admin -p admin
> $JBOSS_HOME/bin/domain.sh --host-config.xml -Djboss.bind.address.management=10.10.10.2
> {noformat}
> And then applying a simplified script like below to machineB:
> {code}
> batch
> /host=master:write-attribute(name=name, value=slave)
> /host=master/core-service=discovery-options/static-discovery=primary:add(host=10.10.10.1, port=9990, protocol=remote+http)
> /host=master:write-remote-domain-controller(username=admin, security-realm="ManagementRealm")
> /host=master/core-service=management/security-realm=ManagementRealm/server-identity=secret:add(value="YWRtaW4=")
> run-batch
> /host=master:reload
> {code}
> Executing this scripts results in a server log output like below and stopping of the 'DomainController':
> {noformat}
> [Host Controller] INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
> [Host Controller] WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /jboss/jboss-eap-7.2/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> [Host Controller] WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote+http://10.0.0.1:9990: 2-$-WFLYDC0015: There is already a registered host named 'master'
> [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnection$HostControllerConnectRequest.handleRequest(RemoteDomainConnection.java:390)
> [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:321)
> [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleRequest(AbstractMessageHandler.java:286)
> [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:234)
> [Host Controller] at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:85)
> [Host Controller] at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> [Host Controller] at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
> [Host Controller] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> [Host Controller] at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> [Host Controller] at java.lang.Thread.run(Thread.java:748)
> [Host Controller]
> [Host Controller] WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain.
> [Host Controller] ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect
> [Host Controller] FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99
> [Host Controller] INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: JBoss EAP 7.2.4.GA (WildFly Core 6.0.16.Final-redhat-00002) stopped in 77ms
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[View Less]
5 years, 4 months
[JBoss JIRA] (WFCORE-4143) Embed CLI failures on IBM jdk - checkLogging
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4143?page=com.atlassian.jira.plugi... ]
James Perkins closed WFCORE-4143.
---------------------------------
Resolution: Out of Date
I'm closing this as out of date as these tests were disabled for an IBM JVM in WFCORE-4525. I did test these on OpenJ9 and there were no issues.
> Embed CLI failures on IBM jdk - checkLogging
> --------------------------------------------
>
> Key: WFCORE-4143
> URL: …
[View More]https://issues.jboss.org/browse/WFCORE-4143
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Environment: IBM JDK
> {noformat}
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 8.0.5.20 - pxa6480sr5fp20-20180802_01(SR5 FP20))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20180731_393394 (JIT enabled, AOT enabled)
> OpenJ9 - bd23af8
> OMR - ca1411c
> IBM - 98805ca)
> JCL - 20180719_01 based on Oracle jdk8u181-b12
> {noformat}
> Reporter: Petr Kremensky
> Assignee: James Perkins
> Priority: Major
> Labels: OpenJ9
>
> {{testLogging}} for Cli tests in Wildfly-core testsuite fails on IBM JDK.
> *reproduce*
> cd wildfly-core/testsuite
> mvn clean test -fae -Dts.manualmode -pl manualmode,standalone -Dtest=CLIEmbedHostControllerTestCase,CLIEmbedServerTestCase,SilentModeTestCase
> ...
> [ERROR] Failures:
> [ERROR] SilentModeTestCase.testLogging:99->checkIfEmpty:152
> [INFO]
> [ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0
> ...
> [ERROR] Failures:
> [ERROR] CLIEmbedHostControllerTestCase.testHelp:321->checkLogging:744
> [ERROR] CLIEmbedHostControllerTestCase.testStdOutDefault:160->stdoutTest:188->checkClientSideLogging:231->checkLogging:744
> [ERROR] CLIEmbedHostControllerTestCase.testStdOutDiscard:166->stdoutTest:188->checkClientSideLogging:231->checkLogging:744
> [ERROR] CLIEmbedHostControllerTestCase.testStdOutEcho:172->stdoutTest:188->checkClientSideLogging:231->checkLogging:744
> [ERROR] CLIEmbedServerTestCase.testHelp:543->checkLogging:764
> [ERROR] CLIEmbedServerTestCase.testStdOutDefault:196->stdoutTest:224->checkClientSideLogging:267->checkLogging:764
> [ERROR] CLIEmbedServerTestCase.testStdOutDiscard:202->stdoutTest:224->checkClientSideLogging:267->checkLogging:764
> [ERROR] CLIEmbedServerTestCase.testStdOutEcho:208->stdoutTest:224->checkClientSideLogging:267->checkLogging:764
> [INFO]
> [ERROR] Tests run: 51, Failures: 8, Errors: 0, Skipped: 0
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[View Less]
5 years, 4 months