Entity Beans deployment on weblogic8.1

[Joginder Raperia]

When I am deploying entity beans on WebLogic App Server 8.1,I am getting 'Assertion failed [Assertion violated] '
When I try to deploy the entity beans as 'ReadOnly', which has container managed relationships to other entity beans,everything works fine.When I try to deploy these beans using 'Read Mostly' pattern,I get the following error:
<BEA-149004> <Failures were detected while initiating Deploy task for application websitemanager-service.>
####<Apr 1, 2004 12:38:39 AM PST> <Debug> <Deployer> <cgiwls01> <cgiwls01-18161> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Assertion violated ]
at weblogic.utils.Debug.assertion(Debug.java:47)
at weblogic.ejb20.cmp.rdbms.RDBMSBean.processSymmetricRole(RDBMSBean.java:1639)
at weblogic.ejb20.cmp.rdbms.RDBMSBean.processRole(RDBMSBean.java:1242)
at weblogic.ejb20.cmp.rdbms.RDBMSBean.processDescriptors(RDBMSBean.java:1108)
at weblogic.ejb20.cmp.rdbms.Deployer.readTypeSpecificData(Deployer.java:441)
at weblogic.ejb20.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.java:483)
at weblogic.ejb20.persistence.PersistenceType.setupDeployer(PersistenceType.java:414)
at weblogic.ejb20.deployer.CMPInfoImpl.setup(CMPInfoImpl.java:110)
at weblogic.ejb20.ejbc.EJB20CMPCompiler.generatePersistenceSources(EJB20CMPCompiler.java:64)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:245)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:763)
at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1277)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2634)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:17
Any help on this is highly appericiated.

[Valentin Crettaz]

Moving this to the BEA Weblogic forum. Please continue this discussion there. Thank you

[Reid M. Pinchback]

I had the exact same problem.

In your application do you have multiple deployments of entity beans with CMR relationships? In other words, scenarios like:

- Java code for Bean A

- Java code for Bean B

- Deployment Descriptors have A1 (a bean based on code A), B1 (a bean based on code B), and a relationship between them

- DDs also have A2 (based on A), B2 (based on B), and a relationship between them (i.e. different EJB names, different tables, etc.)

WebLogic 8.1 can't handle that. Got that straight from BEA. Amazingly, amazingly, amazingly braindead. I can't imagine what they were thinking when they came up with that implementation.