5 Replies Latest reply on Jun 3, 2014 11:46 AM by mandrosen

8.0.0 to 8.1.0 migration class loading issue

mandrosen Jun 2, 2014 4:37 PM

I have an application that worked in wildfly-8.0.0.Final and I am trying to upgrade to 8.1.0.Final. I have tried both a fresh install and a patch update, but in both instances, I get a NoClassDefFoundError in the web application when trying to access my EJBs. The EJBs load fine, I see them in the log and I see them in the JNDI context. Is there a class loading change or a migration document that might explain this?

This is what I am seeing:

2014-06-02 15:22:00,523 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named PersonIntBean in deployment unit subdeployment "app.jar" of deployment "app.ear" are as follows:

java:global/app/app/PersonBean!com.app.ejb.person.PersonInt

java:app/app/PersonBean!com.app.ejb.person.PersonInt

java:module/PersonBean!com.app.ejb.person.PersonInt

java:global/app/app/PersonBean

java:app/app/PersonBean

java:module/PersonBean

....

Caused by: java.lang.ClassNotFoundException: com.app.ejb.PersonInt from [Module "deployment.app.ear.webapp.war:main" from Service Module Loader]

at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final]

at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final]

at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final]

at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final]

at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final]

1. Re: 8.0.0 to 8.1.0 migration class loading issue

jason.greene Jun 2, 2014 6:33 PM (in response to mandrosen)

Do you have any specialized class loading configuration?

Could you share jboss-deployment-structure.xml, application.xml, and any manifest.mf files that contain classpath, extensions, or module imports?
Actions
2. Re: Re: 8.0.0 to 8.1.0 migration class loading issue

mandrosen Jun 2, 2014 6:42 PM (in response to jason.greene)
Absolutely.

application.xml 574 bytes

jboss-deployment-structure.xml 285 bytes

webapp.MANIFEST.MF 302 bytes
Actions
3. Re: Re: Re: 8.0.0 to 8.1.0 migration class loading issue

jason.greene Jun 2, 2014 6:51 PM (in response to mandrosen)
Thanks.

Ok so the behavior change is caused by a bug in 8.0.0 that prevented sub deployment isolation from getting honored, which now works correctly in 8.1:

<ear-subdeployments-isolated>true</ear-subdeployments-isolated>

I also notice that your web app has an empty Class-Path, so these two combined lead to your war not being able to see classes in your ejb jar. So you can either add a Class-path reference in your war's META-INF/Manifest.MF to point to your ejb jar. Or you could remove that isolation flag (or set it to false).

Let me know if that works for you.

Thanks!
Actions
4. Re: Re: Re: Re: 8.0.0 to 8.1.0 migration class loading issue

jason.greene Jun 2, 2014 6:53 PM (in response to jason.greene)
BTW If you go the Class-Path route it would look like this:

Class-Path: app.jar
Actions
5. Re: 8.0.0 to 8.1.0 migration class loading issue

mandrosen Jun 3, 2014 11:46 AM (in response to mandrosen)

Thank you. I just needed the to set isolated to false. It works with and without the Class-Path set.
Actions

Go to original post