3 Replies Latest reply on Apr 4, 2011 3:15 AM by jaikiran

PreDestroyImpl

rajivtmathew Mar 30, 2011 2:12 PM

JBoss 6.0.0 AS Final

Default deployment profile

Apart from the JBoss 6, I've also upgraded hibernate search libraries, so they arent the ones that come with the JBoss 6 download.

I get a NoClassDefFoundException for this class PreDestroyImpl.

A cursory examination of the jboss/common/lib folder reveals that this class is defined in 2 jars, namely:

jboss-ejb3-ext-api-impl.jar (org.jboss.ejb3.annotation.impl)

AND

jboss-ejb3-interceptors (org.jboss.ejb3.interceptors.annotation.impl)

I'm wondering if this is due to a conflict between these 2 classes, or whether it has something to do with my classpath.

My deployment structure looks like:

jboss/server/default/deploy/[DEPLOYMENT.ear]

I've attached the relevant portion of the deployment server log file. Any help would be much appreciated.

1. NoClassDefFoundError: org/jboss/ejb3/interceptors/annotation/impl/PreDestroyImpl

jaikiran Mar 31, 2011 2:55 AM (in response to rajivtmathew)

The root cause appears to be a StackOverFlowError:

13:50:25,330 WARN [ClassLoaderManager] Unexpected error during load of:org.jboss.ejb3.interceptors.annotation.impl.PreDestroyImpl: java.lang.StackOverflowError
It appears to be triggered from your application call to getHibernate() method. What does your bean code look like?
Actions
2. Re: NoClassDefFoundError: org/jboss/ejb3/interceptors/annotation/impl/PreDestroyImpl

rajivtmathew Mar 31, 2011 8:37 PM (in response to jaikiran)

Hi Jaikiran,

Are you asking about the deployment structure of my EAR?
I don't notice anywhere in my application code where I'm making a direct call to getHibernate(). I did notice an invocation of callHibernate() from my bean, and assume thats what you meant. I'm investigating currently with a breakpoint at that method call. Hope to have more information soon.

Thanks.
Actions
3. Re: NoClassDefFoundError: org/jboss/ejb3/interceptors/annotation/impl/PreDestroyImpl

jaikiran Apr 4, 2011 3:15 AM (in response to rajivtmathew)

rajivtmathew wrote:

I did notice an invocation of callHibernate() from my bean, and assume thats what you meant.
Yes, that's the one I was referring to. That's part of the call trace and appears to be triggering a recursive call ending up with StackOverFlowError.
Actions