NamingException initialContext.lookup

I have imported a working eclipse J2EE project into JDeveloper 10.1.2.1.0 and fixed some compilation errors by adding the proper libraries. When I run the dcount-ejb project it serves up the login.jsp, but when I attempt to login to the app I get this error:
05/11/02 13:18:16 $$$getRemoteHome() NamingException:
initialContext.lookup of java:comp/env/ejb/UsersSBManager
Error instantiating web-app JNDI-context: No location specified and no suitable instance of the type 'com.cde.decemberCount.ejbJar.users.ejb.SessionBean.UsersSBRemote' found for the ejb-ref ejb/UsersSBManager
I ran "Verify Enterprise Bean" on UsersSBManager and received:
Error : Referenced home interface com.cde.decemberCount.ejbJar.users.ejb.EntityBean.UsersEBRemoteHome not found in project.
Error : Referenced remote interface
com.cde.decemberCount.ejbJar.users.ejb.EntityBean.UsersEBRemote
not found in project.
I have added the dcount-ejb.jar (containing all the beans including the UsersEBRemote) to my libraries and classpath.
What else am I forgetting

In continuing to troubleshoot this problem, I increased the size of the Embedded OC4J Server log and caught this error at the top of the file. I believe it is the core of the problem with the EJB's. I'm hoping its a simple configuration issue:
05/11/03 08:59:30 Error instantiating application 'current-workspace-app' at file:/H:/DCount/dCount-oc4j-app.xml: Error initializing ejb-module; Exception Unable to find/read assembly info for H:\DCount\ProjectNotes\config\build\lib\classes\com\cde\decemberCount (META-INF/ejb-jar.xml)

Similar Messages

EJBContext.lookup() vs InitialContext.lookup() @ EJB3.0

current design of my application uses a helper class for retrieving the system resources. according the new ejb3.0 specs i can't use dependency injection in helper classes. so, if we wanna stay with the current design, we should continue with the 2.1 style initialcontext.lookup.
my question is if brand new EJBContext.lookup()is just a wrapper that hides direct jndi usage, or there is any deep reason not to use InitialContext.lookup() anymore even if this means that the whole design should be rebuilt from scratch?
thanks folks!

Good question :-) EJBContext.lookup() is just a convenience method to make the lookup a bit easier to understand.
-- It removes the JNDI API from the developer's view.
-- It removes the notion of "java:comp/env" from the developer's view.
-- It removes the need to catch a checked exception during the lookup.
However, the object returned from EJBContext.lookup("abc") is exactly the same as the equivalent new InitialContext().lookup("java:comp/env/abc"). So, you can feel free to use the older more explicit JNDI component environment lookup wherever you'd like, but for code located directly within the bean class, it's easiest to use injection or EJBContext.lookup.
--ken

Understand InitialContext lookup - Understanding concepts

I am new to EJB, I am trying to understand the concepts. I am trying to understand example posted on https://glassfish.dev.java.net/javaee5/ejb/examples/Sful.html.
What I don't understand is how Standalone Java Client is doing the lookup and against what is it doing the lookup. Is it just getting the reference from the class that's packaged in jar file ? If so, then how is it maintaining state of the object - isn't that just as using any other class in the package. I would have thought that there would be some trading service like CORBA where server registers the object and client gets the reference to the object. But, in Client examples that I see it isn't clear how it get's the reference to the object that could either be running on the same host or different host in different JVM i.e being deployed by App server.
I am trying to understand specifics and can't seem to get simple and good information about it. Could somebody help me in understanding this.
I want to start this discussion and probably if you guys help me I'll ask some more questions.

When you deploy an application containing an EJB that exposes a Remote interface, the EJB
container registers an object representing the Remote EJB in its naming service. The naming
service lives in the server JVM. The name of the Remote EJB object is vendor-specific. SUN's
approach for assigning global JNDI names (a.k.a. "mapped" names) is here :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html#SessionBeanGlobalJNDINameAssignment
The portable way to retrieve an EJB reference is to define an EJB dependency and access that
dependency via a java:comp/env lookup or through dependency injection. However, those options
are not available to stand-alone Java clients, since stand-alone Java clients are not Java EE
components. Take a look at the approach used by the Application Client in the Sful example to
see the difference. There's more on the difference between Application Clients and stand-alone
Java clients here :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html#AppClientDef
In the case of the stand-alone client, when the no-arg InitialContext is instantiated, the client
JVM bootstraps a naming provider that knows about the server's naming service. That
works because the appserv-rt.jar has a jndi.properties file that controls the bootstrapping.
Since the stand-alone java client can not use the Java EE component environment to access
the EJB dependency, it is forced to explicitly use a global JNDI name instead. In the example
you cited, the global JNDI name has defaulted to the fully qualified name of the remote business
interface.
--ken

LoadBalance in InitialContext Lookup

Hi,
I'm having following requirement.An Ejb has been deplyed in a weblogic cluster which has two Servers Server A & B.
In Server A the Ejb is in started mode,& in Server B it is in Stopped state.Now from the server B i'm using a standalone client to lookup the ejb using JNDI name & initial context.
+          Hashtable env = new Hashtable();+
+          env.put( javax.naming.Context.INITIAL_CONTEXT_FACTORY , "weblogic.jndi.WLInitialContextFactory" );+
+          env.put( javax.naming.Context.PROVIDER_URL , "t3://SERVERB:9001,SERVERA:9001" );+
+          ctx = new InitialContext( env );+
I had given two URL's [ both Server A & Server B] in the initialcontext. What I'm expecting is the initialcontext will lookup serverB where the EJB is in stopped state, then it will lookup in Server A where the EJB is in started stated & communicate with it.
But now i'm getting the exception, it is throw from ServerB where the EJB is in Stopped state.
+Exception in thread "main" javax.naming.NameNotFoundException: Unable to resolve 'XXXEngineBean'. Resolved '' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'XXXEngineBean'. Resolved '']; remaining name 'XXXEngineBean'+
+     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)+
Thanks in Advance

