[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 edited comment on WFLY-10349 at 5/10/18 4:39 AM:
---------------------------------------------------------------
Hmm, all I found is that when you create a JAR file there should be some default manifest added.
No requirement on it being there if you for some reason decide to get rid of it.
Also there is plenty of questions around the web on how to execute JARs without manifest files. That being said, it may not be legit of course :)
But WFLY core code clearly [doesn't account|https://github.com/wildfly/wildfly-core/blob/master/server/src/ma...] for that possibility, hence the NPE.
EDIT: Ah I see you just edited your comment Martin, so we are agreed on this one.
was (Author: manovotn):
Hmm, all I found is that when you create a JAR file there should be some default manifest added.
No requirement on it being there if you for some reason decide to get rid of it.
Also there is plenty of questions around the web on how to execute JARs without manifest files. That being said, it may not be legit of course :)
But WFLY core code clearly [doesn't account|https://github.com/wildfly/wildfly-core/blob/master/server/src/ma...] for that possibility, hence the NPE.
> 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] (WFCORE-3816) ExtensionIndexService throws NPE while reading extensions on the IBM jdk
by Petr Kremensky (JIRA)
Petr Kremensky created WFCORE-3816:
--------------------------------------
Summary: ExtensionIndexService throws NPE while reading extensions on the IBM jdk
Key: WFCORE-3816
URL: https://issues.jboss.org/browse/WFCORE-3816
Project: WildFly Core
Issue Type: Bug
Components: Server
Affects Versions: 5.0.0.Alpha7
Environment: {noformat}
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 8.0.5.11 - pxa6480sr5fp11-20180326_01(SR5 FP11))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180309_380776 (JIT enabled, AOT enabled)
OpenJ9 - 49fcaf39
OMR - 5cbbadf
IBM - 4453dac)
JCL - 20180319_01 based on Oracle jdk8u161-b12
{noformat}
Reporter: Petr Kremensky
Assignee: Petr Kremensky
https://github.com/wildfly/wildfly-core/blob/5.0.0.Alpha7/server/src/main... reads extensions from jars manifest like:
{code:java}
File jar = new File(<jar>)
final JarFile jarFile = new JarFile(jar);
final Manifest manifest = jarFile.getManifest();
final Attributes mainAttributes = manifest.getMainAttributes();
...
{code}
The latest [IBM jdk 8.0-5.11|https://developer.ibm.com/javasdk/downloads/sdk8/] (and possible some of previous releases) contains some jars \[1\] where {{manifest.getMainAttributes();}} throws NPE, causing deploy operation of archive with Extension-List to fail, see WFLY-10349.
\[1\]
ibm-java-8.0-5.11/jre/lib/ext/traceformat.jar: java.lang.NullPointerException
ibm-java-8.0-5.11/jre/lib/ext/dtfj.jar: java.lang.NullPointerException
ibm-java-8.0-5.11/jre/lib/ext/dtfjview.jar: java.lang.NullPointerException
--
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:
--------------------------------------
Hmm, all I found is that when you create a JAR file there should be some default manifest added.
No requirement on it being there if you for some reason decide to get rid of it.
Also there is plenty of questions around the web on how to execute JARs without manifest files. That being said, it may not be legit of course :)
But WFLY core code clearly [doesn't account|https://github.com/wildfly/wildfly-core/blob/master/server/src/ma...] for that possibility, hence the NPE.
> 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] (DROOLS-2539) [Guided Decision Table] Selected Cell highlight ignores hidden columns
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2539?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2539:
-----------------------------------
Summary: [Guided Decision Table] Selected Cell highlight ignores hidden columns (was: Selected Cell highlight ignores hidden columns)
> [Guided Decision Table] Selected Cell highlight ignores hidden columns
> ----------------------------------------------------------------------
>
> Key: DROOLS-2539
> URL: https://issues.jboss.org/browse/DROOLS-2539
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.7.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> If you create a Guided Decision Table and hide at least one column and then select on the "Row number" cell (selecting all cells on the row) the "Selection" highlight overflows the table. This is caused by the creation of the highlight ignoring hidden columns.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2539) Selected Cell highlight ignores hidden columns
by Michael Anstis (JIRA)
Michael Anstis created DROOLS-2539:
--------------------------------------
Summary: Selected Cell highlight ignores hidden columns
Key: DROOLS-2539
URL: https://issues.jboss.org/browse/DROOLS-2539
Project: Drools
Issue Type: Bug
Components: Guided Decision Table Editor
Affects Versions: 7.7.0.Final
Reporter: Michael Anstis
Assignee: Michael Anstis
If you create a Guided Decision Table and hide at least one column and then select on the "Row number" cell (selecting all cells on the row) the "Selection" highlight overflows the table. This is caused by the creation of the highlight ignoring hidden columns.
--
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 Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-10349?page=com.atlassian.jira.plugin... ]
Martin Kouba edited comment on WFLY-10349 at 5/10/18 4:28 AM:
--------------------------------------------------------------
It seems that {{traceformat.jar}} in 8.0-5.11 does not declare a manifest file. -I think it's mandatory, isn't it?- It's not as the META-INF directory is optional - see also https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html. So {{ExtensionIndexService}} should handle this correcly, i.e. {{java.util.jar.JarFile.getManifest()}} may return null.
was (Author: mkouba):
It seems that {{traceformat.jar}} in 8.0-5.11 does not declare a manifest file. I think it's mandatory, isn't it?
> 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 Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-10349?page=com.atlassian.jira.plugin... ]
Martin Kouba commented on WFLY-10349:
-------------------------------------
It seems that {{traceformat.jar}} in 8.0-5.11 does not declare a manifest file. I think it's mandatory, isn't it?
> 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] (DROOLS-2538) [DMN Designer] Save throws NPE
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2538:
-----------------------------------
Summary: [DMN Designer] Save throws NPE
Key: DROOLS-2538
URL: https://issues.jboss.org/browse/DROOLS-2538
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.8.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Priority: Critical
Attachments: null-pointer.png
Save of the diagram throws NPE, see the attachment.
--
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:
---------------------------------------
{code:java}
public class ManifestTest {
public static void main(String[] args) {
try {
File jar = new File("/usr/lib/java/ibm-java-8.0-5.11/jre/lib/ext/traceformat.jar");
final JarFile jarFile = new JarFile(jar);
final Manifest manifest = jarFile.getManifest();
final Attributes mainAttributes = manifest.getMainAttributes();
} catch (IOException ioe) {
ioe.printStackTrace();
} catch (NullPointerException npe) {
System.err.println("This one will pop-up through.");
}
}
}
{code}
{noformat}
This one will pop-up through.
{noformat}
> 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:
---------------------------------------
[~manovotn]
{code:java}
final Attributes mainAttributes = manifest.getMainAttributes();
{code}
is inside try {} catch (IOException e), I assume that problem here is that IBM jdk throws NPE in some cases where other vendors throw an instance of IOException. I'll try it out, should be an easy fix.
> 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