3.0.7 startup java.lang.ClassNotFoundException

[hschmid]

Hi,
after upgrading from 3.0.6 to 3.0.7 I get the following java.lang.ClassNotFoundException on startup:

16:34:29,555 INFO [EjbModule] Deploying LiabilityBean
16:34:29,617 WARN [EjbModule] Could not load the org.jboss.resource.connectionm
anager.CachedConnectionInterceptor interceptor for this container
java.lang.ClassNotFoundException: org.jboss.resource.connectionmanager.CachedCon
nectionInterceptor
at java.net.URLClassLoader$1.run(URLClassLoader.java:198)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at org.jboss.ejb.EjbModule.addInterceptors(EjbModule.java:814)
at org.jboss.ejb.EjbModule.initializeContainer(EjbModule.java:749)
at org.jboss.ejb.EjbModule.createStatelessSessionContainer(EjbModule.jav
a:557)
at org.jboss.ejb.EjbModule.createContainer(EjbModule.java:512)
at org.jboss.ejb.EjbModule.createService(EjbModule.java:335)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:
136)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)

and so on.

I have a ejb-jar file with two statefull session beans inside.

I see the class beeing referenced in standardjboss.xml, but are not able to locate it in any jar file in the distribution.

Can anybody help please?
It worked fine with 3.0.4, 3.0.5 and 3.0.6

Thanks,
Hans

[frito]

Hi,

did you copy your deployment descriptors or configuration xml files from your older project? Some things may have changed ;-)

Compare your files with these that came with the new version. Are they valid against the dtd? Or post a snippet of your deployment descriptors.

Greetings,
Frito

[hschmid]

Thanks for responding,

yes I did copy them as I did from 3.0.4 to 3.0.5 and 3.0.6 and
yes, I compared them against the files from default folder.

Will check them again against the new dtd's though.

I read in an other forum, that there are problems with the stateful container and this class so I reverted back to 3.0.6.


Here my deployment Descriptor ejb-jar.xml

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">

<ejb-jar>
<enterprise-beans>

<ejb-name>LiabilityBean</ejb-name>
de.einsurance.ejb.liability.LiabilityHome
de.einsurance.ejb.liability.Liability
<ejb-class>de.einsurance.ejb.liability.LiabilityBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>


<ejb-name>LegalBean</ejb-name>
de.einsurance.ejb.legal.LegalHome
de.einsurance.ejb.legal.Legal
<ejb-class>de.einsurance.ejb.legal.LegalBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>

</enterprise-beans>

<assembly-descriptor>
<container-transaction>

<ejb-name>LiabilityBean</ejb-name>
<method-name>*</method-name>

<trans-attribute>Supports</trans-attribute>
</container-transaction>
<container-transaction>

<ejb-name>LegalBean</ejb-name>
<method-name>*</method-name>

<trans-attribute>Supports</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

and the jboss.xml:
<?xml version="1.0" encoding="UTF-8"?>


<enterprise-beans>

<ejb-name>LiabilityBean</ejb-name>
<jndi-name>ejb/liability/Liability</jndi-name>


<ejb-name>LegalBean</ejb-name>
<jndi-name>ejb/legal/Legal</jndi-name>

</enterprise-beans>

[frito]

The container configuration for your beans might be more interesting...

Greetings,
Frito