[JBoss JIRA] (WFLY-10349) WeldBundledLibraryDeployment Test cases fail on IBM jdk
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10349?page=com.atlassian.jira.plugin... ]
Petr Kremensky reassigned WFLY-10349:
-------------------------------------
Assignee: Petr Kremensky (was: Martin Kouba)
> WeldBundledLibraryDeployment Test cases fail on IBM jdk
> -------------------------------------------------------
>
> Key: WFLY-10349
> URL: https://issues.jboss.org/browse/WFLY-10349
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Test Suite
> Environment: {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 1.8.0_161, vendor: IBM Corporation
> Java home: /usr/lib/java/ibm-java-8.0-5.11/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.15.17-300.fc27.x86_64", arch: "amd64", family: "unix"
> $ git rev-parse --short HEAD
> 11e21f08d3
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Petr Kremensky
>
> WeldBundledLibraryDeploymentEarTestCase and WeldBundledLibraryDeploymentTestCase fails on IBM jdk.
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -B -DskipTests
> cd testsuite/integration/basic
> mvn test -Dtest=WeldBundledLibraryDeploymentEarTestCase,WeldBundledLibraryDeploymentTestCase -DtestLogToFile=false
> ...
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] WeldBundledLibraryDeploymentEarTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentEarTestCase » Deployment
> [ERROR] WeldBundledLibraryDeploymentTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
>
> *server log errors*
> {noformat}
> 11:56:22,104 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.extension-index: org.jboss.msc.service.StartException in service jboss.deployment.extension-index: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:811)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.server.moduleservice.ExtensionIndexService.start(ExtensionIndexService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> ... 6 more
> 11:56:22,260 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> 11:56:22,261 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear" was rolled back with the following failure message:
> {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10349) WeldBundledLibraryDeployment Test cases fail on IBM jdk
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10349?page=com.atlassian.jira.plugin... ]
Petr Kremensky updated WFLY-10349:
----------------------------------
Component/s: (was: CDI / Weld)
> WeldBundledLibraryDeployment Test cases fail on IBM jdk
> -------------------------------------------------------
>
> Key: WFLY-10349
> URL: https://issues.jboss.org/browse/WFLY-10349
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Environment: {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 1.8.0_161, vendor: IBM Corporation
> Java home: /usr/lib/java/ibm-java-8.0-5.11/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.15.17-300.fc27.x86_64", arch: "amd64", family: "unix"
> $ git rev-parse --short HEAD
> 11e21f08d3
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Petr Kremensky
>
> WeldBundledLibraryDeploymentEarTestCase and WeldBundledLibraryDeploymentTestCase fails on IBM jdk.
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -B -DskipTests
> cd testsuite/integration/basic
> mvn test -Dtest=WeldBundledLibraryDeploymentEarTestCase,WeldBundledLibraryDeploymentTestCase -DtestLogToFile=false
> ...
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] WeldBundledLibraryDeploymentEarTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentEarTestCase » Deployment
> [ERROR] WeldBundledLibraryDeploymentTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
>
> *server log errors*
> {noformat}
> 11:56:22,104 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.extension-index: org.jboss.msc.service.StartException in service jboss.deployment.extension-index: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:811)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.server.moduleservice.ExtensionIndexService.start(ExtensionIndexService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> ... 6 more
> 11:56:22,260 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> 11:56:22,261 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear" was rolled back with the following failure message:
> {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10349) WeldBundledLibraryDeployment Test cases fail on IBM jdk
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10349?page=com.atlassian.jira.plugin... ]
Petr Kremensky commented on WFLY-10349:
---------------------------------------
On my local machine, the exception is thrown while {{ExtensionIndexService}} is processing the ibm-java-8.0-5.11/jre/lib/ext/traceformat.jar file. I'll remove the weld from the component list.
> WeldBundledLibraryDeployment Test cases fail on IBM jdk
> -------------------------------------------------------
>
> Key: WFLY-10349
> URL: https://issues.jboss.org/browse/WFLY-10349
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Test Suite
> Environment: {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 1.8.0_161, vendor: IBM Corporation
> Java home: /usr/lib/java/ibm-java-8.0-5.11/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.15.17-300.fc27.x86_64", arch: "amd64", family: "unix"
> $ git rev-parse --short HEAD
> 11e21f08d3
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Martin Kouba
>
> WeldBundledLibraryDeploymentEarTestCase and WeldBundledLibraryDeploymentTestCase fails on IBM jdk.
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -B -DskipTests
> cd testsuite/integration/basic
> mvn test -Dtest=WeldBundledLibraryDeploymentEarTestCase,WeldBundledLibraryDeploymentTestCase -DtestLogToFile=false
> ...
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] WeldBundledLibraryDeploymentEarTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentEarTestCase » Deployment
> [ERROR] WeldBundledLibraryDeploymentTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
>
> *server log errors*
> {noformat}
> 11:56:22,104 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.extension-index: org.jboss.msc.service.StartException in service jboss.deployment.extension-index: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:811)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.server.moduleservice.ExtensionIndexService.start(ExtensionIndexService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> ... 6 more
> 11:56:22,260 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> 11:56:22,261 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear" was rolled back with the following failure message:
> {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2352) Executable model test coverage: run the optaplanner turtleTests with the executable model turned on and see if it survives the ordeal
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2352?page=com.atlassian.jira.plugi... ]
Tibor Zimányi commented on DROOLS-2352:
---------------------------------------
New issue reported based on the tests results: https://issues.jboss.org/browse/DROOLS-2537
> Executable model test coverage: run the optaplanner turtleTests with the executable model turned on and see if it survives the ordeal
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2352
> URL: https://issues.jboss.org/browse/DROOLS-2352
> Project: Drools
> Issue Type: Task
> Components: core engine
> Reporter: Geoffrey De Smet
> Assignee: Tibor Zimányi
>
> For now, we're looking for a one time test. Later I presume the exe model will be come the default, so these tests would just run?
> To run the optaplanner turtle tests, run all tests in optaplanner-examples with the VM parameter `-DrunTurtleTests=true`. They take 48 hours to run. You can also just run one, for example NurseRosteringSolveAllTurtleTest, but don't forget that VM parameter.
> Mario Fusco says you can do this to turn on the executable model:
> {code}
> kieBuilder.buildAll( ExecutableModelProject.class );
> {code}
> I presume you 'd need to hack that in `ScoreDirectorFactoryConfig.buildDroolsScoreDirectorFactory()`.
> Note: I have no idea if this even make sense: those turtle tests use a drl file input and don't use the kie-maven-plugin. We're looking for a switch to just turn it on and see if they are all still green. Mario thinks it's possible, if I understand it correctly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10349) WeldBundledLibraryDeployment Test cases fail on IBM jdk
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/WFLY-10349?page=com.atlassian.jira.plugin... ]
Matej Novotny commented on WFLY-10349:
--------------------------------------
[~pkremens] the related IBM issue seems to be [this one|http://www-01.ibm.com/support/docview.wss?uid=swg1IJ02283].
Note that it *was closed as program error _(not resolved in 8.0.5.6)_* which seems wrong. We had a similar query somewhere, either in Weld issue tracker or in mails, I am trying to dig that up.
> WeldBundledLibraryDeployment Test cases fail on IBM jdk
> -------------------------------------------------------
>
> Key: WFLY-10349
> URL: https://issues.jboss.org/browse/WFLY-10349
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Test Suite
> Environment: {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 1.8.0_161, vendor: IBM Corporation
> Java home: /usr/lib/java/ibm-java-8.0-5.11/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.15.17-300.fc27.x86_64", arch: "amd64", family: "unix"
> $ git rev-parse --short HEAD
> 11e21f08d3
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Martin Kouba
>
> WeldBundledLibraryDeploymentEarTestCase and WeldBundledLibraryDeploymentTestCase fails on IBM jdk.
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -B -DskipTests
> cd testsuite/integration/basic
> mvn test -Dtest=WeldBundledLibraryDeploymentEarTestCase,WeldBundledLibraryDeploymentTestCase -DtestLogToFile=false
> ...
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] WeldBundledLibraryDeploymentEarTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentEarTestCase » Deployment
> [ERROR] WeldBundledLibraryDeploymentTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
>
> *server log errors*
> {noformat}
> 11:56:22,104 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.extension-index: org.jboss.msc.service.StartException in service jboss.deployment.extension-index: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:811)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.server.moduleservice.ExtensionIndexService.start(ExtensionIndexService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> ... 6 more
> 11:56:22,260 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> 11:56:22,261 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear" was rolled back with the following failure message:
> {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10349) WeldBundledLibraryDeployment Test cases fail on IBM jdk
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10349?page=com.atlassian.jira.plugin... ]
Petr Kremensky commented on WFLY-10349:
---------------------------------------
>From server log,
{noformat}
Caused by: java.lang.NullPointerException
at org.jboss.as.server.moduleservice.ExtensionIndexService.start(ExtensionIndexService.java:94)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
{noformat}
this looks like the problematic part:
{code:title=Bar.java}
final Manifest manifest = jarFile.getManifest();
final Attributes mainAttributes = manifest.getMainAttributes();
{code}
TestCase:
{code:title=WeldBundledLibraryDeploymentTestCase.java}
jar.setManifest(new StringAsset("Extension-List: weld1\nweld1-Extension-Name: " + EXTENSION_NAME + "\n"));
{code}
> WeldBundledLibraryDeployment Test cases fail on IBM jdk
> -------------------------------------------------------
>
> Key: WFLY-10349
> URL: https://issues.jboss.org/browse/WFLY-10349
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Test Suite
> Environment: {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 1.8.0_161, vendor: IBM Corporation
> Java home: /usr/lib/java/ibm-java-8.0-5.11/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.15.17-300.fc27.x86_64", arch: "amd64", family: "unix"
> $ git rev-parse --short HEAD
> 11e21f08d3
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Martin Kouba
>
> WeldBundledLibraryDeploymentEarTestCase and WeldBundledLibraryDeploymentTestCase fails on IBM jdk.
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -B -DskipTests
> cd testsuite/integration/basic
> mvn test -Dtest=WeldBundledLibraryDeploymentEarTestCase,WeldBundledLibraryDeploymentTestCase -DtestLogToFile=false
> ...
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] WeldBundledLibraryDeploymentEarTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentEarTestCase » Deployment
> [ERROR] WeldBundledLibraryDeploymentTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
>
> *server log errors*
> {noformat}
> 11:56:22,104 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.extension-index: org.jboss.msc.service.StartException in service jboss.deployment.extension-index: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:811)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.server.moduleservice.ExtensionIndexService.start(ExtensionIndexService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> ... 6 more
> 11:56:22,260 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> 11:56:22,261 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear" was rolled back with the following failure message:
> {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10349) WeldBundledLibraryDeployment Test cases fail on IBM jdk
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10349?page=com.atlassian.jira.plugin... ]
Petr Kremensky edited comment on WFLY-10349 at 5/10/18 2:52 AM:
----------------------------------------------------------------
>From server log,
{noformat}
Caused by: java.lang.NullPointerException
at org.jboss.as.server.moduleservice.ExtensionIndexService.start(ExtensionIndexService.java:94)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
{noformat}
this looks like the problematic part:
{code:title=ExtensionIndexService.java}
final Manifest manifest = jarFile.getManifest();
final Attributes mainAttributes = manifest.getMainAttributes();
{code}
TestCase:
{code:title=WeldBundledLibraryDeploymentTestCase.java}
jar.setManifest(new StringAsset("Extension-List: weld1\nweld1-Extension-Name: " + EXTENSION_NAME + "\n"));
{code}
was (Author: pkremens):
>From server log,
{noformat}
Caused by: java.lang.NullPointerException
at org.jboss.as.server.moduleservice.ExtensionIndexService.start(ExtensionIndexService.java:94)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
{noformat}
this looks like the problematic part:
{code:title=Bar.java}
final Manifest manifest = jarFile.getManifest();
final Attributes mainAttributes = manifest.getMainAttributes();
{code}
TestCase:
{code:title=WeldBundledLibraryDeploymentTestCase.java}
jar.setManifest(new StringAsset("Extension-List: weld1\nweld1-Extension-Name: " + EXTENSION_NAME + "\n"));
{code}
> WeldBundledLibraryDeployment Test cases fail on IBM jdk
> -------------------------------------------------------
>
> Key: WFLY-10349
> URL: https://issues.jboss.org/browse/WFLY-10349
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Test Suite
> Environment: {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 1.8.0_161, vendor: IBM Corporation
> Java home: /usr/lib/java/ibm-java-8.0-5.11/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.15.17-300.fc27.x86_64", arch: "amd64", family: "unix"
> $ git rev-parse --short HEAD
> 11e21f08d3
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Martin Kouba
>
> WeldBundledLibraryDeploymentEarTestCase and WeldBundledLibraryDeploymentTestCase fails on IBM jdk.
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -B -DskipTests
> cd testsuite/integration/basic
> mvn test -Dtest=WeldBundledLibraryDeploymentEarTestCase,WeldBundledLibraryDeploymentTestCase -DtestLogToFile=false
> ...
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] WeldBundledLibraryDeploymentEarTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentEarTestCase » Deployment
> [ERROR] WeldBundledLibraryDeploymentTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
>
> *server log errors*
> {noformat}
> 11:56:22,104 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.extension-index: org.jboss.msc.service.StartException in service jboss.deployment.extension-index: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:811)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.server.moduleservice.ExtensionIndexService.start(ExtensionIndexService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> ... 6 more
> 11:56:22,260 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> 11:56:22,261 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear" was rolled back with the following failure message:
> {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months