0000081: Multiple EJB entries with the same <env-entry> name don't deploy

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0000081

[Resin]

minor

always

04-04-05 00:00

05-11-05 00:00

Reporter

user62

View Status

public

Assigned To

Priority

urgent

Resolution

fixed

Status

closed

Product Version

3.0.12

Summary

0000081: Multiple EJB entries with the same <env-entry> name don't deploy

Description

RSN-72
If I have multiple EJBs (specifically MDBs) defined and each of them has a <env-entry> with the same name, Resin fails to deploy with the following exception:

[22:36:11.546] `java:comp/env/ejb/BeanFactoryPath' is a conflicting JNDI resourc
e for `'
com.caucho.config.ConfigException: No destination is configured.
        at com.caucho.ejb.message.MessageServer.start(MessageServer.java:122)
        at com.caucho.ejb.EjbServerManager.start(EjbServerManager.java:609)
        at com.caucho.ejb.EjbServerManager.init(EjbServerManager.java:568)
        at com.caucho.ejb.EjbServerManager.initEJBs(EjbServerManager.java:557)
        at com.caucho.server.e_app.EnterpriseApplication.configureEJB(EnterpriseApplication.java:525)
        at com.caucho.server.e_app.EnterpriseApplication.init(EnterpriseApplication.java:355)
        at com.caucho.server.e_app.EarEntry.configureInstance(EarEntry.java:273)
        at com.caucho.server.e_app.EarEntry.configureInstance(EarEntry.java:74)
        at com.caucho.server.deploy.Entry.startImpl(Entry.java:496)
        at com.caucho.server.deploy.Entry.redeployIfModifiedImpl(Entry.java:452)
        at com.caucho.server.deploy.Entry.startAutomatic(Entry.java:385)
        at com.caucho.server.deploy.DeployContainer.start(DeployContainer.java:154)
        at com.caucho.server.webapp.ApplicationContainer.start(ApplicationContainer.java:617)
        at com.caucho.server.host.Host.start(Host.java:492)
        at com.caucho.server.deploy.Entry.startImpl(Entry.java:498)
        at com.caucho.server.deploy.Entry.redeployIfModifiedImpl(Entry.java:452)
        at com.caucho.server.deploy.Entry.startAutomatic(Entry.java:385)
        at com.caucho.server.deploy.DeployContainer.start(DeployContainer.java:154)
        at com.caucho.server.host.HostContainer.start(HostContainer.java:507)
        at com.caucho.server.resin.ServletServer.start(ServletServer.java:894)
        at com.caucho.server.resin.ResinServer.start(ResinServer.java:466)
        at com.caucho.server.resin.Resin.init(Resin.java:297)
        at com.caucho.server.resin.Resin.main(Resin.java:553)

This seems to go against the use of this option on MDBs. In this particular case I am using the AbstractJmsMessageDrivenBean from Spring that expects to find the env entry "ejb/BeanFactoryPath" to find out the name of the context configuration files. Each bean could define its own configuration file.

I think this was fixed at one time but appears to be a regression in 3.0.12.

Additional Information

Windows and OS X with both Java 1.4 and 5.0

Attached Files

Relationships

Notes
(0000087) ferg 04-04-05 00:00	ejb/090b

Issue History
Date Modified	Username	Field	Change
04-04-05 00:00	user62	New Issue
11-30-05 00:00	administrator	Fixed in Version	=> 3.0.13

Mantis 1.0.0rc3[^]

33 total queries executed.
27 unique queries executed.