class not found when deploying two ejb-jars in the same application

[Jon Tirsén‏]

I encounter an error in Weblogic Server 6.1 SP2.
I am trying to deploy an application with the following modules, one war,
one ejb-jar containing services (stateless session-beans) and one ejb-jar
containing the domain (entity beans with cmp). The war uses classes from the
two others and the services ejbs uses classes from the domain. All jars are
also using classes which I have put on the java system classpath.
Also I have added a MANIFEST.MF "Class-Path:"-entry indicating that the
services-jar uses the domain-jar.
I get an error indicating that a class used by the services ejb-jar and
contained within the domain ejb-jar can not be found.

This is the complete error:
<2001-aug-27 17:10:38 CEST> <Error> <J2EE> <Error deploying application
trader_s
ervices:

Unable to deploy EJB:
C:\Development\bea\wlserver6.1\.\config\mydomain\applicati
ons\.wlnotdelete\wlap14170\trader_services.jar from trader_services.jar:

java.lang.NoClassDefFoundError:
com/emm/trader/buyer/domain/key/DeliveryAddressP
K
at java.lang.Class.getMethods0(Native Method)
at java.lang.Class.getMethods(Class.java:742)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.initializeMethodInfo
s(ClientDrivenBeanInfoImpl.java:928)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.<init>(ClientDrivenB
eanInfoImpl.java:210)
at
weblogic.ejb20.deployer.SessionBeanInfoImpl.<init>(SessionBeanInfoImp
l.java:103)
at
weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.
java:320)
at
weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M
BeanDeploymentInfoImpl.java:440)
at
weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymen
tInfoImpl.java:126)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:858)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:160)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:606)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:590)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:350)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy29.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2706)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:360)
at
weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:152)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:606)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:590)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:350)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy38.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub
.start(ApplicationManagerMBean_CachingStub.java:479)
at
weblogic.management.Admin.startApplicationManager(Admin.java:1138)
at weblogic.management.Admin.finish(Admin.java:561)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)

>

[Pen Friend‏]

Jon,

Could you please confirm whether you are using WLS 6.0 SP2 or WLS 6.1 SP2,
because there is no SP for WLS 6.1 as of yet.

[Jon Tirsén‏]

Hmm... Sorry. 6.1 no SP that is.

"Pen Friend" <frie...@hotmail.com> wrote in message
news:3B8A65A4...@hotmail.com...

[Dimitri Rakitine‏]

Interesting. You can try to specify deployment order, so your entity beans
are deployed before session beans:
http://e-docs.bea.com/wls/docs61/adminguide/appman.html#1030797
Or you can try to use weblogic.ejb20.utils.MergeJars to merge ejb-jars
into one.

>>

--
Dimitri

[Jon Tirsén‏]

Hmm, yes, it seems to work when I set a lower deployment order value for the
domain-jar (ie. a _higher_ for the dependent jar).

Is there any way to do this in the weblogic-ejb-jar.xml or like
weblogic-application.xml or something like that. Ie. I don't want to need to
open the console for this.

"Dimitri Rakitine" <d...@dima.dhs.org> wrote in message
news:3b8a...@newsgroups.bea.com...

[Dimitri Rakitine‏]

Jon Tirsén" <jon.t...@emm.com> wrote:
> Hmm, yes, it seems to work when I set a lower deployment order value for the
> domain-jar (ie. a _higher_ for the dependent jar).

> Is there any way to do this in the weblogic-ejb-jar.xml or like
> weblogic-application.xml or something like that. Ie. I don't want to need to
> open the console for this.

No, I don't think so.

On the other hand, I think that WebLogic should fully construct EJB classloader
before deploying ejb-jars. Currently it looks like it adds jars to the classloader
as it deploys them.

--
Dimitri