logo
down
shadow

NameNotFoundException when calling a EJB in Weblogic 10.3


NameNotFoundException when calling a EJB in Weblogic 10.3

By : Jericho
Date : January 10 2021, 01:47 PM
I think the issue was by ths following , Your EJB gets bound under the following JNDI name (when deployed as EJB module):
code :


Share : facebook icon twitter icon
NameNotFoundException when calling a EJB in Weblogic 10.3

NameNotFoundException when calling a EJB in Weblogic 10.3


By : Valencia Jackson
Date : March 29 2020, 07:55 AM
hope this fix your issue To lookup a Remote Interface of a Session Bean with multiple Remote Business interfaces (e.g.com.acme.FooBusiness1, com.acme.FooBusiness2), you need to lookup a name derived from the combination of the target ejb's global JNDI name (the mappedName() in @Stateless) and the specific Remote Business Interface, separated by a "#":
code :
InitialContext ic = new InitialContext();
FooBusiness1 bean1 = (FooBusiness1) ic.lookup("FooEJB#com.acme.FooBusiness1");
FooBusiness2 bean2 = (FooBusiness2) ic.lookup("FooEJB#com.acme.FooBusiness2");
FooBusiness bean = (FooBusiness) ic.lookup("FooEJB");
InitialContext ic = new InitialContext();
(HelloWorld) ic.lookup("HelloWorld#com.foo.HelloWorld");
(HelloWorld) ic.lookup("HelloWorld");
Weblogic javax.naming.NameNotFoundException while running application

Weblogic javax.naming.NameNotFoundException while running application


By : jsp
Date : March 29 2020, 07:55 AM
To fix this issue when looking up the DS the full JNDI structure maps to java:jdbc/appsmsDS.
Please use it for lookup.
Deploying to Weblogic with javax.naming.NameNotFoundException

Deploying to Weblogic with javax.naming.NameNotFoundException


By : christok
Date : March 29 2020, 07:55 AM
it helps some times I had to setup the mail resource in Weblogic, also the configuration file had to change to reflect the new JNDI resource for mail sessions in the Weblogic server too.
From mailSession.JndiName=java:comp/env/mail/xxxx To mailSession.JndiName=mail/xxxx
Local session bean JNDI lookup in WebLogic - NameNotFoundException

Local session bean JNDI lookup in WebLogic - NameNotFoundException


By : Kumar
Date : March 29 2020, 07:55 AM
To fix this issue You must declare a reference to the EJB in order to look it up from java:comp. You can either use the @EJB annotation (with or without injection, see What does the @EJB annotation do?), or you can declare the reference in web.xml using .
Otherwise, if you were using a newer version of WebLogic that supported EE 6, you could use the portable java:global, java:app, or java:module namespaces in order to look up the EJB directly, but since WebLogic 10.3.6 only supports EE 5, you would need to use the configured binding name of the EJB.
Weblogic jndi NameNotFoundException occur with java config

Weblogic jndi NameNotFoundException occur with java config


By : Enricko Smith
Date : March 29 2020, 07:55 AM
wish help you to fix your issue I've had the same issue. If you're using 4.x version of spring that's probably the cause.
You should also check Weblogic's JNDI Tree. If your data source disapears from the tree after rebuilding the project, that's another symptom
Related Posts Related Posts :
shadow
Privacy Policy - Terms - Contact Us © 35dp-dentalpractice.co.uk