Hi,
this may be the same implementation problem of class loading inside SAP NetWeaver Java we stumled oger. I posted an OSS but they will not change it.
If you have to EJBs in different enterprise applications, you MUST set an application reference from one enterprise application "A" (typically the calling with the lookup) to the enterprise application "B" that contains the EJB that is looked up.
see [http://help.sap.com/saphelp_nw73/helpdata/en/4a/ee99c229370c9ee10000000a42189c/content.htm]
"To look up a remote object, you must have its remote interface in the clientu2019s class path (for external clients) or have a class loader reference to it (for components and applications running on the server process)."
This makes the class loader of "B" the parent class loader of "A". If you omit this reference, the object that is returned by the lookup is loaded by class loader of "B" and you try to cast it to the class of class loader "A" which of course fails.
Even calling
PortableRemoteObject.narrow(obj, MyEjbLocalHome .class);
before the class cast does not help (because it does nothing to obj at all).
How do you set an application reference?
In META-INF/application-j2ee-engine.xml in enterprise applicatoin "A" enter
<?xml version="1.0" encoding="UTF-8"?>
<application-j2ee-engine xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="application-j2ee-engine.xsd">
<reference reference-type="hard">
    <reference-target provider-name="VENDOR_NAME_OF_EAR_B" target-type="application">APP_NAME_OF_EAR_B</reference-target>
</reference>
</application-j2ee-engine>
If you are working with Development Components, just add a dependency with "Runtime" and this is done automatically.
BTW if you redeploy "B", "A" will be restarted because its parent class loader changed.
Regards
Rolf

Ramifications of caching results of InitialContext(().lookup?

One of the thing we discovered during our early efforts to port a 5.1 app to
7.0 was that in 7.0 the JNDI lookups were simply taking FOREVER. It was
really horrible.
So, the question is, what are the ramifications of caching the results of
this:
Context ctx = new InitialContext();
SessionBeanHome = (SessionBeanHome) ctx.lookup("SessionBean")
We're guessing that this will fail horrible in a clustered environment, but
what about a stand alone environment?
Thanx!
Will Hartung
([email protected])

Can you provide some statistics, how much time it used to take and how much
is it taking now etc.
In 70, We know that the first InitialContext() call will take some time, as
it needs to initialize kernel and generate the hot-codegened initial context
stub. But once you have this call done, next initialContext call should be
pretty fast.
If you want to avoid the hot-codegen cost of stub, use this work around.
From the browser, try
http://server:port/bea_wls_internal/classes/weblogic/jndi/internal/RootNamin
gNode_WLStub.class
Save this class in your client package. This may give some performance
benefit.
This needs that, your classpath servlet should be turned on. See docs for
more info on this.
But I don't recommend this. This may become an issue later and may generate
version incompatibilities, if you upgrade server and forgot to re-pack the
client etc. I am not sure though.
Hope this helps.
Cheers,
..maruthi
"Will Hartung" <[email protected]> wrote in message
news:3d6a8d58$[email protected]..
One of the thing we discovered during our early efforts to port a 5.1 appto
7.0 was that in 7.0 the JNDI lookups were simply taking FOREVER. It was
really horrible.
So, the question is, what are the ramifications of caching the results of
this:
Context ctx = new InitialContext();
SessionBeanHome = (SessionBeanHome) ctx.lookup("SessionBean")
We're guessing that this will fail horrible in a clustered environment,but
what about a stand alone environment?
Thanx!
Will Hartung
([email protected])

InitialContext lookup over HTTP using a full PROVIDER_URL (including path)

Hi,
We have a standalone Java JMS client application that is sending messages to a queue on a WebLogic (WLS 9.2 MP3) server. It uses the WLInitialContextFactory (WebLogic implementation of InitialContextFactory) class to look up the initial context over HTTP when making the connection to send messages to the queue.
This all works fine when the client connects directly to the server - i.e. supplies the address of the server as the PROVIDER_URL. However, in our infrastructure, we cannot connect directly from this client to the server; we need to go via a HTTP proxy.
In a basic configuration HTTP proxy we set the provider URL to be the address of the proxy server, with the proxy is configured to route all requests straight through to the WebLogic server. This configuration also works fine - the JMS client can send messages successfully.
Unfortunately, this basic proxy configuration is still not sufficient for our Production environment. Our production proxy "fronts" multiple servers, each one identified by the first portion of the URL. So, the proxy is be configured such that requests to "http://proxy/server1/test_request" will be routed on to "http://server1/test_request", whereas a request to "http://proxy/server2/test_request" will be routed to "http://server2/test_request". This configuration works fine for basic HTTP requests, to webpages etc.
However, when we try we use this mechanism with our JMS client over HTTP, it is not working. We set the provider URL on the client to "http://proxy/server1" in order to send a message to server1. However, we find that the WLInitialContextFactory class seems to be ignoring the final part of the URL ("server1") and still sending requests directly to the root proxy address of "http://proxy", so it doesn't work.
I appreciate that this can be viewed as a WebLogic specific implementation issue for their WLInitialContextFactory, and I've raised a query with their support people on this. From my own research however, it seems the behaviour of their factory is not different to most other implementations - i.e. the major implementations would all have this issue.
I'm wondering if anyone is aware of any implementations that would handle the situation I've described. If not (or otherwise!) is there something crazy about our approach that noone has catered for it?! It seems a reasonable situation to me, but maybe I'm missing something!
Any comments, advice, etc. would be greatly appreciated, thanks.
Regards,
Adrian
Edited by: AdrianFitz on 08-Apr-2010 12:21

Hi,
Thanks for the quick response. Would you mind providing a bit more detail on your suggestion, as am not 100% sure I understand it fully.
If I see what you are getting at, are you talking about configuring proxy settings on my client side, similar to how I have to configure my internet browser with proxy settings when accessing the internet from within my companys LAN?
If I'm interpreting that right, then I guess my use of the word proxy might be a bit inaccurate or lead to some confusion. What my orginal post described as a proxy should have been more accurately describes as a reverse proxy (acting primarily as a load balancer).
Ideally, other than changing the URL slightly, the client should be 'unaware' that it is going through a proxy at all.
Hope that clarifies somewhat, any further comments would be great! Thanks.
Regards,
Adrian

Problem in using InitialContext to do a lookup of CMP EnitityBean.

Hi,
I am running WLS 5.1 SP6 on Windows98. I am trying to lookup a CMP entiry bean from
Java 1.3 client. I can successfully create the InitialContext but having trouble in using it to do the lookup. I get the following error:
jndiContext is javax.naming.InitialContext@61f24(This is line is the result of println : see code)
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.titan.cabin.Client_1.main(Client_1.java:21)
My code of the Java 1.3 client is as follows:
package com.titan.cabin;
import com.titan.cabin.CabinHome;
import com.titan.cabin.Cabin;
import com.titan.cabin.CabinPK;
import javax.naming.InitialContext;
import javax.naming.Context;
import javax.naming.NamingException;
import java.rmi.RemoteException;
import java.util.Properties;
import java.util.Hashtable;
public class Client_1 {
public static void main(String [] args){
try {
InitialContext jndiContext = getWeblogicInitialContext();
System.out.println("jndiContext is " + jndiContext);
CabinHome home = (CabinHome)(jndiContext.lookup("CabinHome"));
Cabin cabin_1 = home.create(1);
System.out.println("created it!");
cabin_1.setName("Master Suite");
cabin_1.setDeckLevel(1);
cabin_1.setShip(1);
cabin_1.setBedCount(3);
CabinPK pk = new CabinPK();
pk.id = 1;
System.out.println("keyed it! ="+ pk);
Cabin cabin_2 = home.findByPrimaryKey(pk);
System.out.println("found by key! ="+ cabin_2);
System.out.println(cabin_2.getName());
System.out.println(cabin_2.getDeckLevel());
System.out.println(cabin_2.getShip());
System.out.println(cabin_2.getBedCount());
} catch (java.rmi.RemoteException re){re.printStackTrace();}
catch (javax.naming.NamingException ne){ne.printStackTrace();}
catch (javax.ejb.CreateException ce){ce.printStackTrace();}
catch (javax.ejb.FinderException fe){fe.printStackTrace();}
public static InitialContext getWeblogicInitialContext()
throws javax.naming.NamingException {
InitialContext ctx = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY, weblogic.jndi.WLInitialContextFactory.class.getName());
ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
ht.put(Context.SECURITY_PRINCIPAL, "system");
ht.put(Context.SECURITY_CREDENTIALS, new weblogic.common.T3User("system", "askpanch"));
try {
ctx = new InitialContext(ht);
// Use the context in your program
catch (NamingException e) {
System.out.println("InitialContext could not be created");
System.out.println("The explanation is " + e.getExplanation());
e.printStackTrace();
// a failure occurred
finally {
try {ctx.close();}
catch (Exception e) {
// a failure occurred
return ctx;
The message printed by System.out.println shows that InitialContext is created but exception is thrown when it is used by the lookup method.
My classpath is as follows:
CLASSPATH=C:\VisualCafeEE\Java\Lib\ERADPUBLIC.JAR;C:\VisualCafeEE\Java\Lib\servlet.jar;C:\VisualCafeEE\Java\Lib\server.jar;C:\VisualCafeEE\Bin\Components\templa
tes.jar;C:\VisualCafeEE\Java\Lib\javax_ejb.ZIP;C:\VisualCafeEE\Java\Lib\jndi.jar;C:\VisualCafeEE\Bin\Components\vcejbwl.jar;C:\VisualCafeEE\Bin\sb;C:\VisualCafe
EE\Bin\sb\classes\sb.jar;.;;C:\VisualCafeEE\Java\Lib;C:\VisualCafeEE\Java\Lib\SYMCLASS.ZIP;C:\VisualCafeEE\Java\Lib\CLASSES.ZIP;C:\VisualCafeEE\Java\Lib\COLLECT
IONS.ZIP;C:\VisualCafeEE\Java\Lib\ICEBROWSERBEAN.JAR;C:\VisualCafeEE\Java\Lib\SYMTOOLS.JAR;C:\VisualCafeEE\JFC\SWINGALL.JAR;C:\VisualCafeEE\Bin\Components\SFC.J
AR;C:\VisualCafeEE\Bin\Components\SYMBEANS.JAR;C:\VisualCafeEE\Java\Lib\DBAW.ZIP;C:\VisualCafeEE\Bin\Components\DBAW_AWT.JAR;C:\VisualCafeEE\Bin\Components\Data
bind.JAR;C:\VisualCafeEE\Java\Lib\ERADTOOLS.JAR;;C:\IBMVJava\eab\runtime30;C:\IBMVJava\eab\runtime20;;.;c:\Weblogic\classes;c:\weblogic\lib\weblogicaux.jar
Any help to solove this problem from anybody is greatly appreciated. I am including some other related articles in this newsgroup for your ready reference(see below).
Thanks a lot,
Ashok Pancharya
Email: [email protected]
Sounds like your WL config is a bit different, perhaps a classpath issue or
a missing .properties file or a different command line. For whatever
reason, the factory does not know what class is supposed to be used as the
initial context.
Peace.
Cameron Purdy
[email protected]
http://www.tangosol.com
WebLogic Consulting Available
"Chris Solar" <[email protected]> wrote in message
news:[email protected]...
Hi-
I'm running WLS 5.1 on NT 4.0 (SP6).
For some reason, I'm unable to use the default
constructor to get an initial context. That is,
if I try:
InitialContext ctx = new InitialContext();
I get a NoInitialContextException, as in:
"Need to specify class name in environment or system
property, or as an applet parameter, or in an application
resource file: java.naming.factory.initial"
This does not happen if I pass in a HashTable or Properties
object containing a value for the initial context factory
(even if it's just weblogic.jndi.WLInitialContextFactory).
Colleagues of mine seem to be able to use
the defaut constructor without any problems.
What am I missing?
-Chris.

Thanks Gene. Good solution. I could solve the problem which is explained in my another article posted just before a minute you posted this response.
Thanks again.
Ashok Pancharya
"Gene Chuang" <[email protected]> wrote:
According to your getWeblogicInitialContext(), you are putting ctxt.close() in a finally block,
which will always get executed, and then returning ctxt. Don't think you can do any lookups with a
closed Context.
Gene Chuang
Join Kiko.com!
"Ashok Pancharya" <[email protected]> wrote in message news:[email protected]...
Hi,
I am running WLS 5.1 SP6 on Windows98. I am trying to lookup a CMP entiry bean from
Java 1.3 client. I can successfully create the InitialContext but having trouble in using it todo the lookup. I get the following error:
jndiContext is javax.naming.InitialContext@61f24(This is line is the result of println : see code)
javax.naming.NoInitialContextException: Need to specify class name in environment or systemproperty, or as an applet parameter, or in an application resource file:
java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.titan.cabin.Client_1.main(Client_1.java:21)
My code of the Java 1.3 client is as follows:
package com.titan.cabin;
import com.titan.cabin.CabinHome;
import com.titan.cabin.Cabin;
import com.titan.cabin.CabinPK;
import javax.naming.InitialContext;
import javax.naming.Context;
import javax.naming.NamingException;
import java.rmi.RemoteException;
import java.util.Properties;
import java.util.Hashtable;
public class Client_1 {
public static void main(String [] args){
try {
InitialContext jndiContext = getWeblogicInitialContext();
System.out.println("jndiContext is " + jndiContext);
CabinHome home = (CabinHome)(jndiContext.lookup("CabinHome"));
Cabin cabin_1 = home.create(1);
System.out.println("created it!");
cabin_1.setName("Master Suite");
cabin_1.setDeckLevel(1);
cabin_1.setShip(1);
cabin_1.setBedCount(3);
CabinPK pk = new CabinPK();
pk.id = 1;
System.out.println("keyed it! ="+ pk);
Cabin cabin_2 = home.findByPrimaryKey(pk);
System.out.println("found by key! ="+ cabin_2);
System.out.println(cabin_2.getName());
System.out.println(cabin_2.getDeckLevel());
System.out.println(cabin_2.getShip());
System.out.println(cabin_2.getBedCount());
} catch (java.rmi.RemoteException re){re.printStackTrace();}
catch (javax.naming.NamingException ne){ne.printStackTrace();}
catch (javax.ejb.CreateException ce){ce.printStackTrace();}
catch (javax.ejb.FinderException fe){fe.printStackTrace();}
public static InitialContext getWeblogicInitialContext()
throws javax.naming.NamingException {
InitialContext ctx = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,weblogic.jndi.WLInitialContextFactory.class.getName());
ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
ht.put(Context.SECURITY_PRINCIPAL, "system");
ht.put(Context.SECURITY_CREDENTIALS, new weblogic.common.T3User("system", "askpanch"));
try {
ctx = new InitialContext(ht);
// Use the context in your program
catch (NamingException e) {
System.out.println("InitialContext could not be created");
System.out.println("The explanation is " + e.getExplanation());
e.printStackTrace();
// a failure occurred
finally {
try {ctx.close();}
catch (Exception e) {
// a failure occurred
return ctx;
The message printed by System.out.println shows that InitialContext is created but exception isthrown when it is used by the lookup method.
My classpath is as follows:
CLASSPATH=C:\VisualCafeEE\Java\Lib\ERADPUBLIC.JAR;C:\VisualCafeEE\Java\Lib\servlet.jar;C:\VisualCafe
EE\Java\Lib\server.jar;C:\VisualCafeEE\Bin\Components\templa
>
tes.jar;C:\VisualCafeEE\Java\Lib\javax_ejb.ZIP;C:\VisualCafeEE\Java\Lib\jndi.jar;C:\VisualCafeEE\Bin
\Components\vcejbwl.jar;C:\VisualCafeEE\Bin\sb;C:\VisualCafe
>
EE\Bin\sb\classes\sb.jar;.;;C:\VisualCafeEE\Java\Lib;C:\VisualCafeEE\Java\Lib\SYMCLASS.ZIP;C:\Visual
CafeEE\Java\Lib\CLASSES.ZIP;C:\VisualCafeEE\Java\Lib\COLLECT
>
IONS.ZIP;C:\VisualCafeEE\Java\Lib\ICEBROWSERBEAN.JAR;C:\VisualCafeEE\Java\Lib\SYMTOOLS.JAR;C:\Visual
CafeEE\JFC\SWINGALL.JAR;C:\VisualCafeEE\Bin\Components\SFC.J
>
AR;C:\VisualCafeEE\Bin\Components\SYMBEANS.JAR;C:\VisualCafeEE\Java\Lib\DBAW.ZIP;C:\VisualCafeEE\Bin
\Components\DBAW_AWT.JAR;C:\VisualCafeEE\Bin\Components\Data
>
bind.JAR;C:\VisualCafeEE\Java\Lib\ERADTOOLS.JAR;;C:\IBMVJava\eab\runtime30;C:\IBMVJava\eab\runtime20
;;.;c:\Weblogic\classes;c:\weblogic\lib\weblogicaux.jar
Any help to solove this problem from anybody is greatly appreciated. I am including some otherrelated articles in this newsgroup for your ready reference(see below).
Thanks a lot,
Ashok Pancharya
Email: [email protected]
Sounds like your WL config is a bit different, perhaps a classpath issue or
a missing .properties file or a different command line. For whatever
reason, the factory does not know what class is supposed to be used as the
initial context.
Peace.
Cameron Purdy
[email protected]
http://www.tangosol.com
WebLogic Consulting Available
"Chris Solar" <[email protected]> wrote in message
news:[email protected]...
Hi-
I'm running WLS 5.1 on NT 4.0 (SP6).
For some reason, I'm unable to use the default
constructor to get an initial context. That is,
if I try:
InitialContext ctx = new InitialContext();
I get a NoInitialContextException, as in:
"Need to specify class name in environment or system
property, or as an applet parameter, or in an application
resource file: java.naming.factory.initial"
This does not happen if I pass in a HashTable or Properties
object containing a value for the initial context factory
(even if it's just weblogic.jndi.WLInitialContextFactory).
Colleagues of mine seem to be able to use
the defaut constructor without any problems.
What am I missing?
-Chris.

NamingException / SocketException during AppMod lookup

Hi,
below there is an Exception i received while try to connect to the AppModule,
deployed as "AppModule Session Bean", to an OC4J 9.0.2. At the End you see my
Sourcecode which produces the Exception.
Does anyone have an Idea whats going wrong with my sourcecode?
Regards Mirko
-- Exception --
Setting up Initial Context...
Diagnostics: (BC4J Bootstrap) Routing diagnostics to standard output (use -Djbo.debugoutput=silent to remove)
[00] Diagnostic Properties: Timing:false Functions:false Linecount:true Threshold:6
[01] CommonMessageBundle (language base) being initialized
[02] Stringmanager using default locale: 'null'
[03] BC4JDeployPlatform: EjbIas
Doing LookUp...de.orb.server.orbServerModule_cm
javax.naming.NamingException: Lookup error: java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read; nested exception is:
java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read
java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
void oracle.jbo.client.remote.ejb.ias.AmHomeImpl.remoteLookup()
void oracle.jbo.client.remote.ejb.ias.AmHomeImpl.initRemoteHome()
void oracle.jbo.client.remote.ejb.ias.AmHomeImpl.<init>(oracle.jbo.JboContext, java.lang.String)
oracle.jbo.common.JboHome oracle.jbo.client.remote.ejb.ias.InitialContextImpl.createJboHome(java.lang.String)
java.lang.Object oracle.jbo.common.JboInitialContext.lookup(java.lang.String)
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
de.orb.server.common.orbServerModule de.orb.net.CommunicationLayer.getApplicationModuleInstance(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String)
void de.orb.net.CommunicationLayer.connectToApplicationModule()
de.pantarhei.datacarrier.DataCarrier de.orb.net.CommunicationLayer.getPanelData(int)
void de.orb.MainFrame.jbInit()
void de.orb.MainFrame.<init>(java.lang.String)
void de.orb.MainApplication.<init>(java.lang.String[])
void de.orb.MainApplication.main(java.lang.String[])
couldn't connect to AppModule
-- source --
env.put (Context.INITIAL_CONTEXT_FACTORY, JboContext.JBO_CONTEXT_FACTORY);
env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_EJB_IAS);
env.put(JboContext.APPLICATION_PATH, "serverEJB");
env.put(Context.SECURITY_PRINCIPAL, "admin"); // OC4J User
env.put(Context.SECURITY_CREDENTIALS, "admin"); // OC4J Passwd
env.put(JboContext.HOST_NAME, machineNo);
env.put(JboContext.CONNECTION_PORT, portNo);
try {
System.out.println("Setting up Initial Context...");
Context ic = new InitialContext(env);
System.out.println("Doing LookUp..." + amName);
orbServerModuleHome home = (orbServerModuleHome)ic.lookup(amName);
System.out.println("Calling create...");
appMod = (orbServerModule)home.create();
System.out.println("establishing Connection...");
appMod.getTransaction().connect(connStr);
} catch(Exception ex) {
throw ex;

Hi,
below there is an Exception i received while try to connect to the AppModule,
deployed as "AppModule Session Bean", to an OC4J 9.0.2. At the End you see my
Sourcecode which produces the Exception.
Does anyone have an Idea whats going wrong with my sourcecode?
Regards Mirko
-- Exception --
Setting up Initial Context...
Diagnostics: (BC4J Bootstrap) Routing diagnostics to standard output (use -Djbo.debugoutput=silent to remove)
[00] Diagnostic Properties: Timing:false Functions:false Linecount:true Threshold:6
[01] CommonMessageBundle (language base) being initialized
[02] Stringmanager using default locale: 'null'
[03] BC4JDeployPlatform: EjbIas
Doing LookUp...de.orb.server.orbServerModule_cm
javax.naming.NamingException: Lookup error: java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read; nested exception is:
java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read
java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
void oracle.jbo.client.remote.ejb.ias.AmHomeImpl.remoteLookup()
void oracle.jbo.client.remote.ejb.ias.AmHomeImpl.initRemoteHome()
void oracle.jbo.client.remote.ejb.ias.AmHomeImpl.<init>(oracle.jbo.JboContext, java.lang.String)
oracle.jbo.common.JboHome oracle.jbo.client.remote.ejb.ias.InitialContextImpl.createJboHome(java.lang.String)
java.lang.Object oracle.jbo.common.JboInitialContext.lookup(java.lang.String)
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
de.orb.server.common.orbServerModule de.orb.net.CommunicationLayer.getApplicationModuleInstance(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String)
void de.orb.net.CommunicationLayer.connectToApplicationModule()
de.pantarhei.datacarrier.DataCarrier de.orb.net.CommunicationLayer.getPanelData(int)
void de.orb.MainFrame.jbInit()
void de.orb.MainFrame.<init>(java.lang.String)
void de.orb.MainApplication.<init>(java.lang.String[])
void de.orb.MainApplication.main(java.lang.String[])
couldn't connect to AppModule
-- source --
env.put (Context.INITIAL_CONTEXT_FACTORY, JboContext.JBO_CONTEXT_FACTORY);
env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_EJB_IAS);
env.put(JboContext.APPLICATION_PATH, "serverEJB");
env.put(Context.SECURITY_PRINCIPAL, "admin"); // OC4J User
env.put(Context.SECURITY_CREDENTIALS, "admin"); // OC4J Passwd
env.put(JboContext.HOST_NAME, machineNo);
env.put(JboContext.CONNECTION_PORT, portNo);
try {
System.out.println("Setting up Initial Context...");
Context ic = new InitialContext(env);
System.out.println("Doing LookUp..." + amName);
orbServerModuleHome home = (orbServerModuleHome)ic.lookup(amName);
System.out.println("Calling create...");
appMod = (orbServerModule)home.create();
System.out.println("establishing Connection...");
appMod.getTransaction().connect(connStr);
} catch(Exception ex) {
throw ex;
} Try..
ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup(amName);
ApplicationModule appModd = home.create();
If you have exported methods then you should be able to cast the
appmodule returned by home.create() to you're appmodule interface. This is the interface generated in the common subpackage.

NamingException and ClassCastException during jndi lookup

Hi,
I am trying to access the SAP database(MaxDb)using JNDI lookup in WebDynpro simple java project.
But, during lookup I am getting the following error
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name : jdbc/VSLOOKUP , can not resolve object reference [Root exception is java.lang.ClassCastException]
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:469)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:558)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.vitalspring.healthbenefits.dbaccess.DBAccessHelper.main(DBAccessHelper.java:51)
Caused by: java.lang.ClassCastException
     at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:149)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:466)
     ... 3 more
Can anybody throw some light on it?
Because, it's urgent for my project.
I would appreciate any kind of help in this regard.
Thanks & Regards,
Rambabu Kancharla

Hello Anilkumar,
Sorry for delay in reply as I was on out of work and didn't get chance to check the SDN forums.
I was able to do it in latest version sneak preview 11.
I think the problem with the version.
Thanks,
Rambabu

NamingException on EJB jndi lookup

I have two applications - deployed under the "default instance".
When I start up OC4J and deloy app1 and app2, then app1 can do a JNDI lookup on a session bean that resides in App2. It uses the RMIInitialContextFactory.
Provider is "ormi://localhost/app2"
My problem is that if I undeploy and redeploy app2, then app1 suddenly can't do a lookup to any sessionBean found in app2 anymore, even though the jndi name still shows up in the browser, and if I try to look it up from an external application running outside of oc4j (with exactly the same code as I'm using in app1), it also works.
So why is app1 not able to find app2 via jndi after a redeployment?
D

Avi - thank you for your response.
First of all, I run on Suse Linux 10.1. Dunno if that's any help, but hey, more info can't help :)
Let's answer your questions:
1.) OCJ4 Version: 10.1.3.0.0 (build 060119.1546.05277)
2.) JDK Version: 1.5.0_07-b03
As for your suggestions:
1.) app1 = parent of app2.
I'm rather new to Oracle, so maybe I made a mistake during my investigations. Still, I'd like to give a breakdown: I built a framework-type application, and thought about deploying "child modules" (plug-in applications) underneath it, as you proposed.
This worked fine, but there comes a problem whenever you try to use something like Hibernate in any application that's not deployed in the root (ie any app that's deployed as a child of another). The problem came in 2 flavours:
A) If you use a jar in the parent and try to do resource loading from the child, the context of the parent is used the whole time. Since the search-policy of the class-loader is loaded->parent->shared->local, and if Hibernate is already used in the parent, it never gets to the child and thus trying to load a resource in the child is futile since parent can't see child context.
B) Lets say you're not using Hibernate at all in the parent application. When doing resource loading (eg the hibernate.cfg.xml file), Hibernate tries to locate the resource via Thread.currentThread().getContextClassLoader(). OC4J returns the parent-app's thread as the currentThread, NOT that of the child-application that you're actually running the code from, thus it will never be able to pick up resources from within a jar part of the child application. The only way that I managed to get it to work, was to include the Hibernate3.jar as part of the EAR deployment (ie listed it as <library path...> in the orion-application.xml. Putting it in shared-libs or app-libs didn't work...ever. Also, if I happened to use Hibernate in the parent-application, it doesn't matter if I put hibernate3.jar in the EAR of the child - the parent-version gets picked up and used due to the search-policy... NOTE: This is in a JAR - I'm not using WAR's so cannot force local loading as is possible with web-apps...
I then opted to deploy applications seperately under the root, and using RMI to communicate from the framework-application to its "modules", and vice-versa. The master doesn't know the exact type of the remote interface of whatever child-module it needs to call, so it uses reflection to call the "create" on the EJBHome of whatever child-module it needs to invoke as well as the method on the actual remote-interface.
Please note, if I deploy both applications (master and child), and perform JNDI lookups from master to child, it works perfectly. As soon as I do a redeploy (or explicity undeploy, deploy), JNDI fails. External clients, though, works all the time. Also, if I redeploy the child before ever calling it from the parent-application, it also works after I did redeployment. It's as if, when you do a JNDI lookup the first time, it caches something and from there on it breaks if you do a redeploy and perform a consequent app-to-app JNDI lookup...
2.) dedicated.rmicontext=true
I tried this by setting it as a JNDI property before getting the InitialContext - makes no difference, unfortunately.
//========CODE============================
// This is in a SessionBean inside the Master Application. For the time being I've hard-coded the provider-url of the client-application.
// NOTE: This EXACT same code is used in the external java client - there it works perfect every time, whether I redeploy or not.
//========================================
Hashtable<String, String> env = new Hashtable<String, String>();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.PROVIDER_URL, "ormi://localhost/client-application");
env.put(Context.SECURITY_PRINCIPAL, "oc4jadmin");
env.put(Context.SECURITY_CREDENTIALS, "MyPassword");
env.put("dedicated.rmicontext","true");
InitialContext ctx = null;
try {
     ctx = new InitialContext(env);
     // WHEN I REDEPLOY, CODE CRASHES ON THE NEXT LINE
     Object home = ctx.lookup("ejb/TestWorkerAProxyBean");
     EJBHome obHome = (EJBHome) PortableRemoteObject.narrow(home, EJBHome.class);
     System.out.println("EJBHOME Is [" + obHome + "]");
     final Object invocationTarget = MethodUtils.invokeExactMethod(obHome,"create",new Object[0]);
     System.out.println("invocation target = [" + invocationTarget + "]");
     ClassLoader classLoader = Thread.currentThread().getContextClassLoader();
     IWorkerProxy proxy = (IWorkerProxy)Proxy.newProxyInstance(classLoader, new Class[]{IWorkerProxy.class}, new InvocationHandler() {
          public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
               try {
                    Method remoteEjbMethod = invocationTarget.getClass().getMethod(method.getName(),method.getParameterTypes());
                    return remoteEjbMethod.invoke(invocationTarget, args);
               } catch (Exception e) {
                    ExceptionHandler.handle(e);
               return null;
} catch (NamingException ne) {
     System.out.println("NamingException");
     ne.printStackTrace();
} catch (NoSuchMethodException e) {
     System.out.println("NoSuchMethodException");
     e.printStackTrace();
} catch (Exception e) {
     System.out.println("Other Exception");
     e.printStackTrace();
==========================
===========EXCEPTION (ONLY IF I REDEPLOY - IT WORKS PERFECT IF I RUN IT FIRST TIME)=================
==========================
06/09/25 17:15:51 NamingException
06/09/25 17:15:51 javax.naming.NameNotFoundException: ejb/TestWorkerAProxyBean not found
06/09/25 17:15:51 at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
06/09/25 17:15:51 at javax.naming.InitialContext.lookup(InitialContext.java:351)
06/09/25 17:15:51 at com.myapp.master.RequestProcessorBean.processRequest(RequestProcessorBean.java:140)
06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
06/09/25 17:15:51 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
06/09/25 17:15:51 at java.lang.reflect.Method.invoke(Method.java:585)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.TxSupportsInterceptor.invoke(TxSupportsInterceptor.java:37)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:86)
06/09/25 17:15:51 at RequestProcessorLocal_StatelessSessionBeanWrapper4.processRequest(RequestProcessorLocal_StatelessSessionBeanWrapper4.java:37)
06/09/25 17:15:51 at com.myapp.master.gateway.FrameworkGatewayBean.processObjectRequest(FrameworkGatewayBean.java:172)
06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
06/09/25 17:15:51 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
06/09/25 17:15:51 at java.lang.reflect.Method.invoke(Method.java:585)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.TxSupportsInterceptor.invoke(TxSupportsInterceptor.java:37)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:86)
06/09/25 17:15:51 at FrameworkGatewayRemote_StatelessSessionBeanWrapper10.processObjectRequest(FrameworkGatewayRemote_StatelessSessionBeanWrapper10.java:94)
06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
06/09/25 17:15:51 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
06/09/25 17:15:51 at java.lang.reflect.Method.invoke(Method.java:585)
06/09/25 17:15:51 at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
06/09/25 17:15:51 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
06/09/25 17:15:51 at java.lang.Thread.run(Thread.java:595)

EJB 3.0 and jndi lookup (simple question)

hi all,
i am newbie on Weblogic Application Server and i have some issues,
i have weblogic application server 10.0, also i have oracle timesten in-memory database, i have configured datasource and deploy my ejb 3.0 application, but i could not done jndi lookup?
here is my example:
1. one stateless session bean :
import javax.ejb.Remote;
@Remote
public interface InsertSubscriber {
     public void insertSubscriber(SubscriberT subscriberT);
} 2. here is it's implementation :
@Remote(InsertSubscriber.class)
@Stateless
public class InsertSubscriberBean implements InsertSubscriber {
     @PersistenceContext(unitName = "TimesTenDS")
     private EntityManager oracleManager;
     public void insertSubscriber(SubscriberT subscriber)
          try {
               System.out.println("started");
               oracleManager.persist(subscriber);
               System.out.println("end");
          } catch (Exception e) {
               e.printStackTrace();
}3 and my test client :
public class Client {
     public static void main(String[] args) {
          Context ctx = null;
          Hashtable ht = new Hashtable();
          ht.put(Context.INITIAL_CONTEXT_FACTORY,
                    "weblogic.jndi.WLInitialContextFactory");
          ht.put(Context.PROVIDER_URL, "t3://192.9.200.222:7001");
          try {
               ctx = new InitialContext(ht);
               InsertSubscriber usagefasade = (InsertSubscriber) ctx
                         .lookup("ejb.InsertSubscriberBean");
          } catch (NamingException e) {
               e.printStackTrace();
          } finally {
               try {
                    ctx.close();
               } catch (Exception e) {
                    e.printStackTrace();
}what i did incorrect ???
i got error like this : Name not fount exception
when i tried to view jndi tree on weblogic server application console i found this :
     Binding Name:
TimestenExampleTimestenExample_jarInsertSubscriberBean_InsertSubscriber
     Class:
test.InsertSubscriberBean_o7jk9u_InsertSubscriberImpl_1000_WLStub
     Hash Code:
286
     toString Results:
weblogic.rmi.internal.CollocatedRemoteRef - hostID: '2929168367193491522S::billing_domain:AdminServer', oid: '286', channel: 'null'what does it mean how i can done lookup to jndi ?
Regards,
Paata Lominadze,
Magticom LTD.
Georgia.

Hi All,
I am using the weblogic cluster with session replication and EJB 2.0 with Local entity beans.
for fail-over session should be replicated to another server so we can achive the same session if 1st server fails.
Suppose i m using two managed server(server1,server2) in the cluster.I am storing the object of class ABC into session and object contains the instance of Local-EntityBean home but i put that as a transient.I have also override the readObject and write object method.
when write object is called on 1st server,readObject method should be called on second server so we will be sure that session is replicating properly.
pleaase find the code below : -
public IssuerPageBean() {
initEJB();
private void readObject(java.io.ObjectInputStream stream) throws IOException, ClassNotFoundException {
stream.defaultReadObject();
initEJB();
initializeCommonObject();
private void writeObject(java.io.ObjectOutputStream stream) throws IOException {
stream.defaultWriteObject();
private void initEJB() {
try {
ic = new InitialContext();
issuerHome = (LocalIssuerHome) ic.lookup("java:comp/env/Issuer");
} catch (NamingException e) {
e.printStackTrace();
in my case if i am calling the constructor IssuerPageBean(),it calls the initEJB() method and lookeup the entity local home properly but when readObject method is called on another server only initEJB() method is called directly and getting the exception below :
WARNING: Error during create -
javax.naming.NameNotFoundException: remaining name: env/ejb/Client
at weblogic.j2eeclient.SimpleContext.resolve(Ljavax/naming/Name;Z)Ljavax/naming/Context;(SimpleContext.java:35)
at weblogic.j2eeclient.SimpleContext.resolve(Ljavax/naming/Name;)Ljavax/naming/Context;(SimpleContext.java:39)
at weblogic.j2eeclient.SimpleContext.lookup(Ljavax/naming/Name;)Ljava/lang/Object;(SimpleContext.java:57)
at weblogic.j2eeclient.SimpleContext.lookup(Ljavax/naming/Name;)Ljava/lang/Object;(SimpleContext.java:57)
at weblogic.j2eeclient.SimpleContext.lookup(Ljava/lang/String;)Ljava/lang/Object;(SimpleContext.java:62)
at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(Ljava/lang/String;)Ljava/lang/Object;(ReadOnlyCont
extWrapper.java:45)
at weblogic.jndi.internal.AbstractURLContext.lookup(Ljava/lang/String;)Ljava/lang/Object;(AbstractURLContext.jav
a:130)
at javax.naming.InitialContext.lookup(Ljava/lang/String;)Ljava/lang/Object;(InitialContext.java:347)
at com.lb.equities.veda.tools.salesvault.jsp.ClientPageBean.initEJB()V(ClientPageBean.java:218)
at com.lb.equities.veda.tools.salesvault.jsp.ClientPageBean.readObject(Ljava/io/ObjectInputStream;)V(ClientPageB
ean.java:191)
at java.lang.LangAccessImpl.readObject(Ljava/lang/Class;Ljava/lang/Object;Ljava/io/ObjectInputStream;)V(Unknown
Source)
at java.io.ObjectStreamClass.invokeReadObject(Ljava/lang/Object;Ljava/io/ObjectInputStream;)V(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Ljava/lang/Object;Ljava/io/ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava/lang/Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava/lang/Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava/lang/Object;(Unknown Source)
at java.util.HashMap.readObject(Ljava/io/ObjectInputStream;)V(Unknown Source)
at java.lang.LangAccessImpl.readObject(Ljava/lang/Class;Ljava/lang/Object;Ljava/io/ObjectInputStream;)V(Unknown
Source)
at java.io.ObjectStreamClass.invokeReadObject(Ljava/lang/Object;Ljava/io/ObjectInputStream;)V(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Ljava/lang/Object;Ljava/io/ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava/lang/Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava/lang/Object;(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Ljava/lang/Object;Ljava/io/ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Ljava/lang/Object;Ljava/io/ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava/lang/Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava/lang/Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava/lang/Object;(Unknown Source)
at weblogic.common.internal.ChunkedObjectInputStream.readObject()Ljava/lang/Object;(ChunkedObjectInputStream.jav
a:120)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(Ljava/lang/Class;)Ljava/lang/Object;(MsgAbbrevInputStream.java:
121)
at weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(ILweblogic/rmi/spi/InboundRequest;Lweblogic/rmi
/spi/OutboundResponse;Ljava/lang/Object;)Lweblogic/rmi/spi/OutboundResponse;(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(Lweblogic/rmi/extensions/server/RuntimeMethodDescriptor;Lweblogic
/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;)V(BasicServerRef.java:492)
Please help .
Thanks in Advance.
Edited by hforever at 03/04/2008 7:28 AM

I can't lookup EJB (3.0) in WebLogic 12 using ENC

I have a simple application divided in 2 modules:
HolaMundo - Servlet component
SimpleEJB - EJB Component
The EJB Component use EJB 3.0. I created a local business interface with one method. A stateless EJB that implement that interface. And I use the ejb-jar.xml for declare it.
And a Servlet that use the EJB.
In Glassfish or Tomee this way for working with EJB works, but i don't understand why it doesn't work in WebLogic 12...
When i try to access to the servlet, i get an error. this is the error:
javax.naming.NameNotFoundException: While trying to look up /app/SimpleEJB/Example!com.edwin.ejb.ExampleLocal in /app/webapp/HolaMundo.war/1051995086.; remaining name '/app/SimpleEJB/Example!com/edwin/ejb/ExampleLocal'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1180)
at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:146)
Servlet:
package servlet;
import java.io.IOException;
import java.io.PrintWriter;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import com.edwin.ejb.ExampleLocal;
public class EJB extends HttpServlet {
   private static final long serialVersionUID = 1L;
   @Override
   protected void doGet(HttpServletRequest arg0, HttpServletResponse arg1)
   throws ServletException, IOException {
   PrintWriter out = arg1.getWriter();
   ExampleLocal el2;
   try {
el2 = (ExampleLocal) new InitialContext()
   .lookup("java:app/SimpleEJB/Example!com.edwin.ejb.ExampleLocal");
   out.println("EJBBBB: " + el2.nombre());
   } catch (NamingException e) {
e.printStackTrace();
Local business interface:
package com.edwin.ejb;
public interface ExampleLocal {
    public String nombre();
EJB Stateless:
package com.edwin.ejb;
public class Example implements ExampleLocal{
    @Override
    public String nombre() {
        return "Edwin";
ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
<display-name>SimpleEJB </display-name>
<enterprise-beans>
    <session>
        <ejb-name>Example</ejb-name>
        <business-local>com.edwin.ejb.ExampleLocal</business-local>
        <ejb-class>com.edwin.ejb.Example</ejb-class>
        <session-type>Stateless</session-type>
    </session>
</enterprise-beans>
</ejb-jar>

Both answers did not work. I do not understand why it did not work because in other Java EE Servers it works.
My JNDI Tree (Screenshot):
http://oi58.tinypic.com/vs1jjd.jpg
However, i could get the EJB when i use the Global ENC, but i got a Casting Exception...
Eg:
try {
ej = (EjLocal) new InitialContext().lookup("java:global.EjemploEJB.Ej!stateless.EjLocal");
out.print("EJ: "+ej.ej());
} catch (NamingException e) {
e.printStackTrace();
Output:
java.lang.ClassCastException: stateless.Ej_1aafe_EjLocalImpl cannot be cast to stateless.EjLocal
at servlet.Ejemplo.doGet(Ejemplo.java:33)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731).....
There is a strange value in the EJB's JNDI Tree:
Header 1
Header 2
Binding Name:
java:global.EjemploEJB.Ej!stateless.EjLocal
Class:
stateless.Ej_1aafe_EjLocalImpl
Hash Code:
2021087981
toString Results:
stateless.Ej_1aafe_EjLocalImpl@78775aed

When I installed jms (j2ee1.3) my lookups doesn't work anymore...

Hi. I was using j2se 1.3 and performed some lookups on objects from an Oracle 8.1.7.
Then, in order to use jms, I installed j2ee 1.3 and j2se 1.3.1. Now my lookups doesn't work anymore, but my lookups on jms objects (por example Queue or QueueConnectionFactory) does work fine. This is the code that produces the error, and the error:
****** CODE *************
String serviceURL = "sess_iiop://desarrollo:2482:SCANALES";
String objectName = "/test/sInformacionSalida";
ServicioInformacionSalida sis = null;
Hashtable env = new Hashtable ();
env.put (Context.URL_PKG_PREFIXES, "oracle.aurora.jndi:com.sun.enterprise.naming");
env.put (Context.SECURITY_PRINCIPAL, "USER");
env.put (Context.SECURITY_CREDENTIALS, "USER");
env.put (Context.SECURITY_AUTHENTICATION, ServiceCtx.NON_SSL_LOGIN);
InitialContext ic = null;
try {
ic = new InitialContext(env);
} catch (NamingException nE) {}
System.out.println("ASIF: Lookup de servicio de salida de informacion de formateo...");
try {
sis = (ServicioInformacionSalida)ic.lookup(serviceURL + objectName);
} catch(NamingException nE) {
System.out.println("ASIF: Error en el lookup: " + nE.getExplanation());
System.out.println("ASIF: " + nE.toString());
nE.printStackTrace();
System.exit(-1);
**************** ERROR ******************
ASIF: Error en el lookup: Unknown service: 200.12.145.40:2482:SCANALES
ASIF: javax.naming.CommunicationException: Unknown service: 200.12.145.40:2482:SCANALES
javax.naming.CommunicationException: Unknown service: 200.12.145.40:2482:SCANALES
at oracle.aurora.jndi.sess_iiop.SessionCtx.initialContext(SessionCtx.java:647)
at oracle.aurora.jndi.sess_iiop.SessionCtx.<init>(SessionCtx.java:67)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.createSession(ServiceCtx.java:161)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.login(ServiceCtx.java:349)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.defaultSession(ServiceCtx.java:219)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.lookup(ServiceCtx.java:373)
at oracle.aurora.jndi.sess_iiop.sess_iiopURLContext.lookup(sess_iiopURLContext.java:256)
at oracle.aurora.jndi.sess_iiop.sess_iiopURLContext.lookup(sess_iiopURLContext.java:242)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at SimpleQueueSender.main(SimpleQueueSender.java:152)**********************************************
Last, from the %J2EE_HOME%\lib\classes\jndi.properties:
java.naming.factory.initial=com.sun.enterprise.naming.SerialInitContextFactory
java.naming.factory.url.pkgs=com.sun.enterprise.naming
The weird thing is that when I remove %J2EE_HOME%\lib\j2ee.jar from the classpath, the lookup works fine again but, of course, I can't use the jms classes.
From the "Unknown service" message, I presume that the problem is related to the service provider and/or something with the environment properties.
PLEASE ANY HELP!!
Thanks.

This seems weird enough for bringing to the attention of the JNDI technical team.
If you have not already done so, you might want to send this message directly to them at [email protected]
There seems to be some incompatibility between Oracle classes and J2EE 1.3 classes. As you have pointed out, in some service provider classe(s).

Javax.naming.NamingException. Root exception is java.lang.NoSuchMethodError

I am using WLS5.1 inside visualage environment. I am trying to run
a Simple EJB which connects to the database and executes two simple
queries. The client code is as shown below:
try{
Context ic = getInitialContext();
System.out.println("Initial Context created......"); java.lang.Object
objref = ic.lookup("simpleBean.AtmHome"); System.out.println("objref
created......");
AtmHome home = (AtmHome) PortableRemoteObject.narrow(objref, AtmHome.class);
System.out.println("home created......");
Atm atm = home.create();
System.out.println("atm created......");
atm.transfer(8, 9, 100000);
catch (NamingException ne)
ne.printStackTrace(System.out);
finally {
     try {
          ic.close();
          System.out.println("Closed the connection");
     catch (Exception e) {
          System.out.println("Exception while closing context....." );
The above code executes fine for the first time but second time
it throws an exception "javax.naming.NamingException.
Root exception is java.lang.NoSuchMethodError"
javax.naming.NamingException. Root exception is java.lang.NoSuchMethodError
     java.lang.Throwable()
     java.lang.Error()
     java.lang.LinkageError()
     java.lang.IncompatibleClassChangeError()
     java.lang.NoSuchMethodError()
     void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
     void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
     javax.naming.NameImpl(java.util.Properties)
     javax.naming.CompositeName()
     weblogic.jndi.toolkit.NormalName(java.lang.String, javax.naming.NameParser)
     weblogic.jndi.toolkit.NormalName weblogic.jndi.toolkit.BasicWLContext.normalizeName(java.lang.String)
     java.lang.Object weblogic.jndi.toolkit.BasicWLContext.lookup(java.lang.String)
     weblogic.rmi.extensions.OutgoingResponse weblogic.jndi.toolkit.BasicWLContext_WLSkel.invoke(weblogic.rmi.extensions.ServerObjectReference,
int, weblogic.rmi.extensions.IncomingRequest, weblogic.rmi.extensions.OutgoingResponse)
     java.lang.Throwable weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(int,
weblogic.rmi.extensions.IncomingRequest)
     void weblogic.rmi.extensions.BasicRequestHandler.handleRequest(weblogic.rmi.extensions.IncomingRequest)
     void weblogic.rmi.internal.BasicExecuteRequest.execute(weblogic.kernel.ExecuteThread)
     void weblogic.kernel.ExecuteThread.run()
--------------- nested within: ------------------
weblogic.rmi.ServerError: A RemoteException occurred in the server
method
- with nested exception:
[java.lang.NoSuchMethodError:
Start server side stack trace:
java.lang.NoSuchMethodError
     java.lang.Throwable()
     java.lang.Error()
     java.lang.LinkageError()
     java.lang.IncompatibleClassChangeError()
     java.lang.NoSuchMethodError()
     void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
     void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
     javax.naming.NameImpl(java.util.Properties)
     javax.naming.CompositeName()
     weblogic.jndi.toolkit.NormalName(java.lang.String, javax.naming.NameParser)
     weblogic.jndi.toolkit.NormalName weblogic.jndi.toolkit.BasicWLContext.normalizeName(java.lang.String)
     java.lang.Object weblogic.jndi.toolkit.BasicWLContext.lookup(java.lang.String)
     weblogic.rmi.extensions.OutgoingResponse weblogic.jndi.toolkit.BasicWLContext_WLSkel.invoke(weblogic.rmi.extensions.ServerObjectReference,
int, weblogic.rmi.extensions.IncomingRequest, weblogic.rmi.extensions.OutgoingResponse)
     java.lang.Throwable weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(int,
weblogic.rmi.extensions.IncomingRequest)
     void weblogic.rmi.extensions.BasicRequestHandler.handleRequest(weblogic.rmi.extensions.IncomingRequest)
     void weblogic.rmi.internal.BasicExecuteRequest.execute(weblogic.kernel.ExecuteThread)
     void weblogic.kernel.ExecuteThread.run()
End server side stack trace
     weblogic.rmi.extensions.WRMIInputStream weblogic.rmi.extensions.AbstractRequest.sendReceive()
     java.lang.Object weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(java.lang.String)
     java.lang.Object weblogic.jndi.toolkit.WLContextStub.lookup(java.lang.String)
     java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
     void simpleBean.AtmClient.main(java.lang.String [])
NamingException is caught....
I found out that it hangs at lookup function in the above code.
Please let me know if I am missing any environment settings.
Thanks
Shailaja

This problem is solved after installing service pack 8 for weblogic
5.1
-shailaja
"shailaja" <[email protected]> wrote:
>
I am using WLS5.1 inside visualage environment. I am trying
to run
a Simple EJB which connects to the database and executes
two simple
queries. The client code is as shown below:
try{
Context ic = getInitialContext();
System.out.println("Initial Context created......"); java.lang.Object
objref = ic.lookup("simpleBean.AtmHome"); System.out.println("objref
created......");
AtmHome home = (AtmHome) PortableRemoteObject.narrow(objref,
AtmHome.class);
System.out.println("home created......");
Atm atm = home.create();
System.out.println("atm created......");
atm.transfer(8, 9, 100000);
catch (NamingException ne)
ne.printStackTrace(System.out);
finally {
     try {
          ic.close();
          System.out.println("Closed the connection");
     catch (Exception e) {
          System.out.println("Exception while closing context....."
The above code executes fine for the first time but second
time
it throws an exception "javax.naming.NamingException.
Root exception is java.lang.NoSuchMethodError"
javax.naming.NamingException. Root exception is java.lang.NoSuchMethodError
     java.lang.Throwable()
     java.lang.Error()
     java.lang.LinkageError()
     java.lang.IncompatibleClassChangeError()
     java.lang.NoSuchMethodError()
     void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
     void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
     javax.naming.NameImpl(java.util.Properties)
     javax.naming.CompositeName()
     weblogic.jndi.toolkit.NormalName(java.lang.String, javax.naming.NameParser)
     weblogic.jndi.toolkit.NormalName weblogic.jndi.toolkit.BasicWLContext.normalizeName(java.lang.String)
     java.lang.Object weblogic.jndi.toolkit.BasicWLContext.lookup(java.lang.String)
     weblogic.rmi.extensions.OutgoingResponse weblogic.jndi.toolkit.BasicWLContext_WLSkel.invoke(weblogic.rmi.extensions.ServerObjectReference,
int, weblogic.rmi.extensions.IncomingRequest, weblogic.rmi.extensions.OutgoingResponse)
     java.lang.Throwable weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(int,
weblogic.rmi.extensions.IncomingRequest)
     void weblogic.rmi.extensions.BasicRequestHandler.handleRequest(weblogic.rmi.extensions.IncomingRequest)
     void weblogic.rmi.internal.BasicExecuteRequest.execute(weblogic.kernel.ExecuteThread)
     void weblogic.kernel.ExecuteThread.run()
--------------- nested within: ------------------
weblogic.rmi.ServerError: A RemoteException occurred in
the server
method
- with nested exception:
[java.lang.NoSuchMethodError:
Start server side stack trace:
java.lang.NoSuchMethodError
     java.lang.Throwable()
     java.lang.Error()
     java.lang.LinkageError()
     java.lang.IncompatibleClassChangeError()
     java.lang.NoSuchMethodError()
     void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
     void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
     javax.naming.NameImpl(java.util.Properties)
     javax.naming.CompositeName()
     weblogic.jndi.toolkit.NormalName(java.lang.String, javax.naming.NameParser)
     weblogic.jndi.toolkit.NormalName weblogic.jndi.toolkit.BasicWLContext.normalizeName(java.lang.String)
     java.lang.Object weblogic.jndi.toolkit.BasicWLContext.lookup(java.lang.String)
     weblogic.rmi.extensions.OutgoingResponse weblogic.jndi.toolkit.BasicWLContext_WLSkel.invoke(weblogic.rmi.extensions.ServerObjectReference,
int, weblogic.rmi.extensions.IncomingRequest, weblogic.rmi.extensions.OutgoingResponse)
     java.lang.Throwable weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(int,
weblogic.rmi.extensions.IncomingRequest)
     void weblogic.rmi.extensions.BasicRequestHandler.handleRequest(weblogic.rmi.extensions.IncomingRequest)
     void weblogic.rmi.internal.BasicExecuteRequest.execute(weblogic.kernel.ExecuteThread)
     void weblogic.kernel.ExecuteThread.run()
End server side stack trace
     weblogic.rmi.extensions.WRMIInputStream weblogic.rmi.extensions.AbstractRequest.sendReceive()
     java.lang.Object weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(java.lang.String)
     java.lang.Object weblogic.jndi.toolkit.WLContextStub.lookup(java.lang.String)
     java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
     void simpleBean.AtmClient.main(java.lang.String [])
NamingException is caught....
I found out that it hangs at lookup function in the above
code.
Please let me know if I am missing any environment settings.
Thanks
Shailaja

JNDI Lookup of ConnectionFactory fails from inside Glassfish application

This may very well end up being a glassfish specific question.
I've got a stand-alone WAR using JSF, where I have a backing bean use some helper objects that will send a JMS message. When this WAR is running from inside of Glassfish, it fails to do the lookup of the ConnectionFactory.
The application pulls the Queue JNDI and the Provider URL from a database, and uses a env Hashtable to do the JNDI InitialContext (which succeeds.) Using this Context, the ConnectionFactory lookup fails.
The remote server in this instance is WebLogic 9.2 (the JNDI is publically available with no user authentication, verified with a JMS developer tool we use internally.)
Here's the stacktrace...
2007-10-15 19:48:04,514 ERROR [net.acadiasoft.shared.jms.util.JMSSenderHelper:130] NamingException: messageFactory not found
javax.naming.NameNotFoundException: messageFactory not found
at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:216)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:188)
at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:74)
at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:111)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:339)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at net.acadiasoft.shared.jms.util.JMSSenderHelper.getConnectionFactory(JMSSenderHelper.java:128)
at net.acadiasoft.shared.jms.util.JMSSenderHelper.init(JMSSenderHelper.java:58)
at net.acadiasoft.shared.jms.util.JMSSenderHelper.<init>(JMSSenderHelper.java:36)
at net.acadiasoft.web.shared.jms.util.AdminJmsHelper.<init>(AdminJmsHelper.java:19)
at net.acadiasoft.web.server.pages.SchedulerBackingBean.deleteJobs(SchedulerBackingBean.java:75)

I've found the problem, and it's something I simply overlooked. I don't know why I didnt realize, but i was setting the java.naming.factory.initial env variable to what Glassfish uses, not WebLogic.

NamingException initialContext.lookup

Similar Messages

Maybe you are looking for