EJBException: Conflict between default jndi name Example for both remote and local for ejb-name:Example in JBoss EAP 5.x

Solution Unverified - Updated -

Issue

  • While deploying the EJB application the following exception is seen
Caused by: javax.ejb.EJBException: Conflict between default jndi name Example for both remote and local for ejb-name:Example, bean class=class com.jboss.examples.ejb.ExampleBean
Local JNDI Name: Example/local
Remote JNDI Name: Example
                at org.jboss.ejb3.proxy.factory.ProxyFactoryHelper.checkForJndiNamingConflict(ProxyFactoryHelper.java:916)
                at org.jboss.ejb3.proxy.factory.ProxyFactoryHelper.getLocalJndiName(ProxyFactoryHelper.java:880)
                at org.jboss.ejb3.proxy.factory.ProxyFactoryHelper.getLocalJndiName(ProxyFactoryHelper.java:863)
                at org.jboss.ejb3.session.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:120)
                at org.jboss.ejb3.session.SessionContainer.instantiated(SessionContainer.java:193)
                at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:728)
                ... 39 more

What is the reason behind this issue and how to fix it?

Environment

  • Red Hat JBoss SOA Platform (SOA-P)
    • 5.x
  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 5.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.