The problem is already discussed in another topic. See also the issue
EJBTHREE-352 in JIRA.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3931652#3931652
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3931652
Is someone working on this issue?
http://jira.jboss.com/jira/browse/EJBTHREE-352
The issue status seems to be 'Open'.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3914595#3914595
Reply to the post :
Ok. Will this issue be fixed in AS 4.0.3 SP2? If yes, what is the planned
release schedule? Or can I somehow install a fixed version of EJB 3.0 container
before that?
BTW, what is the easiest workaround? Changing bean's interface name causes
changes also into web tier.
View the original post
How can I run multiple instances of a stateless EJB 3.0 session bean?
The implementation may vary (different versions, EntityManagers etc).
The idea is to find out, how to implement a full range J2EE system (web tier,
ejb3 tier, db) so that each installation may have different version and use
How do I scope a deployment?
Now deployment of two stateless session beans with different JNDI names in
META-INF/jboss.xml causes the following exception:
javax.management.InstanceAlreadyExistsException:
jboss.j2ee:service=EJB3,name=my.pkg.StatelessSampleBean already registered.
Using
