[JBoss JIRA] (WFLY-10530) Domain test failures on IBM8 - IllegalStateException: The LogManager was not properly installed
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-10530?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-10530:
--------------------------------------
Yes. I've seen an issue like this before with another test and it had to do, IIRC, with they way the IBM JDK initialized a logger very early which caused the issue.
> Domain test failures on IBM8 - IllegalStateException: The LogManager was not properly installed
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-10530
> URL: https://issues.jboss.org/browse/WFLY-10530
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Petr Kremensky
> Assignee: James Perkins
> Priority: Major
>
> org.jboss.as.test.integration.domain.suites.DeploymentOverlayTestCase#testDeploymentOverlayInDomainMode and org.jboss.as.test.integration.domain.suites.ReadEnvironmentVariablesTestCase#testReadEnvironmentVariablesForServers from domain module of Wildfly testsuite fails on the latest IBM 8 jdk with java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
> *reproduce*
> {noformat}
> wildfly/testsuite]$ mvn test -DtestLogToFile=false -pl domain -Dts.domain -Dtest=ReadEnvironmentVariablesTestCase,DeploymentOverlayTestCase
> ...
> [ERROR] Errors:
> [ERROR] DeploymentOverlayTestCase.testDeploymentOverlayInDomainMode:300->performHttpCall:340 » NoClassDefFound
> [ERROR] ReadEnvironmentVariablesTestCase.testReadEnvironmentVariablesForServers:109->getEnvironmentVariables:148 » ExceptionInInitializer
> [INFO]
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
> *Failure message*
> {noformat}
> java.lang.ExceptionInInitializerError
> at java.lang.J9VMInternals.ensureError(J9VMInternals.java:146)
> at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:135)
> at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:316)
> at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:329)
> at org.apache.http.conn.ssl.DefaultHostnameVerifier.<init>(DefaultHostnameVerifier.java:72)
> at org.apache.http.impl.client.HttpClientBuilder.build(HttpClientBuilder.java:955)
> at org.apache.http.impl.client.HttpClients.createDefault(HttpClients.java:58)
> at org.jboss.as.test.integration.domain.suites.ReadEnvironmentVariablesTestCase.getEnvironmentVariables(ReadEnvironmentVariablesTestCase.java:148)
> at org.jboss.as.test.integration.domain.suites.ReadEnvironmentVariablesTestCase.testReadEnvironmentVariablesForServers(ReadEnvironmentVariablesTestCase.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> 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.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> 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.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:379)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:340)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:413)
> Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
> at org.jboss.logmanager.Logger.getLogger(Logger.java:57)
> at org.apache.commons.logging.JBossLogFactory.<init>(JBossLogFactory.java:48)
> at org.apache.commons.logging.LogFactory$Holder.<clinit>(LogFactory.java:42)
> ... 44 more
> {noformat}
> *Environment*
> {noformat}
> $ mvn -version
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z)
> Maven home: /qa/tools/opt/maven3-latest
> Java version: 1.8.0_171, vendor: IBM Corporation
> Java home: /qa/tools/opt/x86_64/ibm-java-x86_64-sdk-8.0-5.15/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-862.el7.x86_64", arch: "amd64", family: "unix"
> ---
> $ java -version
> java version "1.8.0_171"
> Java(TM) SE Runtime Environment (build 8.0.5.15 - pxa6480sr5fp15-20180502_01(SR5 FP15))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180425_385365 (JIT enabled, AOT enabled)
> OpenJ9 - a7ffbfe
> OMR - a531219
> IBM - 59ef3dc)
> JCL - 20180425_01 based on Oracle jdk8u171-b11
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10530) Domain test failures on IBM8 - IllegalStateException: The LogManager was not properly installed
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-10530?page=com.atlassian.jira.plugin... ]
James Perkins reassigned WFLY-10530:
------------------------------------
Assignee: James Perkins
> Domain test failures on IBM8 - IllegalStateException: The LogManager was not properly installed
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-10530
> URL: https://issues.jboss.org/browse/WFLY-10530
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Petr Kremensky
> Assignee: James Perkins
> Priority: Major
>
> org.jboss.as.test.integration.domain.suites.DeploymentOverlayTestCase#testDeploymentOverlayInDomainMode and org.jboss.as.test.integration.domain.suites.ReadEnvironmentVariablesTestCase#testReadEnvironmentVariablesForServers from domain module of Wildfly testsuite fails on the latest IBM 8 jdk with java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
> *reproduce*
> {noformat}
> wildfly/testsuite]$ mvn test -DtestLogToFile=false -pl domain -Dts.domain -Dtest=ReadEnvironmentVariablesTestCase,DeploymentOverlayTestCase
> ...
> [ERROR] Errors:
> [ERROR] DeploymentOverlayTestCase.testDeploymentOverlayInDomainMode:300->performHttpCall:340 » NoClassDefFound
> [ERROR] ReadEnvironmentVariablesTestCase.testReadEnvironmentVariablesForServers:109->getEnvironmentVariables:148 » ExceptionInInitializer
> [INFO]
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
> *Failure message*
> {noformat}
> java.lang.ExceptionInInitializerError
> at java.lang.J9VMInternals.ensureError(J9VMInternals.java:146)
> at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:135)
> at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:316)
> at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:329)
> at org.apache.http.conn.ssl.DefaultHostnameVerifier.<init>(DefaultHostnameVerifier.java:72)
> at org.apache.http.impl.client.HttpClientBuilder.build(HttpClientBuilder.java:955)
> at org.apache.http.impl.client.HttpClients.createDefault(HttpClients.java:58)
> at org.jboss.as.test.integration.domain.suites.ReadEnvironmentVariablesTestCase.getEnvironmentVariables(ReadEnvironmentVariablesTestCase.java:148)
> at org.jboss.as.test.integration.domain.suites.ReadEnvironmentVariablesTestCase.testReadEnvironmentVariablesForServers(ReadEnvironmentVariablesTestCase.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> 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.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> 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.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:379)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:340)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:413)
> Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
> at org.jboss.logmanager.Logger.getLogger(Logger.java:57)
> at org.apache.commons.logging.JBossLogFactory.<init>(JBossLogFactory.java:48)
> at org.apache.commons.logging.LogFactory$Holder.<clinit>(LogFactory.java:42)
> ... 44 more
> {noformat}
> *Environment*
> {noformat}
> $ mvn -version
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z)
> Maven home: /qa/tools/opt/maven3-latest
> Java version: 1.8.0_171, vendor: IBM Corporation
> Java home: /qa/tools/opt/x86_64/ibm-java-x86_64-sdk-8.0-5.15/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-862.el7.x86_64", arch: "amd64", family: "unix"
> ---
> $ java -version
> java version "1.8.0_171"
> Java(TM) SE Runtime Environment (build 8.0.5.15 - pxa6480sr5fp15-20180502_01(SR5 FP15))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180425_385365 (JIT enabled, AOT enabled)
> OpenJ9 - a7ffbfe
> OMR - a531219
> IBM - 59ef3dc)
> JCL - 20180425_01 based on Oracle jdk8u171-b11
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11121) CI - Master linux JDK 11 job - compilation fails - forked embedded process has failed
by Ken Wills (Jira)
[ https://issues.jboss.org/browse/WFLY-11121?page=com.atlassian.jira.plugin... ]
Ken Wills edited comment on WFLY-11121 at 10/5/18 10:12 AM:
------------------------------------------------------------
I'm happy to help with this on CI, but this issue should not be assigned to me, IMO.
If I'm wrong, please reassign it back to me, and let me know what you need me to do :)
was (Author: luck3y):
I'm happy to help with this on CI, but this issue should not be assigned to me, IMO.
If I'm wrong, please reassign it back to me, and let me know what you need be to do :)
> CI - Master linux JDK 11 job - compilation fails - forked embedded process has failed
> --------------------------------------------------------------------------------------
>
> Key: WFLY-11121
> URL: https://issues.jboss.org/browse/WFLY-11121
> Project: WildFly
> Issue Type: Bug
> Reporter: Rostislav Svoboda
> Assignee: Jason Greene
> Priority: Blocker
> Labels: Java11
>
> Compilation of Master linux JDK 11 job fails - forked embedded process has failed.
> https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk11
> {code}
> [Step 2/3] [ERROR] Failed to execute goal org.wildfly.galleon-plugins:wildfly-galleon-maven-plugin:
> 2.0.0.Final:generate-feature-specs (feature-spec-build) on project wildfly-servlet-galleon-pack:
> Feature spec generator failed: Forked embedded process has failed -> [Help 1]
> {code}
> My local machine runs are passing for me, using {{java version "11" 2018-09-25 (build 11+28)}}
> This fail can be related to VMs setup on TeamCity, another option can be galleon related issue.
> CCing also [~aloubyansky]
> We need to have valid Java 11 runs on upstream to guard proper functionality of WildFly.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11121) CI - Master linux JDK 11 job - compilation fails - forked embedded process has failed
by Ken Wills (Jira)
[ https://issues.jboss.org/browse/WFLY-11121?page=com.atlassian.jira.plugin... ]
Ken Wills commented on WFLY-11121:
----------------------------------
I'm happy to help with this on CI, but this issue should not be assigned to me, IMO.
If I'm wrong, please reassign it back to me, and let me know what you need be to do :)
> CI - Master linux JDK 11 job - compilation fails - forked embedded process has failed
> --------------------------------------------------------------------------------------
>
> Key: WFLY-11121
> URL: https://issues.jboss.org/browse/WFLY-11121
> Project: WildFly
> Issue Type: Bug
> Reporter: Rostislav Svoboda
> Assignee: Ken Wills
> Priority: Blocker
> Labels: Java11
>
> Compilation of Master linux JDK 11 job fails - forked embedded process has failed.
> https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk11
> {code}
> [Step 2/3] [ERROR] Failed to execute goal org.wildfly.galleon-plugins:wildfly-galleon-maven-plugin:
> 2.0.0.Final:generate-feature-specs (feature-spec-build) on project wildfly-servlet-galleon-pack:
> Feature spec generator failed: Forked embedded process has failed -> [Help 1]
> {code}
> My local machine runs are passing for me, using {{java version "11" 2018-09-25 (build 11+28)}}
> This fail can be related to VMs setup on TeamCity, another option can be galleon related issue.
> CCing also [~aloubyansky]
> We need to have valid Java 11 runs on upstream to guard proper functionality of WildFly.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11121) CI - Master linux JDK 11 job - compilation fails - forked embedded process has failed
by Ken Wills (Jira)
[ https://issues.jboss.org/browse/WFLY-11121?page=com.atlassian.jira.plugin... ]
Ken Wills reassigned WFLY-11121:
--------------------------------
Assignee: Jason Greene (was: Ken Wills)
> CI - Master linux JDK 11 job - compilation fails - forked embedded process has failed
> --------------------------------------------------------------------------------------
>
> Key: WFLY-11121
> URL: https://issues.jboss.org/browse/WFLY-11121
> Project: WildFly
> Issue Type: Bug
> Reporter: Rostislav Svoboda
> Assignee: Jason Greene
> Priority: Blocker
> Labels: Java11
>
> Compilation of Master linux JDK 11 job fails - forked embedded process has failed.
> https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk11
> {code}
> [Step 2/3] [ERROR] Failed to execute goal org.wildfly.galleon-plugins:wildfly-galleon-maven-plugin:
> 2.0.0.Final:generate-feature-specs (feature-spec-build) on project wildfly-servlet-galleon-pack:
> Feature spec generator failed: Forked embedded process has failed -> [Help 1]
> {code}
> My local machine runs are passing for me, using {{java version "11" 2018-09-25 (build 11+28)}}
> This fail can be related to VMs setup on TeamCity, another option can be galleon related issue.
> CCing also [~aloubyansky]
> We need to have valid Java 11 runs on upstream to guard proper functionality of WildFly.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10529) ParseAndMarshalModelsTestCase fails on the latest IBM8 with Failed to register MBean with MBeanServer
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-10529?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-10529:
------------------------------------
Comment: was deleted
(was: The CLI is not relevant.)
> ParseAndMarshalModelsTestCase fails on the latest IBM8 with Failed to register MBean with MBeanServer
> -----------------------------------------------------------------------------------------------------
>
> Key: WFLY-10529
> URL: https://issues.jboss.org/browse/WFLY-10529
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Petr Kremensky
> Priority: Major
>
> org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase from manualmode module of wildlfy testsuite fails with the latest IBM 8 JDK bits.
> *reproduce*
> {noformat}
> wildfly/testsuite]$ mvn test -DtestLogToFile=false -pl integration/manualmode -Dts.manualmode -Dtest=ParseAndMarshalModelsTestCase
> ...
> [ERROR] Tests run: 40, Failures: 40, Errors: 0, Skipped: 0
> {noformat}
> *Error message appearing in the logs*
> {noformat}
> Jun 07, 2018 3:57:14 PM org.jboss.msc.service.ServiceContainerImpl <init>
> ERROR: MSC000010: Failed to register MBean with MBeanServer
> javax.management.InstanceAlreadyExistsException: jboss.msc:type=container,name=host-controller
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:449)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1910)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:978)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:912)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:336)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:534)
> at org.jboss.msc.service.ServiceContainerImpl.<init>(ServiceContainerImpl.java:368)
> at org.jboss.msc.service.ServiceContainer$Factory.create(ServiceContainer.java:221)
> at org.wildfly.core.embedded.EmbeddedHostControllerBootstrap$ShutdownHook.register(EmbeddedHostControllerBootstrap.java:90)
> at org.wildfly.core.embedded.EmbeddedHostControllerBootstrap$ShutdownHook.access$100(EmbeddedHostControllerBootstrap.java:80)
> at org.wildfly.core.embedded.EmbeddedHostControllerBootstrap.<init>(EmbeddedHostControllerBootstrap.java:54)
> at org.wildfly.core.embedded.EmbeddedHostControllerFactory$HostControllerImpl.start(EmbeddedHostControllerFactory.java:270)
> at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:88)
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:58)
> at org.jboss.as.cli.embedded.EmbedHostControllerHandler.doHandle(EmbedHostControllerHandler.java:268)
> at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:89)
> at org.jboss.as.cli.impl.CommandExecutor$2.lambda$build$0(CommandExecutor.java:685)
> at org.jboss.as.cli.impl.CommandExecutor$2$$Lambda$79.00000000200064E0.execute(Unknown Source)
> at org.jboss.as.cli.impl.CommandExecutor.lambda$execute$0(CommandExecutor.java:708)
> at org.jboss.as.cli.impl.CommandExecutor$$Lambda$78.00000000AD3CF710.call(Unknown Source)
> at java.util.concurrent.FutureTask.run(FutureTask.java:277)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.lang.Thread.run(Thread.java:811)
> {noformat}
> *Failure cause*
> {noformat}
> Caused by: org.jboss.as.cli.CommandLineException: Cannot start embedded server
> at org.jboss.as.cli.embedded.EmbedServerHandler.doHandle(EmbedServerHandler.java:300)
> at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:89)
> at org.jboss.as.cli.impl.CommandExecutor$2.lambda$build$0(CommandExecutor.java:685)
> at org.jboss.as.cli.impl.CommandExecutor$2$$Lambda$79.00000000200064E0.execute(Unknown Source)
> at org.jboss.as.cli.impl.CommandExecutor.lambda$execute$0(CommandExecutor.java:708)
> at org.jboss.as.cli.impl.CommandExecutor$$Lambda$78.00000000AD3CF710.call(Unknown Source)
> at java.util.concurrent.FutureTask.run(FutureTask.java:277)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.lang.Thread.run(Thread.java:811)
> Caused by: java.lang.ClassCastException: org.jboss.as.controller.client.helpers.DelegatingModelControllerClient incompatible with org.jboss.as.controller.client.ModelControllerClient
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.getModelControllerClient(EmbeddedManagedProcessImpl.java:72)
> at org.jboss.as.cli.embedded.EmbedServerHandler.doHandle(EmbedServerHandler.java:244)
> ... 9 more
> {noformat}
> *Environment*
> {noformat}
> $ mvn -version
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z)
> Maven home: /qa/tools/opt/maven3-latest
> Java version: 1.8.0_171, vendor: IBM Corporation
> Java home: /qa/tools/opt/x86_64/ibm-java-x86_64-sdk-8.0-5.15/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-862.el7.x86_64", arch: "amd64", family: "unix"
> ---
> $ java -version
> java version "1.8.0_171"
> Java(TM) SE Runtime Environment (build 8.0.5.15 - pxa6480sr5fp15-20180502_01(SR5 FP15))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180425_385365 (JIT enabled, AOT enabled)
> OpenJ9 - a7ffbfe
> OMR - a531219
> IBM - 59ef3dc)
> JCL - 20180425_01 based on Oracle jdk8u171-b11
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10529) ParseAndMarshalModelsTestCase fails on the latest IBM8 with Failed to register MBean with MBeanServer
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-10529?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-10529:
-----------------------------------------
The CLI is not relevant.
> ParseAndMarshalModelsTestCase fails on the latest IBM8 with Failed to register MBean with MBeanServer
> -----------------------------------------------------------------------------------------------------
>
> Key: WFLY-10529
> URL: https://issues.jboss.org/browse/WFLY-10529
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Petr Kremensky
> Priority: Major
>
> org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase from manualmode module of wildlfy testsuite fails with the latest IBM 8 JDK bits.
> *reproduce*
> {noformat}
> wildfly/testsuite]$ mvn test -DtestLogToFile=false -pl integration/manualmode -Dts.manualmode -Dtest=ParseAndMarshalModelsTestCase
> ...
> [ERROR] Tests run: 40, Failures: 40, Errors: 0, Skipped: 0
> {noformat}
> *Error message appearing in the logs*
> {noformat}
> Jun 07, 2018 3:57:14 PM org.jboss.msc.service.ServiceContainerImpl <init>
> ERROR: MSC000010: Failed to register MBean with MBeanServer
> javax.management.InstanceAlreadyExistsException: jboss.msc:type=container,name=host-controller
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:449)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1910)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:978)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:912)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:336)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:534)
> at org.jboss.msc.service.ServiceContainerImpl.<init>(ServiceContainerImpl.java:368)
> at org.jboss.msc.service.ServiceContainer$Factory.create(ServiceContainer.java:221)
> at org.wildfly.core.embedded.EmbeddedHostControllerBootstrap$ShutdownHook.register(EmbeddedHostControllerBootstrap.java:90)
> at org.wildfly.core.embedded.EmbeddedHostControllerBootstrap$ShutdownHook.access$100(EmbeddedHostControllerBootstrap.java:80)
> at org.wildfly.core.embedded.EmbeddedHostControllerBootstrap.<init>(EmbeddedHostControllerBootstrap.java:54)
> at org.wildfly.core.embedded.EmbeddedHostControllerFactory$HostControllerImpl.start(EmbeddedHostControllerFactory.java:270)
> at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:88)
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:58)
> at org.jboss.as.cli.embedded.EmbedHostControllerHandler.doHandle(EmbedHostControllerHandler.java:268)
> at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:89)
> at org.jboss.as.cli.impl.CommandExecutor$2.lambda$build$0(CommandExecutor.java:685)
> at org.jboss.as.cli.impl.CommandExecutor$2$$Lambda$79.00000000200064E0.execute(Unknown Source)
> at org.jboss.as.cli.impl.CommandExecutor.lambda$execute$0(CommandExecutor.java:708)
> at org.jboss.as.cli.impl.CommandExecutor$$Lambda$78.00000000AD3CF710.call(Unknown Source)
> at java.util.concurrent.FutureTask.run(FutureTask.java:277)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.lang.Thread.run(Thread.java:811)
> {noformat}
> *Failure cause*
> {noformat}
> Caused by: org.jboss.as.cli.CommandLineException: Cannot start embedded server
> at org.jboss.as.cli.embedded.EmbedServerHandler.doHandle(EmbedServerHandler.java:300)
> at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:89)
> at org.jboss.as.cli.impl.CommandExecutor$2.lambda$build$0(CommandExecutor.java:685)
> at org.jboss.as.cli.impl.CommandExecutor$2$$Lambda$79.00000000200064E0.execute(Unknown Source)
> at org.jboss.as.cli.impl.CommandExecutor.lambda$execute$0(CommandExecutor.java:708)
> at org.jboss.as.cli.impl.CommandExecutor$$Lambda$78.00000000AD3CF710.call(Unknown Source)
> at java.util.concurrent.FutureTask.run(FutureTask.java:277)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.lang.Thread.run(Thread.java:811)
> Caused by: java.lang.ClassCastException: org.jboss.as.controller.client.helpers.DelegatingModelControllerClient incompatible with org.jboss.as.controller.client.ModelControllerClient
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.getModelControllerClient(EmbeddedManagedProcessImpl.java:72)
> at org.jboss.as.cli.embedded.EmbedServerHandler.doHandle(EmbedServerHandler.java:244)
> ... 9 more
> {noformat}
> *Environment*
> {noformat}
> $ mvn -version
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z)
> Maven home: /qa/tools/opt/maven3-latest
> Java version: 1.8.0_171, vendor: IBM Corporation
> Java home: /qa/tools/opt/x86_64/ibm-java-x86_64-sdk-8.0-5.15/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-862.el7.x86_64", arch: "amd64", family: "unix"
> ---
> $ java -version
> java version "1.8.0_171"
> Java(TM) SE Runtime Environment (build 8.0.5.15 - pxa6480sr5fp15-20180502_01(SR5 FP15))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180425_385365 (JIT enabled, AOT enabled)
> OpenJ9 - a7ffbfe
> OMR - a531219
> IBM - 59ef3dc)
> JCL - 20180425_01 based on Oracle jdk8u171-b11
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3073) Wrong full package if you use classes from another folder
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3073?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3073:
-------------------------------------
[~gabriolo] the attached [^scesim.zip] contains simple project where I created scesim asset in different package than rule and data object. When I click run I got exception, could you please have a look? One more question, after importing data object via *Data Objects* tab, I have to reopen the asset to be able use that data object in column definition is this correct?
> Wrong full package if you use classes from another folder
> ----------------------------------------------------------
>
> Key: DROOLS-3073
> URL: https://issues.jboss.org/browse/DROOLS-3073
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Major
> Attachments: Screenshot from 2018-10-05 15-32-12.png, scesim.zip
>
>
> Step to reproduce:
> - Create a Data Object "Object1" in a specific package (i.e. com.myspace.myproject)
> - Create a Test Scenario (Preview) "Test1" in a different package (i.e. com.myspace)
> - Use Data Objects tab to import "Object1" to "Test1"
> - Reload the asset and map a field of "Object1" to a column
> - Fill "Test1" with valid values
> - Run the scenario
> Result: Impossible to load class com.myspace.Object1
> Minor bug: if "Test1" has been create in default package the error that you get is "Impossible to load class *.*Object1" so it should be impossible to create the asset into default package or it should consider it to avoid "." symbol at the beginning
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3073) Wrong full package if you use classes from another folder
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3073?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3073:
--------------------------------
Attachment: scesim.zip
> Wrong full package if you use classes from another folder
> ----------------------------------------------------------
>
> Key: DROOLS-3073
> URL: https://issues.jboss.org/browse/DROOLS-3073
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Major
> Attachments: Screenshot from 2018-10-05 15-32-12.png, scesim.zip
>
>
> Step to reproduce:
> - Create a Data Object "Object1" in a specific package (i.e. com.myspace.myproject)
> - Create a Test Scenario (Preview) "Test1" in a different package (i.e. com.myspace)
> - Use Data Objects tab to import "Object1" to "Test1"
> - Reload the asset and map a field of "Object1" to a column
> - Fill "Test1" with valid values
> - Run the scenario
> Result: Impossible to load class com.myspace.Object1
> Minor bug: if "Test1" has been create in default package the error that you get is "Impossible to load class *.*Object1" so it should be impossible to create the asset into default package or it should consider it to avoid "." symbol at the beginning
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3073) Wrong full package if you use classes from another folder
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3073?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3073:
--------------------------------
Attachment: Screenshot from 2018-10-05 15-32-12.png
> Wrong full package if you use classes from another folder
> ----------------------------------------------------------
>
> Key: DROOLS-3073
> URL: https://issues.jboss.org/browse/DROOLS-3073
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Major
> Attachments: Screenshot from 2018-10-05 15-32-12.png
>
>
> Step to reproduce:
> - Create a Data Object "Object1" in a specific package (i.e. com.myspace.myproject)
> - Create a Test Scenario (Preview) "Test1" in a different package (i.e. com.myspace)
> - Use Data Objects tab to import "Object1" to "Test1"
> - Reload the asset and map a field of "Object1" to a column
> - Fill "Test1" with valid values
> - Run the scenario
> Result: Impossible to load class com.myspace.Object1
> Minor bug: if "Test1" has been create in default package the error that you get is "Impossible to load class *.*Object1" so it should be impossible to create the asset into default package or it should consider it to avoid "." symbol at the beginning
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months