Jndi-name javax.naming.NameAlreadyBoundException:
Hi,
I am getting the following error while deploying a CMP Bean. Initially
this started to deploy, but later when I recompiled the source files
and tried to deploy again, I get the following errors.
In fact I am tired of trying to see what's actually happening.
Your immediate response is highly appreciated.
thanks and regards,
F S Joseph
Unable to deploy EJB: country from Country.jar:
weblogic.ejb20.WLDeploymentException: Unable to bind EJB Home
Interface to the JNDI name: ejb.CountryHome. The error was:
javax.naming.NameAlreadyBoundException: Failed to bind remote object
(ClusterableRemoteRef(127.0.0.1
null)/292 [cashnet.ejb.CountryHome+javax.ejb.EJBHome+weblogic.ejb.QueryHome+weblogic.ejb20.interfaces.QueryHandler+weblogic.ejb20.interfaces.RemoteHome])
to replica aware stub at CountryHome(ClusterableRemoteRef(127.0.0.1
[127.0.0.1/291])/291 [cashnet.ejb.CountryHome+javax.ejb.EJBHome+weblogic.ejb.QueryHome+weblogic.ejb20.interfaces.QueryHandler+weblogic.ejb20.interfaces.RemoteHome]);
remaining name 'ejb'
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
at weblogic.jndi.internal.ServerNamingNode_WLStub.bind(Unknown
Source)
at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:359)
at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:353)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:951)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1302)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:342)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1509)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:970)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:957)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1074)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:700)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:956)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1302)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:342)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1509)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:970)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:957)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1074)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:700)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
failed application Country on cashnetserver
there is already an ejb with this name!
this is set in weblogic-ejb-jar.xml
Ronak Parekh wrote:
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 'com.sempire.builder.business_component'
<<no stack trace available>>
Similar Messages
-
Javax.naming.NameAlreadyBoundException:
Hi
I am getting following error while
starting managed server (admin server is already running)
in a clustered environment.
"javax.naming.NameAlreadyBoundException:
AuditTopic is already bound; remaining name 'com.bea.wlpi' "
even though there is only one entry for "AuditTopic" in config.xml
I have attached config.xml with this post.
here is some portion of the server console
=================================================================
<Oct 1, 2003 7:41:26 PM IST> <Notice> <AI> <000000> <Started WebLogic Integration
- AI Ser
ver version 7.0.2.0>
javax.naming.NameAlreadyBoundException: AuditTopic is already bound; remaining
name 'com.b
ea.wlpi'
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:26
3)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:23
0)
at weblogic.jndi.internal.ServerNamingNode_WLStub.bind(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:358)
at javax.naming.InitialContext.bind(InitialContext.java:353)
at com.bea.wlpi.server.init.BPMInitBean.ejbCreate(Unknown Source)
at com.bea.wlpi.server.init.BPMInitBean_ddwui7_Impl.ejbCreate(BPMInitBean_ddwui7_I
mpl.java:122)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:1
51)
at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:188)
at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManager.java:37
5)
at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:1507)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1392)
at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:391)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:1039
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1
025)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplicat
ions(SlaveDeployer.java:617)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Deployme
ntManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:65)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:832)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
at weblogic.Server.main(Server.java:32)
weblogic.ejb20.WLDeploymentException: AuditTopic is already boundjavax.ejb.CreateException
: AuditTopic is already bound
at com.bea.wlpi.server.init.BPMInitBean.ejbCreate(Unknown Source)
at com.bea.wlpi.server.init.BPMInitBean_ddwui7_Impl.ejbCreate(BPMInitBean_ddwui7_I
mpl.java:122)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:1
51)
at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:188)
at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManager.java:37
5)
at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:1507)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1392)
at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:391)
=================================================================
Thanks in advance.
Vijay
[config.xml]In config.xml remove the <Application></Application> tag for Ejb.
Application Deployed="" Name=""
Path="">
<EJBComponent Name="" Targets="" URI=""/> </Application>
gary <[email protected]> wrote:
Hi guys, hope you can help:
I had to change the packages of some ejbs and now when I try to deploy
the new .jar file I get the error below. I have tried deleting the ejb's
off the server, rebooted the server and nothing seems to work. Any help
would be appreciated. (Weblogic version 6.1)
Thanks in advance,
Gary
Unable to deploy EJB: quizinterface from etvquiz-ejb.jar:
Unable to bind a cluster-aware stateless session EJBObject to the name:
channel4.quizinterface_EO. Please ensure that the jndi-name in the weblogic-ejb-jar.xml
is correct. The error was:
javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-aware
stub to a name that is currently bound to a replica-aware stub; remaining
name ''
<<no stack trace available>>
>
<Nov 1, 2002 1:57:46 PM GMT> <Error> <Management> <Error deploying application
.\config\mydomain\app
lications\etvquiz: java.lang.reflect.UndeclaredThrowableException> -
Javax.naming.NameAlreadyBoundException [LDAP: error code 68
I am getting the below Error when I am trying to add the entry into the LPAD Server.
javax.naming.NameAlreadyBoundException: [LDAP: error code 68 - Entry Already Exists]; remaining name 'ou=People,dc=company,dc=co,dc=in'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.c_bind(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.c_bind(Unknown Source)
at com.sun.jndi.toolkit.ctx.ComponentContext.p_bind(Unknown Source)
at com.sun.jndi.toolkit.ctx.PartialCompositeContext.bind(Unknown Source)
at com.sun.jndi.toolkit.ctx.PartialCompositeContext.bind(Unknown Source)
at javax.naming.InitialContext.bind(Unknown Source)
at com.test.CreateUser.main(CreateUser.java:54)
I am using the following sample program to test this.
public class CreateUser {
public static void main(String[] args) {
java.util.Hashtable env = new java.util.Hashtable();
env.put( javax.naming.Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory" );
env.put( javax.naming.Context.PROVIDER_URL, "ldap://c-4966:62260");
env.put( javax.naming.Context.SECURITY_AUTHENTICATION, "simple");
env.put( javax.naming.Context.SECURITY_PRINCIPAL, "cn=Directory Manager");
env.put( javax.naming.Context.SECURITY_CREDENTIALS, "test");
String dn = "ou=People,dc=company,dc=co,dc=in";
try {
// create DirContext
DirContext ctx = new InitialDirContext(env);
// Attributes for new entry
Attributes attrs = new BasicAttributes();
Attribute attr = new BasicAttribute("objectclass");
attr.add( 0, "top" );
attr.add( 1, "person" );
attr.add( 2, "organizationalPerson" );
attr.add( 3, "inetorgperson" );
attrs.put(attr);
System.out.println("1...........");
attrs.put("cn", "Sai Krishna");
attrs.put("sn", "Potluri");
attrs.put("givenName","Sia Potluri");
attrs.put("uid","saipotluri");
attrs.put("userPassword", "balaji");
/*attr = new javax.naming.directory.BasicAttribute("mail");
attr.add( 0, "[email protected]" );
attr.add( 1, "[email protected]" );
attrs.put( attr );
attrs.put( "telephonenumber", "111-1111-3333" );*/
System.out.println("2...........");
ctx.bind(dn, attrs);
} catch ( javax.naming.NamingException ex ) {
System.err.println("Fail to Add Entry\n");
ex.printStackTrace();
Any help is highly appreciated.
Thanks in Advance
DARMAYou're adding the entry "ou=people,dc=company,dc=co,dc=in" and not an entry under "ou=people,dc=company,dc=co,dc=in".
The dn of the new entry should be something like "cn=Sai Krishna,ou=people,dc=company,dc=co,dc=in" when you call ctx.bind(dn,...) -
Javax.naming.NameAlreadyBoundException: Failed to bind remote object
I am getting an error while deploying wli-ejbs.ear file. This ear uses oracle thin drivers to connect to database. But while deploying i am receiving an error as below. Can anyone please help me to solve this problem?
Deployer:149033]preparing application wli-ejbs on managed2_cvf01
[Deployer:149033]preparing application wli-ejbs on managed1_cvf01
[Deployer:149033]prepared application wli-ejbs on managed1_cvf01
[Deployer:149033]prepared application wli-ejbs on managed2_cvf01
[Deployer:149033]activating application wli-ejbs on managed1_cvf01
[Deployer:149033]activating application wli-ejbs on managed2_cvf01
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application wli-ejbs on cvf01_cluster.: weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: activate failed for calendar/oracle
Module: calendar/oracle Error: Exception activating module: EJBModule(calendar/oracle,status=PREPARED)
Unable to deploy EJB: RemoteCalendarBean from calendar/oracle:
[EJB:011008]Unable to bind EJB Home Interface to the JNDI name: RemoteCalendarBean.
javax.naming.NameAlreadyBoundException: Failed to bind remote object (ClusterableRemoteRef(704752282736664516S:172.24.206.163:[7003,7003,7004,7004,7003,7004,-1,0,0]:172.24.206.163:7003,172.24.206.163:7003:cvf01:managed1_cvf01 null)/948 [com.bea.wli.calendar.api.BusinessCalendarHome+javax.ejb.EJBHome+weblogic.ejb20.interfaces.RemoteHome]) to replica aware stub at RemoteCalendarBean(ClusterableRemoteRef(704752282736664516S:172.24.206.163:[7003,7003,7004,7004,7003,7004,-1,0,0]:172.24.206.163:7003,172.24.206.163:7003:cvf01:managed1_cvf01 [704752282736664516S:172.24.206.163:[7003,7003,7004,7004,7003,7004,-1,0,0]:172.24.206.163:7003,172.24.206.163:7003:cvf01:managed1_cvf01/944, -8505871579836432025S:172.24.206.163:[7005,7005,7006,7006,7005,7006,-1,0,0]:172.24.206.163:7003,172.24.206.163:7003:cvf01:managed2_cvf01/1008])/944 [com.bea.wli.calendar.api.BusinessCalendarHome+javax.ejb.EJBHome+weblogic.ejb20.interfaces.RemoteHome]); remaining name ''
at weblogic.rmi.cluster.ClusterableRemoteObject.onBind(ClusterableRemoteObject.java:177)
at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:347)
at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:124)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:291)
at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:279)
at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:386)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1141)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1385)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:631)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3315)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2194)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2167)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2503)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2421)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2138)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:676)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)run the sync.bat file as mentioned in the instructions...
or through EBCC(select sampleportal-project dir, app name "sampleportal")...
good luck
Vijay
"ellen" <[email protected]> wrote:
>
I installed sampleportal and did all the changes according to the documents,
when
the server started, there is this error:
Unable to deploy EJB: CatalogWebService from catalogwe.jar:
Unable to bind EJB Home Interface to the JNDI name: sampleportal.BEA_commerce.CatalogWebService.
The error was: javax.naming.nameAlreadyBoundException: Failed to bind remote
object...to
replica aware stub at CatalogWebService; remaining name'sampleportal.BEA_commerce'
After the server started with the above error, I tried to run the app, here
is what
occured:
PortalPersistenceManager: portal'sampleportal/sampleportal' not found.
Has anybody seen this before?
Ellen -
Javax.naming.NameAlreadyBoundException: localhome is already
Hi,
I'm trying to install a clustered environment. I was able to startup the ff:
1. NodeManager = port 24101
2. Admin Server = 24102
However, when i want to startup the managed servers, i'm getting an error....
The WebLogic Server did not start up properly.
Exception raised:
'weblogic.management.configuration.ConfigurationException: -
with nested exception:
[javax.naming.NameAlreadyBoundException: localhome is already bound]'
Reason: weblogic.server.ServerLifecycleException:
weblogic.management.configuration.ConfigurationException: -
with nested exception:
[javax.naming.NameAlreadyBoundException: localhome is already bound]
Where do you think is the problem?. is there something to do with my configuration of the weblogic? SOS please.You're adding the entry "ou=people,dc=company,dc=co,dc=in" and not an entry under "ou=people,dc=company,dc=co,dc=in".
The dn of the new entry should be something like "cn=Sai Krishna,ou=people,dc=company,dc=co,dc=in" when you call ctx.bind(dn,...) -
Jndi.properties - javax.naming.NoInitialContextException
hi
i'm new to netbeans (5.5) and the Sun 9 appserver. I've been using JBoss & Eclipse to date.
I'm getting the javax.naming.NoInitialContextException and I believe it's because I'm not using jndi.properties like in jboss.
The problem is that I cannot seem to find where it should go and what it should look like.
Can someone please help ?
ThanksAll the documentation you need is here:
http://docs.sun.com/app/docs/coll/1343.3
I would particularly point you to http://docs.sun.com/app/docs/doc/819-3659/6n5s6m5bn?a=view -
Could not deploy an JAR archive because JNDI name is already in use.
Hi,
I have a problem.
When the WebLogic server starts, it cannot deploy an EJB application because a
JDNI name is already in use.
What can I do to unregister this name ?
If it is possible a better description is step by step.
The WebLogic server, when starts, prints the next lines:
<18/01/2002 12:35:24 PM GMT-06:00> <Error> <J2EE> <Error deploying EJB Component
: sui_ejb
weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested exc
eption is:
javax.naming.NameAlreadyBoundException: Can't rebind anything but a repl
ica-aware stub to a name that is currently bound to a replica-aware stub; remain
ing name ''
javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-awar
e stub to a name that is currently bound to a replica-aware stub; remaining name
<<no stack trace available>>
>
<18/01/2002 12:35:24 PM GMT-06:00> <Error> <J2EE> <Error deploying application
s
ui_ejb: Could not deploy: 'sui_ejb.jar': JNDI name in use
>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer> <WebLogic Server
st
arted>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer> <ListenThread liste
ning on port 7001, ip address 157.253.174.63>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer> <SSLListenThread
li
stening on port 7002, ip address 157.253.174.63>
In advance, thanks for your help.
- Ricardo De la Rosa (Colombia)Cameron,
I resolve the problem using your clues.
The problem was that I include the ejb.jar file in the .ear file and I copy the
ejb.jar file in the applications directory and it is redundant.
It is only needed to include the ejb.jar file in the .ear file.
Best regards,
- Ricardo (Colombia)
"Cameron Purdy" <[email protected]> wrote:
In that case, check the config.xml and make sure that the app isn't being
deployed in ways that you weren't expecting ... just double-check
everything. Sometimes the console does weird things.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Ricardo De la Rosa" <[email protected]> wrote in message
news:[email protected]...
Cameron,
I think that it isn't the problem because yesterday it deploys correctly,and
today I didn't touch the compilation options.
Thank you !
If you have another idea I really appreciate it.
Best regards,
- Ricardo (Colombia)
"Cameron Purdy" <[email protected]> wrote:
Hi Ricardo,
Certain items are not replica-aware, such as JMS queues, so they must
be
deployed to a single target in the cluster. It sounds like your EJB
is
compiled with an option that turned off the replica aware stubs.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you shouldbe!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Ricardo De la Rosa" <[email protected]> wrote in message
news:[email protected]...
Hi,
I have a problem.
When the WebLogic server starts, it cannot deploy an EJB applicationbecause a
JDNI name is already in use.
What can I do to unregister this name ?
If it is possible a better description is step by step.
The WebLogic server, when starts, prints the next lines:
<18/01/2002 12:35:24 PM GMT-06:00> <Error> <J2EE> <Error deployingEJB
Component
: sui_ejb
weblogic.ejb20.EJBDeploymentException: Error deploying stateless
EJB;
nested exc
eption is:
javax.naming.NameAlreadyBoundException: Can't rebind anythingbut
a repl
ica-aware stub to a name that is currently bound to a replica-awarestub;
remain
ing name ''
javax.naming.NameAlreadyBoundException: Can't rebind anything but
a
replica-awar
e stub to a name that is currently bound to a replica-aware stub;remaining name
<<no stack trace available>>
>
<18/01/2002 12:35:24 PM GMT-06:00> <Error> <J2EE> <Error deployingapplication
s
ui_ejb: Could not deploy: 'sui_ejb.jar': JNDI name in use
>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer> <WebLogicServer
st
arted>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer>
<ListenThread
liste
ning on port 7001, ip address 157.253.174.63>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer><SSLListenThread
li
stening on port 7002, ip address 157.253.174.63>
In advance, thanks for your help.
- Ricardo De la Rosa (Colombia) -
I have received a naming conflict when starting up App Server 7.
I am using the Sun Studio Enterprise.
The abstract schema name for the entity bean is Billercenter and everywhere else that the bean is referenced is billerCenter.
I am thinking that the server is complaining about the name not matching in the application module, but it won't let me change out the name. The following error is from the server.log. Anyone know what the fix is?
[12/May/2004:16:59:13] SEVERE ( 4516): EJB5090: Exception in creating EJB container [javax.naming.NameAlreadyBoundException [Root exception is org.omg.CosNaming.NamingContextPackage.AlreadyBound: IDL:omg.org/CosNaming/NamingContext/AlreadyBound:1.0]]
[12/May/2004:16:59:13] SEVERE ( 4516): appId=billerCenter_EJBModule moduleName=billerCenter_EJBModule ejbName=billerCenter
[12/May/2004:16:59:13] SEVERE ( 4516): LDR5012: Jndi name conflict found in [billerCenter_EJBModule]. Jndi name [ejb/Billercenter] for bean [billerCenter] is already in use.
[12/May/2004:16:59:13] SEVERE ( 4516): LDR5013: Naming exception while creating EJB container:
javax.naming.NameAlreadyBoundException. Root exception is org.omg.CosNaming.NamingContextPackage.AlreadyBound: IDL:omg.org/CosNaming/NamingContext/AlreadyBound:1.0
at org.omg.CosNaming.NamingContextPackage.AlreadyBoundHelper.read(AlreadyBoundHelper.java:60)
at org.omg.CosNaming._NamingContextExtStub.bind(_NamingContextExtStub.java:222)
at com.sun.jndi.cosnaming.CNCtx.callBindOrRebind(CNCtx.java:552)
at com.sun.jndi.cosnaming.CNCtx.bind(CNCtx.java:588)
at javax.naming.InitialContext.bind(InitialContext.java:359)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:204)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:168)
at com.sun.ejb.containers.BaseContainer.initializeHome(BaseContainer.java:409)
at com.sun.ejb.containers.EntityContainer.initializeHome(EntityContainer.java:355)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:230)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:345)
at com.iplanet.ias.server.EJBModuleLoader.load(EJBModuleLoader.java:79)
at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:194)
at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:166)
at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:297)
at com.iplanet.ias.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:464)
at com.iplanet.ias.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:451)
at com.iplanet.ias.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:294)
at com.iplanet.ias.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:99)
at com.iplanet.ias.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
[12/May/2004:16:59:13] WARNING ( 4516): CORE5020: Error while loading ejb module
[12/May/2004:16:59:13] WARNING ( 4516): ADM5603:Event listener error [Error while loading EJB module [billerCenter_EJBModule]. Please refer to the server log for more details. ]12/May/2004:16:59:13] SEVERE ( 4516): LDR5012: Jndi name conflict found in [billerCenter_EJBModule]. Jndi name [ejb/Billercenter] for bean [billerCenter] is already in use.
If you look at your deployment descriptor which should be ejb-jar.xml you s hould have more than 1 jndi entries which are identical for more than 1 ejbs .. -
JMS cluster and happen JMS Queue Exception javax.naming.NameAlreadyBoundExc
Hi,
Sorry I not sure how to setup JMS cluster in WLS 10.3.2. We have two manager server in two machine. And will join into one cluster. After configure the JMS module & JMS server. We found it only can work in one server. And will faill in another server. And reply the error message as below :
Any one can help to tell me why one server success. And other is fail !
javax.naming.NameAlreadyBoundException: JMS_Queue_misdel_a is already bound; rem
aining name ''
at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:357)
at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:140)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)
at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.jav
==> config for JMS
<jms-server>
<name>JMS_Server_cim_a</name>
<target>ebowls05</target>
<persistent-store xsi:nil="true"></persistent-store>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
<expiration-scan-interval>30</expiration-scan-interval>
</jms-server>
<jms-server>
<name>JMS_Server_cim_b</name>
<target>ebowls06</target>
<persistent-store xsi:nil="true"></persistent-store>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
<expiration-scan-interval>30</expiration-scan-interval>
</jms-server>
<migratable-target>
<name>ebowls06 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do
not delete manually.</notes>
<user-preferred-server>ebowls06</user-preferred-server>
<cluster>ebouatCluster</cluster>
</migratable-target>
<migratable-target>
<name>ebowls05 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do
not delete manually.</notes>
<user-preferred-server>ebowls05</user-preferred-server>
<cluster>ebouatCluster</cluster>
</migratable-target>
<jms-system-resource>
<name>JMS_ConnFactory_cim</name>
<target>ebouatCluster</target>
<descriptor-file-name>jms/JMS_ConnFactory_cim/JMS_ConnFactory_cim-jms.xml</d
escriptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>JMS_Queue_promis</name>
<target>ebouatCluster</target>
<sub-deployment>
<name>JMS_Queue_promis@JMS_Server_cim_a</name>
<target>JMS_Server_cim_a</target>
</sub-deployment>
<sub-deployment>
<name>JMS_Queue_promis@JMS_Server_cim_b</name>
<target>JMS_Server_cim_b</target>
</sub-deployment>
<descriptor-file-name>jms/JMS_Queue_promis/JMS_Queue_promis-jms.xml</descrip
tor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>JMS_Template_cim</name>
<target>ebouatCluster</target>
<descriptor-file-name>jms/JMS_Template_cim/JMS_Template_cim-jms.xml</descrip
tor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>JMS_Queue_misdel_a</name>
<target>ebouatCluster</target>
<sub-deployment>
<name>JMS_Queue_misdel_a@JMS_Server_cim_a</name>
<target>JMS_Server_cim_a</target>
</sub-deployment>
<sub-deployment>
<name>JMS_Queue_misdel_a@JMS_Server_cim_b</name>
<target>JMS_Server_cim_b</target>
</sub-deployment>
<descriptor-file-name>jms/JMS_Queue_misdel_a/JMS_Queue_misdel_a-jms.xml</des
criptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>JMS_Queue_misdel_b</name>
<target>ebouatCluster</target>
<sub-deployment>
<name>JMS_Queue_misdel_b@JMS_Server_cim_a</name>
<target>JMS_Server_cim_a</target>
</sub-deployment>
<sub-deployment>
<name>JMS_Queue_misdel_b@JMS_Server_cim_b</name>
<target>JMS_Server_cim_b</target>
</sub-deployment>
<descriptor-file-name>jms/JMS_Queue_misdel_b/JMS_Queue_misdel_b-jms.xml</des
criptor-file-name>
</jms-system-resource>1 - JMS clustering is an advanced concept, and, in most cases, uses "distributed queues". In case you haven't already, I highly recommend reading the JMS chapter of the new book "Professional Oracle WebLogic" as well as the related chapters in the JMS Programmer's Guide in the edocs.
2 - The basic problem below is that you have two different queues that have matching JNDI names, but are in the same cluster.
3 - The config snippet supplied below does not include the queue configuration. Queue configuration is embedded within the referenced module files.
4 - Please ensure that you follow configuration best practices, as per: http://download.oracle.com/docs/cd/E15523_01/web.1111/e13738/best_practice.htm#CACJCGHG -
In JBuilder7,the default JNDI Name of a entity bean(Authors) is
AuthorsRemote (in the webogic-ejb-jar.xml). I configed a Tx DATA source
configuration using this JNDI name.When I deployed the entity bean , the
WLS7.0 reported errors like this:
unable to deploy EJB: Authors from mymod2.jar:
weblogic.ejb20.WLDeploymentException: Unable to bind EJB Home Interface to
the JNDI name: AuthorsRemote. The error was:
javax.naming.NameAlreadyBoundException: AuthorsRemote is already bound;
remaining name ''
If I configed the Tx Data Source with a different JNDI name MyJNDI3 and
deloyed ,I got errors like this:
javax.naming.NameNotFoundException: Unable to resolve 'AuthorsRemote'
Resolved: '' Unresolved:'AuthorsRemote' ; remaining name 'AuthorsRemote'
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
java:109)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:262)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:229)-- Failed initializing bean access.Hi,
If say, the EJB deploys without error with the jndi name 'AuthorsRemote'
what do you expect when doing a ctx.lookup("AuthorsRemote")
A ejb instance or a datasource instance??
I think the above would validate the error that is thrown.
Vimala
paul wrote:
In JBuilder7,the default JNDI Name of a entity bean(Authors) is
AuthorsRemote (in the webogic-ejb-jar.xml). I configed a Tx DATA source
configuration using this JNDI name.When I deployed the entity bean , the
WLS7.0 reported errors like this:
unable to deploy EJB: Authors from mymod2.jar:
weblogic.ejb20.WLDeploymentException: Unable to bind EJB Home Interface to
the JNDI name: AuthorsRemote. The error was:
javax.naming.NameAlreadyBoundException: AuthorsRemote is already bound;
remaining name ''
If I configed the Tx Data Source with a different JNDI name MyJNDI3 and
deloyed ,I got errors like this:
javax.naming.NameNotFoundException: Unable to resolve 'AuthorsRemote'
Resolved: '' Unresolved:'AuthorsRemote' ; remaining name 'AuthorsRemote'
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
java:109)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:262)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:229)-- Failed initializing bean access. -
Help! NameAlreadyBound Exception, JNDI name conflict
Hi, I am using EJB 3.0 and I really have no idea on using JNDI. I read several queries and answers on this problem but I dont know how to solve it. When i go to ejb-jar.xml, I see very little information. Please help! Urgently needed. Any ideas will do, thanks!
EJB5090: Exception in creating EJB container [javax.naming.NameAlreadyBoundException: Use rebind to override]
appId=ESCM moduleName=ESCM-ejb_jar ejbName=SystemfunctionBean
LDR5012: Jndi name conflict found in [ESCM]. Jndi name [AHL.SystemfunctionRemote] for bean [SystemfunctionBean] is already in use.
LDR5013: Naming exception while creating EJB container:
javax.naming.NameAlreadyBoundException: Use rebind to override
at com.sun.enterprise.naming.TransientContext.doBindOrRebind(TransientContext.java:279)
at com.sun.enterprise.naming.TransientContext.bind(TransientContext.java:219)
at com.sun.enterprise.naming.SerialContextProviderImpl.bind(SerialContextProviderImpl.java:98)
at com.sun.enterprise.naming.LocalSerialContextProviderImpl.bind(LocalSerialContextProviderImpl.java:77)
at com.sun.enterprise.naming.SerialContext.bind(SerialContext.java:372)
at com.sun.enterprise.naming.SerialContext.bind(SerialContext.java:387)
at javax.naming.InitialContext.bind(InitialContext.java:363)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:215)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:168)
at com.sun.ejb.containers.BaseContainer.initializeHome(BaseContainer.java:948)
at com.sun.ejb.containers.StatelessSessionContainer.initializeHome(StatelessSessionContainer.java:220)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:671)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:490)
at com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:184)
at com.sun.enterprise.server.TomcatApplicationLoader.load(TomcatApplicationLoader.java:113)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:322)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:216)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:189)
at com.sun.enterprise.server.ApplicationManager.applicationEnabled(ApplicationManager.java:754)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:914)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:892)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:445)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:160)
at com.sun.enterprise.admin.server.core.AdminNotificationHelper.sendNotification(AdminNotificationHelper.java:128)
at com.sun.enterprise.admin.server.core.ConfigInterceptor.postInvoke(ConfigInterceptor.java:109)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:97)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:297)
at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:56)
at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:142)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:109)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:216)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
CORE5021: Application NOT loaded: [ESCM]12/May/2004:16:59:13] SEVERE ( 4516): LDR5012: Jndi name conflict found in [billerCenter_EJBModule]. Jndi name [ejb/Billercenter] for bean [billerCenter] is already in use.
If you look at your deployment descriptor which should be ejb-jar.xml you s hould have more than 1 jndi entries which are identical for more than 1 ejbs .. -
Conflicts binding EJB to JNDI names
Hi everyone, I'm having a problem to run an application client due to JNDI errors during the binding of EJB modules.
I'm using NetBeans 5.5 and Sun Java Application Server 9 PE.
the server log shows these messages:
SEVERE| Exception in creating EJB container [javax.naming.NameAlreadyBoundException: Use rebind to override]
SEVERE| appId=+CorpTour+ moduleName=+Tour+_jar ejbName=+reservationBean+
SEVERE| Jndi name conflict found in [+CorpTour+]. Jndi name [+reservationRemote+] for bean [+reservationBean+] is already in use.
SEVERE| Naming exception while creating EJB container: javax.naming.NameAlreadyBoundException: Use rebind to override
here the components are:
Enterprise application: CorpTour
EJB: Tour
Session Bean: reservationBean
Session Bean remote interface: reservationRemote
I created all the EJB calls using the IDE assitant so I don't know what's wrong.
Another thing is that the IDE created the application-client.xml file but not the ejb-jar file.
I would reeeeally appreciate any help on this problem. Thanks in advanceWhat version of WLS are you using?
Bart Jenkins, Globeflow SA
"Rafal Mantiuk" <[email protected]> wrote in message
news:[email protected]..
Can I do a thing like this:
-) I deploy an EJB on a server A.
-) I bind the EJB that is deployed on the server A to jndi on a server
B. The EJB is not deployed on server B.
-) Web client that runs on server B can lookup the EJB in its local
jndi. However all calls go to the server A.
Server A and B are not in the cluster.
Rafal -
Unable to bind EJB Home Interface to the JNDI name
Why do I get this error?? What is the jndi-name in weblogic-ejb-jar.xml
Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:
Unable to bind EJB Home Interface to the JNDI name:
com.sempire.builder.business
_component.Organization. The error was:
javax.naming.NameAlreadyBoundException: Organization is already bound;
remaining
name 'com.sempire.builder.business_component'
<<no stack trace available>>Slava,
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 web.xml file is:
<ejb-local-ref>
<description>
Reference EJB resources in Weblogic Resources
</description>
<ejb-ref-name>GangsterEJB</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>com.sempire.builder.business_component.GangsterHome</local-home>
<local>com.sempire.builder.business_component.Gangster</local>
</ejb-local-ref>
My weblogic-ejb-jar.xml file is:
<weblogic-enterprise-bean>
<ejb-name>GangsterEJB</ejb-name>
<entity-descriptor>
<persistence>
<persistence-type>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-type>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
</persistence-use>
</persistence>
</entity-descriptor>
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/GangsterDB</res-ref-name>
<jndi-name>oraclePool</jndi-name>
</resource-description>
</reference-descriptor>
<local-jndi-name>Gangster_test</local-jndi-name>
</weblogic-enterprise-bean>
I do not get the problem.
Thank you
Ronak Parekh
"Slava Imeshev" <[email protected]> wrote:
Hi Ronak,
This exception means that you already have a bean
with the same JNDI name. Search your weblogic-ejb-jar.xml files
for multiple occurrences of the name and fix the problem.
Regards,
Slava Imeshev
"Ronak Parekh" <[email protected]> wrote in message
news:[email protected]...
Why do I get this error?? What is the jndi-name in weblogic-ejb-jar.xml
Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:
Unable to bind EJB Home Interface to the JNDI name:
com.sempire.builder.business
_component.Organization. The error was:
javax.naming.NameAlreadyBoundException: Organization is already bound;
remaining
name 'com.sempire.builder.business_component'
<<no stack trace available>> -
Javax.naming.directory.InvalidAttributeValueException: [LDAP: error code 21
I have collected the following code from "http://www.concentric.net/~adhawan/tutorial/"
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.naming.NameAlreadyBoundException;
import javax.naming.directory.*;
import java.util.*;
public class MakeRoot {
final static String ldapServerName = "localhost";
final static String rootdn = "cn=Manager, o=jndiTest";
final static String rootpass = "secret";
final static String rootContext = "o=jndiTest";
public static void main( String[] args ) {
// set up environment to access the server
Properties env = new Properties();
env.put( Context.INITIAL_CONTEXT_FACTORY,
"com.sun.jndi.ldap.LdapCtxFactory" );
env.put( Context.PROVIDER_URL, "ldap://" + ldapServerName + "/" );
env.put( Context.SECURITY_PRINCIPAL, rootdn );
env.put( Context.SECURITY_CREDENTIALS, rootpass );
try {
// obtain initial directory context using the environment
DirContext ctx = new InitialDirContext( env );
// now, create the root context, which is just a subcontext
// of this initial directory context.
ctx.createSubcontext( rootContext );
} catch ( NameAlreadyBoundException nabe ) {
System.err.println( rootContext + " has already been bound!" );
} catch ( Exception e ) {
System.err.println( e );
}I am using the ldap server at here:
http://download.bergmans.us/openldap/openldap-2.2.29/openldap-2.2.29-db-4.3.29-openssl-0.9.8a-win32_Setup.exe
My slap.conf is:database bdb
suffix "dc=jndiTest"
rootdn "cn=Manager,dc=jndiTest"
# Cleartext passwords, especially for the rootdn, should
# be avoid. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
rootpw secret
# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory ./data
# Indices to maintain
index objectClass eqWhile running this code:
ldap://localhost:389/
javax.naming.directory.InvalidAttributeValueException: [LDAP: error code 21 - ob
jectClass: value #0 invalid per syntax]; remaining name 'dc=jndiTest'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(Unknown Source)
at com.sun.jndi.toolkit.ctx.ComponentContext.p_createSubcontext(Unknown
Source)
at com.sun.jndi.toolkit.ctx.PartialCompositeContext.createSubcontext(Unk
nown Source)
at com.sun.jndi.toolkit.ctx.PartialCompositeContext.createSubcontext(Unk
nown Source)
at javax.naming.InitialContext.createSubcontext(Unknown Source)
at MakeRoot.main(MakeRoot.java:35)It's obviously connecting with the given credentials and provider url. But then why is it not working?
Any help would highly appreciated. Thanks in advance.That is right I agree. And I guess that happened because I was trying to doing different permutation-combination with the naming scheme and I forgot to update slapd.conf. And even after made that change it was showing the same error. The poster forgot to mention to include java.schema. That change made it work finally.
Thanks for your reply. -
Javax.naming.NameNotFoundException while Message driven bean
I am adding a message driven bean in to my EJB application and trying
to deploy it in the WebLogic 6.0 server.
Now please let me know is there any other step i am missing.
1) This is what i have added in my ejb-jar.xml
<enterprise-beans>
<message-driven>
<description>no description</description>
<display-name>ActivatorBean</display-name>
<ejb-name>ActivatorBean</ejb-name>
<ejb-class>com.savvion.bizlogic.server.ActivatorBean</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<jms-destination-type>javax.jms.Queue</jms-destination-type>
</message-driven-destination>
<security-identity>
<description/>
<run-as-specified-identity>
<description/>
<role-name/>
</run-as-specified-identity>
</security-identity>
</message-driven>
2) I am adding this is in the weblogic-ejb.xml
<weblogic-enterprise-bean>
<ejb-name>ActivatorBean</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>MyMessageQueueFactory</destination-jndi-name>
</message-driven-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>1200</trans-timeout-seconds>
</transaction-descriptor>
<jndi-name>MessageQueue</jndi-name>
</weblogic-enterprise-bean>
anything else which needs to added in WebLogic-ejb.xml or in config.xml
because as per the following error message there should be some
entry in config.xml.
onemore thing i am little bit confused in
<destination-jndi-name>MyMessageQueueFactory</destination-jndi-name>
and
<jndi-name>MessageQueue</jndi-name>
and when i deploed this in WebLogic got this error message on the
prompt
<Error> <J2EE> <Error deploying EJB Component : LEngine
weblogic.ejb20.EJBDeploymentException: Error deploying Message-Driven
Bean,
couldn't find Queue 'MyMessageQueueFactory'. Make sure it was declared
in your config.xml.
; nested exception is:
javax.naming.NameNotFoundException: Unable to resolve MyMessageQueueFactory.
Resolved: '' Unresolved:'MyMessageQueueFactory' ; remaining name
javax.naming.NameNotFoundException: Unable to resolve MyMessageQueueFactory.
Reso
lved: '' Unresolved:'MyMessageQueueFactory' ; remaining name ''
<<no stack trace available>>
>
<Error> <J2EE> <Error deploying application
WFEngine: Could not deploy: 'xyz.jar'
Possible reasons include:
1. The bean or an interface class has been modified but
the deployment descriptor has not been updated
2. The database mappings in the deployment descriptor do not
match the database definition
3. The jar file is not a valid jar file
4. The jar file does not contain a valid bean>
Thanks
NareshI am adding a message driven bean in to my EJB application and trying
to deploy it in the WebLogic 6.0 server.
Now please let me know is there any other step i am missing.
1) This is what i have added in my ejb-jar.xml
<enterprise-beans>
<message-driven>
<description>no description</description>
<display-name>ActivatorBean</display-name>
<ejb-name>ActivatorBean</ejb-name>
<ejb-class>com.savvion.bizlogic.server.ActivatorBean</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<jms-destination-type>javax.jms.Queue</jms-destination-type>
</message-driven-destination>
<security-identity>
<description/>
<run-as-specified-identity>
<description/>
<role-name/>
</run-as-specified-identity>
</security-identity>
</message-driven>
2) I am adding this is in the weblogic-ejb.xml
<weblogic-enterprise-bean>
<ejb-name>ActivatorBean</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>MyMessageQueueFactory</destination-jndi-name>
</message-driven-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>1200</trans-timeout-seconds>
</transaction-descriptor>
<jndi-name>MessageQueue</jndi-name>
</weblogic-enterprise-bean>
anything else which needs to added in WebLogic-ejb.xml or in config.xml
because as per the following error message there should be some
entry in config.xml.
onemore thing i am little bit confused in
<destination-jndi-name>MyMessageQueueFactory</destination-jndi-name>
and
<jndi-name>MessageQueue</jndi-name>
and when i deploed this in WebLogic got this error message on the
prompt
<Error> <J2EE> <Error deploying EJB Component : LEngine
weblogic.ejb20.EJBDeploymentException: Error deploying Message-Driven
Bean,
couldn't find Queue 'MyMessageQueueFactory'. Make sure it was declared
in your config.xml.
; nested exception is:
javax.naming.NameNotFoundException: Unable to resolve MyMessageQueueFactory.
Resolved: '' Unresolved:'MyMessageQueueFactory' ; remaining name
javax.naming.NameNotFoundException: Unable to resolve MyMessageQueueFactory.
Reso
lved: '' Unresolved:'MyMessageQueueFactory' ; remaining name ''
<<no stack trace available>>
>
<Error> <J2EE> <Error deploying application
WFEngine: Could not deploy: 'xyz.jar'
Possible reasons include:
1. The bean or an interface class has been modified but
the deployment descriptor has not been updated
2. The database mappings in the deployment descriptor do not
match the database definition
3. The jar file is not a valid jar file
4. The jar file does not contain a valid bean>
Thanks
Naresh
Maybe you are looking for
-
How to remove old iPhone from iTunes account?
Last I was on itunes it told me I had 4 out of 5 authorized devices on my account, how do I remove old devices?
-
Refreshing drop down list in a web template based on a query view
Refreshing drop down list in a web template based on a query view I have just developed my first set of portal pages displaying the results of Bex queries and query views in the SAP Netweaver portal. I developed the pages using web application desi
-
How to backup only users' relevant files from File History on Windows 8.1?
Hi, I would like to find out how to backup certain user's files from File History on Windows 8.1? I'm planning to store the backup files on our server, over a shared network, so that client can retrieve them whenever they need. I manage to do one by
-
Pass value to a field dynamically..
Hi Experts, Can any one solve this issue?. I want to pass value to different fields dynamically.. Egu2026 I have work are having fields lwa_table-var1, lwa_table-var2, lwa_table-var3, lwa_table-var4, u2026.. up to lwa_table-var100. My logic is I have
-
Using HP 6500 all in one and cannot print on Versacheck forms
HP 6500 All in One will not print on Versacheck forms from Microsoft Money.