.WeldStartService and .beanmanager not found

[Frank Griffin]

I have an EAR app that has been running for years under JBoss/WildFly.  I recently tried to migrate it to WildFly 29.0.0.Final, and I'm getting the following error.  This is a Maven project, and since I'd like this to be able to run under any standard EJB server I tend to avoid WF-specific XML files or modifications, although I do have a jboss-cli script to do WF-related configuration.  Also, this app dates from the EJB 2 days, so I tend to avoid annotations wherever possible, using the older XML descriptor files as much as possible.

The error occurs when trying to deploy the EAR:

13:58:42,818 ERROR [org.jboss.as.controller.management-operation] (DeploymentScann
er-threads - 1) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {
   "WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"dvd-ear.ear\".\
"org.profsoftsvcs-dvd-ejb-1.0-SNAPSHOT.jar\".POST_MODULE" => "WFLYSRV0153: Failed
to process phase POST_MODULE of subdeployment \"org.profsoftsvcs-dvd-ejb-1.0-SNAPS
HOT.jar\" of deployment \"dvd-ear.ear\"
   Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for interface javax.ejb.SessionBean with ClassLoader ModuleClassLoader
for Module \"deployment.dvd-ear.ear\" from Service Module Loader
   Caused by: java.lang.ClassFormatError: Failed to link javax/ejb/EJBException (
Module \"deployment.dvd-ear.ear\" from Service Module Loader): Absent Code attribute in method that is not native or abstract in class file javax/ejb/EJBException"}
,
   "WFLYCTL0412: Required services that are not installed:" => [
       "jboss.deployment.unit.\"dvd-ear.ear\".beanmanager",
       "jboss.deployment.unit.\"dvd-ear.ear\".WeldStartService"
   ],
   "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"dvd-ear.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"dvd-ear.ear\".beanmanager, jboss.deployment.unit.\"dvd-ear.ear\".WeldStartService]"]

WildFly is running under JDK 17, but the app is built with JDK 8, because of problems with the WF Client-side code and JDK >=9.  There are hints of reflection problems in the above error, but I'm more concerned with the unavailablity of the CDI stuff like Weld.

I've added a beans.xml file to src/main/resources/META-INF with bean-discovery-mode="all", to no avail.

Any ideas would be welcome, thanks

[Frank Griffin]

I think I've solved the problem.  I just found a reference saying that WF 26 dropped support for Java 8, and that's what the app was built with.  So the reflection error above is actually at the heart of it.  I'll have to rebuild and solve the client problem some other way.

[Emmanuel Hugonnet]

You may want to take a look at https://github.com/wildfly-extras/deployment-transformer-feature-pack
Not sure if it will solve your issue

> --
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/wildfly/2637f6c4-f318-4163-bd71-8797d60f3d19n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/2637f6c4-f318-4163-bd71-8797d60f3d19n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Frank Griffin]

Thanks for the reply.  Since this app has traditionally worked with vanilla WF as delivered, I'd rather get it working again with vanilla WF.

My guess about dropping support for Java 8 didn't pan out.   I rebuilt all but the client-side classes with Java 17, and still get the same error.  I'm wondering if I'm getting a wrong version of the javax.ejb stuff, possibly from a pre-java9 compile.

[James Perkins]

It's not a JDK issue. You're referencing Jakarta EE 8 API's, e.g. javax.ejb.*, in a Jakarta EE 10, e.g. jakarta.ejb.*,  server. The transformer mentioned previously is to update your deployments byte from javax based namespaces to jakarta base name spaces.

[Frank Griffin]

Ah, I had seen articles about javax -> jakarta, but I didn't realize WF was at EE10.  I'll change my sources, thanks very much.