• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

ejb-jndi problem

 
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In case I change the name of the jndi name to a unique name. I still get the same problem. I checked for multiple occurences, but there aren't any.
My weblogic-ejb-jar.xml file is:
<weblogic-enterprise-bean>
<ejb-name>GangsterEJB</ejb-name>
<local-jndi-name>Gangster</local-jndi-name>
</weblogic-enterprise-bean>
I do not get the problem.
Thank you
Ronak Parekh

This is the error:
Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:

Unable to bind EJB Home Interface to the JNDI name: Organization. The error was:

javax.naming.NameAlreadyBoundException: Organization is already bound; remaining
name ''
<<no stack trace available>>

Ronak Parekh
 
Ranch Hand
Posts: 401
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Something is already bound to the JNDI name "Organization" and you are trying to deploy an EJB with that name, too. It might be a jdbc pool or datasource or just about anything. Make sure you pick unique names for everything that goes in jndi.
It is often helpful to use some prefix for different types of things. For example, you might want to use something like: "jdbcPool.OrgPool" for pools, "dataSource.Organization", "ejb.Organizaiton" for remote ejb homes and "localEjb.Organization" for the local ejb homes. That makes it easier to prevent name collisions like this.
You can check what has the other name. When your server comes up, you can check jndi from the console (right-click on the server) or using weblogic.Admin LIST command:
java weblogic.Admin LIST
There are other arguments you will have to give for weblogic.Admin - like url, password, etc but just type java weblogic.Admin and it will give you a usage help.
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic