1 Reply Latest reply on Jan 24, 2017 8:55 AM by andey

weld.weldClassIntrospector is missing

lamikam2 Jan 23, 2017 3:09 PM

I am migrating a WLS app to EAP 7.0. I have looked at the quick-starts, other similar posts, but still cannot resolve. I am deploying an EAR file with several support jars, and an EJB project.

I am getting several errors, including ones like this:

"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"HansenIntegtationFramework.ear\".\"HansenIntegrationFramework-ejb-1.0.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"HansenIntegtationFramework.ear\".\"HansenIntegrationFramework-ejb-1.0.jar\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment \"HansenIntegrationFramework-ejb-1.0.jar\" of deployment \"HansenIntegtationFramework.ear\"

Caused by: java.lang.NoClassDefFoundError: Failed to link com/hsntech/hif/eao/impl/AuthorizationCacheImpl (Module \"deployment.HansenIntegtationFramework.ear.HansenIntegrationFramework-ejb-1.0.jar:main\" from Service Module Loader): com/hsntech/hif/utils/Observer"},

"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"HansenIntegtationFramework.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"HansenIntegtationFramework.ear\".beanmanager]"]

2017-01-23 14:36:36,023 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 73) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "HansenIntegtationFramework.ear")]) - failure description: {

I know the referenced classes (com/hsntech/hif/utils/Observer) are in a jar that is in the EAR file

1. Re: weld.weldClassIntrospector is missing

andey Jan 24, 2017 8:55 AM (in response to lamikam2)

NoClassDefFoundError is thrown when the JVM tries to load a definition of a class and no definition can be found. NoClassDefFoundError is caused by typically a ClassNotFoundException or a ExceptionInInitializerError. After the initial ClassNotFoundException / ExceptionInInitializerError, the JVM will just throw a NoClassDefFoundError and will not show the original cause.

The NoClassDefFoundError occurs after a ClassNotFoundException. The ClassNotFoundException will occur the first time the class is referenced and the classloader tries to load it. The next time the class is referenced, the classloader has cached that is is not found and will throw a NoClassDefFoundError

Typically there should be a ClassNotFoundException that preceeds NoClassDefFoundError

Its seems jar mismatch issue in different JBoss EAP version

You need to refer migration guide at[1] which describes step by step process :
[1]Migration Guide - Red Hat Customer Portal
Actions