Details
Description
While attempting to reproduce JBEAP-24150 with 8.0.0.Beta-CR1, I tried out the reproducer from JBEAP-24130. The reproducer needs to have one of it's classes migrated to jakarta dependencies (javax.ejb to jakarta.ejb) before it can be used. But before I realized that, I tried deploying it with no changes. The result was that it deployed successfully, but the EJB within wasn't recognized and published.
The problem here is that the server did not warn me and did not throw an exception when I deployed the jar which had the unsatisfied dependency on javax.ejb and I was left searching on my own what the problem was.
Server log snippet from EAP 7.4 (expected behavior):
...
11:54:49,557 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
...
11:54:50,102 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'Hello' in deployment unit 'deployment "JBEAP-24130.jar"' are as follows:
java:global/JBEAP-24130/Hello!com.jboss.examples.ejb.Hello
java:app/JBEAP-24130/Hello!com.jboss.examples.ejb.Hello
java:module/Hello!com.jboss.examples.ejb.Hello
java:jboss/exported/JBEAP-24130/Hello!com.jboss.examples.ejb.Hello
ejb:/JBEAP-24130/Hello!com.jboss.examples.ejb.Hello
java:global/JBEAP-24130/Hello
java:app/JBEAP-24130/Hello
java:module/Hello
...
11:54:50,977 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.4.2.GA (WildFly Core 15.0.5.Final-redhat-00001) started in 3300ms - Started 449 of 648 services (346 services are lazy, passive or on-demand)
...
Server log snippet from EAP 8.0.0.Beta-CR1:
... 11:20:57,668 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete ... 11:20:57,757 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "JBEAP-24130.jar" (runtime-name: "JBEAP-24130.jar") ... 11:20:57,996 INFO [org.jboss.as.server] (ServerService Thread Pool -- 43) WFLYSRV0010: Deployed "JBEAP-24130.jar" (runtime-name : "JBEAP-24130.jar") ... 11:20:58,042 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 8.0.0.Beta (WildFly Core 19.0.0.Beta16-redhat-00004) started in 2299ms - Started 355 of 596 services (347 services are lazy, passive or on-demand) - Server configuration file in use: standalone.xml
As expected, with 8.0.Beta, the client within the reproducer then failed with:
org.jboss.ejb.client.RequestSendFailedException: EJBCLIENT000409: No more destinations are available ... Suppressed: org.jboss.ejb.client.RequestSendFailedException: org.jboss.remoting3.ServiceOpenException: Unknown service name jboss.ejb@remote+http://localhost:8080 ...
Attachments
Issue Links
- is cloned by
-
WFLY-18749 Deploying a jar with unsatisfied dependencies does not warn/throw an exception
-
- Pull Request Sent
-