[
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)