JMS-JNDI-QConnectionFactory lookup-WSAD 5.1

Hi
I am trying to create a stand-alone client to Websphere MQ JMS in WSAD 5 using the following simple code:
java.util.Properties prop = new java.util.Properties();
               prop.put(
                    javax.naming.Context.INITIAL_CONTEXT_FACTORY,
                    "com.ibm.websphere.naming.WsnInitialContextFactory");
               prop.put(javax.naming.Context.PROVIDER_URL, "iiop://localhost:2809/");
javax.naming.Context ctx = new javax.naming.InitialContext(prop);
System.out.println("Got the initial context");
System.out.println("Starting object lookup");
javax.jms.QueueConnectionFactory factory = (javax.jms.QueueConnectionFactory)ctx.lookup("E2ELocalQCF");
//Object obj = ctx.lookup("E2ELocalQCF"); (If uncommented,this works fine!)
It fails while casting to QueueConnectionFactory (context is fine).
Got the initial context
Starting object lookup
java.lang.ClassCastException: javax.naming.Reference
I include all the required JARS from base_v5/lib and base_v5/mqjms/java/lib and the implFactory.jar from wstools/eclipse/plugin folder and the java/javac from base_v5\java\bin.
The same error appears incase I do a look up for Queue object.
Has any of you come across this problem.
Any help would be much appreciated.
Sincerely
Rajneesh
ForwardSourceID:NT000181A6

this is classpath issue try with this classpath it will work...
set classpath=D:\Program Files\WebSphere\AppServer\lib\j2ee.jar;D:\Program Files\WebSphere\AppServer\lib\naming.jar;D:\Program Files\WebSphere\AppServer\lib\namingclient.jar;D:\Program Files\WebSphere\AppServer\lib\ecutils.jar;D:\Program Files\WebSphere\AppServer\lib\messagingImpl.jar;D:\Program Files\WebSphere\AppServer\lib\messaging.jar;D:\Program Files\WebSphere\AppServer\properties;D:\Program Files\ibm\WebSphere MQ\Java\lib\com.ibm.mqjms.jar;D:\Program Files\ibm\WebSphere MQ\Java\lib\jndi.jar;D:\Program Files\ibm\WebSphere MQ\Java\lib\jms.jar;D:\Program Files\ibm\WebSphere MQ\Java\lib\com.ibm.mq.jar;D:\Program Files\ibm\WebSphere MQ\Java\lib;D:\Program Files\WebSphere\AppServer\java\jre\lib\ext\ibmorb.jar;
set path=D:\Program Files\WebSphere\AppServer\java\bin;

Similar Messages

JMS - JNDI lookup Problem

Hi,
I am using OC4J 10g (10.1.3.1.0).
I have a standalone JMS application which tries to get QueueConnectionFactory. The application and the OC4J reside in the same machine.
This is what my code looks like
Properties parm = new Properties();
parm.setProperty("java.naming.factory.initial",
"com.evermind.server.rmi.RMIInitialContextFactory");
parm.setProperty("java.naming.provider.url",
"opmn:ormi://localhost");
parm.setProperty("java.naming.security.principal", "oc4jadmin");
parm.setProperty("java.naming.security.credentials", "oc4jadmin");
jndiContext = new InitialContext(parm);
queueConnectionFactory = (QueueConnectionFactory)jndiContext.lookup("jms/MainQueueConnectionFactory");
And my JMS.xml entry
<jms-server port="9127">
<queue-connection-factory name="MainQueueConnectionFactory" host="localhost" port="9127" password="oc4jadmin" username="oc4jadmin" location="jms/MainQueueConnectionFactory"/>
<queue name="MainQueue" location="jms/MainQueue"/>
</jms-server>
When i run my standalone, i get this exception
WARNING: Error in obtaining server list from OPMN on host localhost:6003. Please verify that OPMN is running.
JNDI API lookup failed: javax.naming.NameNotFoundException: jms/MainQueueConnectionFactory not found
Any help with this would be appreciated.
Cheers,
Sumanth

Just a guess off the top of my head but if you are using this provider URL
opmn:ormi://localhostThen you need to augment it with the OC4J instance name.
opmn:ormi://localhost:homeYou may also need to check OPMN and see what request port it is using -- do an
$ORACLE_HOME/opmn/bin/opmnctl status -portAnd then use that port in your URL as follows
opmn:ormi://localhost:<port>:homeIf it comes back as 6003 then that is the default port and thus does not need to be provided.
-steve-

EJB3 - where to perform JMS JNDI lookups?

Hi, I was reading about how the WebLogic jms wrappers work at:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/jms/j2ee.html
and noticed this section:
"The JNDI lookups of the Connection Factory and Destination objects can be expensive in terms of performance. This is particularly true if the Destination object points to a Foreign JMS Destination MBean, and therefore, is a lookup on a non-local JNDI provider.". I am using Sonic MQ as my foreign JMS Provider hence this is of particular interest to me.
The document recommends caching these lookups in the ejbCreate() method of an EJB. I'm new to EJB3 but notice there is no concept of an ejbCreate() method there so where should I cache the lookups and how do I ensure they get re-looked up in the case of a connection failure?
Many thanks
Mandy

Thanks very much Tom, this helps a lot. I think my confusion lay in the fact that this document talks about caching the JNDI lookups in the ejbCreate and gives the example PoolTestBean.java which uses EJB2 style code. I've made your recommended changes to my code, would you mind just casting your eye over to see if looks ok? I have chosen to cache on create of the bean rather than on first invocation as I want clients to fail on startup rather than during their processing.
Sorry about code layout, not sure how to use HTML in posts to make it verbatim..
@Stateless
@TransactionAttribute(NEVER)
//@ExcludeDefaultInterceptors
public class ServiceWrapperBean implements ServiceWrapper {
     // injected resources
     @Resource
     private SessionContext sctx; // inject the bean context
     @Resource(name = "sonicConnectionFactory", mappedName = "sonic.connFactory", shareable = true)
     private ConnectionFactory connectionFactory;
     @Resource(name = "LegacyAccessIn", mappedName = "queue/LegacyIn", shareable = true)
     private Destination sendQueue;
     public void sendMessage(String msg) {
          if (connectionFactory == null)
               connectionFactory = (javax.jms.ConnectionFactory) sctx
                         .lookup("sonicConnectionFactory");
          if (sendQueue == null)
               sendQueue = (javax.jms.Destination) sctx.lookup("LegacyAccessIn");
          if (msg == null)
               throw new IllegalArgumentException("object cannot be null!");
          Connection con = null;
          Session session = null;
          MessageProducer sender = null;
          try {
               con = connectionFactory.createConnection();
               session = con.createSession(true, Session.AUTO_ACKNOWLEDGE);
               sender = session.createProducer(null);
               Message message = session.createTextMessage("do stuff");
               sender.send(sendQueue, message);
          } catch (JMSException e) {
               // Invalidate the JNDI objects if there is a failure
               // this is necessary because the destination object
               // may become invalid if the destination server has
               // been shut down
               connectionFactory = null;
               sendQueue = null;
               throw new RuntimeException(e);
          } finally {
               if (con != null) {
                    try {
                         // Return JMS resources to the resource reference pool for later re-use.
                         // Closing a connection automatically also closes its sessions, etc.
                         con.close(); // also closes other objects
                    } catch (JMSException je) {
                         // ignore
     }

Question: J2SE use of JMS/JNDI

Is it possibe to JMS to communicate between main methods/threads
running in separate instance of the the Sun MicroSystem's
Java virtual machine, or is a third party program needed,
like JBoss?
May a JNDI Context lookup, with J2EE installed,
be used to lookup between Java Virtual Machines?

Zac1234 wrote:
Is it possibe to JMS to communicate between main methods/threads
running in separate instance of the the Sun MicroSystem's
Java virtual machine, and
or is a third party program needed,Are not a simple either/or choice. You can indeed use JMS in a J2SE context, without needing an app. server. But you'll still need a JMS provider. Apache ActiveMQ would be handy. Google "POJO JMS" for more info than you can shake a stick at on this subject

How to use JNDI to lookup remote EJB Home?

Hello,
I am writing a servlet to call a remote EJB on another machine.
I use JNDI to lookup remote EJBHome (not) but fail.
Any advice?
Any trick to configure application-client.xml?
Thanks!

Use com.evermind.server.rmi.RMIInitialContextFactory instead
Here an example
// EmployeeClient.java
package mypackage5;
import javax.ejb.*;
import javax.naming.*;
import javax.rmi.PortableRemoteObject;
import java.io.*;
import java.util.*;
import java.rmi.RemoteException;
import com.evermind.server.ApplicationClientInitialContextFactory;
import com.evermind.server.rmi.RMIInitialContextFactory;
* A simple client for accessing an EJB.
public class EmployeeClient
public static void main(String[] args)
System.out.println("EmployeeClient.main(): client started...");
try
* initialize JNDI context by setting factory, url and credential
* in a hashtable
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
//env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.ApplicationClientInitialContextFactory");
env.put(Context.PROVIDER_URL, "ormi://koushikm:23791/application4");
env.put(Context.SECURITY_PRINCIPAL, "admin");
env.put(Context.SECURITY_CREDENTIALS, "admin");
* or set these properties in jndi.properties
* or use container defaults if that's where client got launched from
Context context = new InitialContext(env);
* Lookup the EmployeeHome object. The reference is retrieved from the
* application-local context (java:comp/env). The variable is
* specified in the assembly descriptor (META-INF/application-client.xml).
Object homeObject =
context.lookup("HelloEJB");
System.out.println("EmployeeClient.main(): bean found...");
// Narrow the reference to EmployeeHome.
HelloEJBHome home =
(HelloEJBHome) PortableRemoteObject.narrow(homeObject,
HelloEJBHome.class);
System.out.println("EmployeeClient.main(): home narrowed...");
// Create remote object and narrow the reference to Employee.
HelloEJB remote =
(HelloEJB) PortableRemoteObject.narrow(home.create(), HelloEJB.class);
System.out.println("EmployeeClient.main(): remote created...");
String message=remote.helloWorld("SUCCESS");
System.out.println(message);
} catch(NumberFormatException e) {
System.err.println("NumberFormatException: " + e.getMessage());
} catch(RemoteException e) {
System.err.println("RemoteException: " + e.getMessage());
} catch(IOException e) {
System.err.println("IOException: " + e.getMessage());
} catch(NamingException e) {
System.err.println("NamingException: " + e.getMessage());
} catch(CreateException e) {
System.err.println("CreateException: " + e.getMessage());
Hello,
I am writing a servlet to call a remote EJB on another machine.
I use JNDI to lookup remote EJBHome (not) but fail.
Any advice?
Any trick to configure application-client.xml?
Thanks!

JMS JNDI configurtaration problem

IHAC where we are connecting PeopleSoft Integration Broker. Unfortunately PIB doesn't support LDAP for JNDI (go figure). So I have to use a .bindings file.
Problem is, when I run the HelloWorldMessageJNDI I get the following error:
Using file:///tmp/mq for Context.PROVIDER_URL
Looking up Connection Factory object with lookup name: CSoutboundQCF Connection Factory object found.
Looking up Queue object with lookup name: CSoutboundQ Failed to lookup Queue object.
Please make sure you have created the Queue object using the command:
       imqobjmgr -i add_q.props
The exception details:
javax.naming.NameNotFoundException: CSoutboundQ
       at com.sun.jndi.fscontext.RefFSContext.getObjectFromBindings(RefFSContext.java:400)
       at com.sun.jndi.fscontext.RefFSContext.lookupObject(RefFSContext.java:327)
       at com.sun.jndi.fscontext.RefFSContext.lookup(RefFSContext.java:146)
       at com.sun.jndi.fscontext.FSContext.lookup(FSContext.java:127)
       at javax.naming.InitialContext.lookup(Unknown Source)
       at HelloWorldMessageJNDI.<init>(HelloWorldMessageJNDI.java:187)
       at HelloWorldMessageJNDI.main(HelloWorldMessageJNDI.java:120)

It's looks almost as the same as my problem in web app., when I forgot wrote tags <resource-env-ref in web.xml..
e.g. web.xml
<resource-env-ref>
<resource-env-ref-name>jms/MainQueue</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>
<resource-ref>
<res-ref-name>jms/MainQueueConnectionFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
</resource-ref>
....

JNDI context lookup to SwiftMQ blocks

I have a piece of code that is trying to connect to a SwiftMQ v2 JMS server. Everything worked fine until yesterday when the following problem start happening consistently:
My program gets stuck when trying to do context lookup.
As far as I can tell, there were no code changes or SwiftMQ changes on the server where this is running (i dont have control of the machine).
Here is the part of the code:
cat.debug("routerConnect(): start");
env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, strContextFactory);
env.put(Context.PROVIDER_URL, strSMQPURL[iCurrentJMS]);
env.put(Context.SECURITY_PRINCIPAL, strSecurityPrincipal[iCurrentJMS]);
env.put(Context.SECURITY_CREDENTIALS, strSecurityCredential[iCurrentJMS]);
ctx = new InitialContext(env);
cat.debug("ctx.lookup"); ///// THIS IS THE LAST DEBUG STATEMENT PRINTED IN THE LOG
queueConnectionFactory = (QueueConnectionFactory) ctx.lookup(strConnectionFactory[iCurrentJMS]);
queue = (Queue) ctx.lookup(strQueueName[iCurrentJMS]);
ctx.close();
ctx.lookup is the last debug statement printed in the log.
Does anybody has any idea of where this problem is coming from and how to get around it?
What puzzles me most is that it just start happening with no reason ... or at least that's what it looks like!
Thank you very much for your support!
Seb

After doing the following two things, The issue is resolved.
#1:
Configure Default Server for Datasource (Web logic console --> Data Sources --> jdbc/AppsDataSource --> Targets --> select, if not default server not selected --> Save --> restart the server.)
Note:
If we don't deploy while JNDI creation then below is correct. "You can select one or more targets to deploy your new JDBC data source. If you don't select a target, the data source will be created but not deployed. You will need to deploy the data source at a later time."
#2: If The Jdeveloper is newly installed, Create a dummy UI application. & run a test.jspx page.

JNDI Destination Lookup

I have issues with my JNDI lookup . I got my context.xml outside of my webapplication . I have pasted the code below . But it was throwing NameNotFoundException .
javax.naming.NameNotFoundException: jms/Test at com.sun.jndi.fscontext.RefFSContext.getObjectFromBindings(RefFSContext.java:400)
Hashtable hashtableEnvironment = new Hashtable();
hashtableEnvironment.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.fscontext.RefFSContextFactory");
hashtableEnvironment.put(Context.PROVIDER_URL, "file:///C:/sample");
Context context = new InitialContext(hashtableEnvironment);
NamingEnumeration namingenumeration = context.listBindings("");
while (namingenumeration.hasMore()) {
Binding binding = (Binding)namingenumeration.next();
System.out.println(
binding.getName() + " is bound to " +
binding.getObject()
Destination dest = (Destination) context.lookup("jms/test");
context.close();

Which JMS provider is it (though it seems like you are using IBM MQ). You should check that bindings are correctly created if it is IBM MQ.

WEBLOGIC - JMS - JNDI

I created a new JMS Server under weblogic admin console and a queue under destinations.There was a icon sitting next to JNDI name saying the queue jndi name will not take effect until restart.I restarted many times but the error didn't go off and I couldn't bind it to the queue through my program.Any help is appreciated.

Rightnow Iam getting classcast exception when I try to look up the queue from the server. The following snippet of code causes the error,
queue = (Queue) initCtx.lookup("testQueue");
testQueue is defined in weblogic8.1 under JMS server.
Any help is appreciated.

Sun App Sever 8.1 / JNDI - datasource lookup problems

I get an error when calling the ctx.lookup function. I have the datasource and the resource set up in the server OK. I can ping successfully and view the table data. I am using NetBeans 4.1 / Sun 8.1
I have been up all night (11pm - 4:30am) trying to figure this out.
    <%
        java.sql.Connection conn = null;
        java.util.Hashtable env = new java.util.Hashtable();
        javax.naming.Context ctx ;
        javax.sql.DataSource cachedDataSource;
        try {
        env.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
        ctx = new javax.naming.InitialContext();
        cachedDataSource = (javax.sql.DataSource)ctx.lookup("jdbc/mysql");
        if (cachedDataSource == null)
            {out.println("<h2>The datasource is not getting set properly</h2>");
            conn = cachedDataSource.getConnection();}
        else
        { out.println("<h2>the datasource is not null and seems like it gets initialized.<h2>"); }
        } catch (javax.naming.NamingException ne) {}
          catch (java.sql.SQLException se) {}
        env = null;
        ctx = null;
        conn.close();
        conn = null;
        cachedDataSource = null;
    %>

RTFM
http://docs.sun.com/app/docs/doc/819-0079
The resource lookup in the application code looks like this:
InitialContext ic = new InitialContext();
String dsName = "java:comp/env/jdbc/HelloDbDs";
DataSource ds = (javax.sql.DataSource)ic.lookup(dsName);
Connection connection = ds.getConnection();
The resource being queried is listed in the res-ref-name element of the web.xml file as follows:
<resource-ref>
<description>DataSource Reference</description>
<res-ref-name>jdbc/HelloDbDs</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
The resource-ref section in a Sun Java System specific deployment descriptor, for example sun-web.xml, maps the res-ref-name (the name being queried in the application code) to the JNDI name of the JDBC resource. The JNDI name is the same as the name of the JDBC resource as defined in the resource file when the resource is created.
<resource-ref>
<res-ref-name>jdbc/HelloDbDs</res-ref-name>
<jndi-name>jdbc/HelloDbDataSource</jndi-name>

JNDI EJB Lookup fails on Remote Server

Hi,
I am having two different domain (domain1,domain2) respectvely. My ABC.ear j2eee application is deployed on domain2 and its iiop port is 33703.In domain1 i have xyz.war (web application) and it's IIOP port is 3700 .In xyz.war i am having CallEJB.jsp file.In this Jsp file i want to lookup an EJB Service called PaymentEJB(JNDI Name is ejb/PaymentEJB).
The code is below
InitialContext context=new InitialContext();
Object objRef=context.lookup("corbaname:iiop:andaman:33703#ejb/PaymentEJB");
I am getting the following error.
[#|2005-12-14T16:42:03.422+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.corba._DEFAULT_.rpc.transport|_ThreadID=11;|"IOP00410216: (COMM_FAILURE) Unable to create IIOP listener on the specified host/port: all interfaces/3700"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2661)
My doubt is
1.While starting domain1 and domain2 iiop listeners are started on the port 3700 and 33703.in that case why EJB lookup tries to create listener on one more time.
2.I am looking the 33703 port only.but it tries to create port on 3700 why?
3.It was working till JES2005Q1.Is there any patch i need to install? or i need to change anything in my code.
I am frustrated with this error for past one week.I will be happy if some body will give me the peace of mind(thru some solution).

http://docs.sun.com/source/819-0079/dgjndi.html
This might help.

JMS/JNDI introducing white spaces

Hi.
I am having trouble getting the example at http://technet.oracle.com/docs/tech/java/oc4j/htdocs/OC4JExample.html to work. I finally started the client program that uses JMS with java Main instead of java -Djava.naming.security.credentials=<admin password> Main
Then I saw in a popup box that somewhere along the way there has been appended a single whitespace character after the login name "admin" was spelled "admin " and "ormi://localhost" was spelled "ormi://localhost ". My jndi.properties file did not include white spaces. Anyone seen this before?
-Christer

Hi
          Please find my answers below:
          Q1:
          It depends how you configured the JMSSevers.
          If both the JMSServers are targeted to the same MigratableTarget, then you do the migration only once, that will move both of them to the new active server.
          If not, you have to perform the migration once for each MT.
          Q2:
          No, you dont have to start the Managed Server II, unless otherwise you wanted it to be readily available for the migration next time.
          Q3:
          You can just repeat the migration process by specifying the destination as Maganged Server-I this time. You dont need change the configuration for this, since the MT, shall already have the Candidate servers M1 and M2 and both JMSServers are targeted to MT.
          Q4:
          Yes, as long as the CF is targeted to the cluster, your connection is valid. But your destinations references will become invalid after migration, so you have to have some logic in the exception listeners to reconnect again.
          Hope this helps.

DataSource-class pool-JNDI-bind-lookup

Hi,
I am a beginner in this subject and it is confused. I read that
the best way to use the connections is from a DataSource. There
are 2 ways to configure it:
1- From the data-source.xml file
2- Or using InitialContext, Context and bind method from a java
program loaded in the startup.
If so, which one is better?
On the other hand, there are some classes I can use, for
instance:
1- OracleConnectionCacheImpl
2- OracleConnectionPoolDataSource
etc.
which one is better?
Thank you very much for any comment.
Andres.

Hi:
upon further research, i find that the data
that was used in State class at binding does not change on any update,
like via foll -
State s = (State)ic.lookup(JNDINAME);
s.addHashtableEntry (key, val); or
s.setDesc ("new desc");
next time i lookup State class the hashtable entry is missing and desc is
old and not "new desc".
any help appreciated.
thanks
rajans
Rajan Sadasivan wrote:
Hi:
I am using jdk1.3, weblogic6.0
I am binding a state class like ->
public class State implements Serializable {
private String desc;
private Hashtable sessions;
onto the JNDI tree. Binding is done like initialCxt.bind (name,
_state);
and state's sessions has one entry in it and state's desc is set.
I then use another client to do _initialCxt.lookup (name) on same
weblogic JVM.
The _state object is returned with correct value of desc; but the
sessions
hashtable is empty and the single entry is gone. I do see also the the
State's finialize () method is called.
Can anyone explain why i am losing hashtable information ?
How do I make this work in weblogic jndi with hashtable info ?
thanks
rajans

JNDI replication\lookup problems

          Hi,
          We have a WL5.1 SP12 cluster that until today consisted of 2 Solaris boxes running
          8 WL instances on the 2.6 OS.
          Today we attempted to add a third Solaris box, running 2 SP12 WL instances on the
          2.8 OS. These two new instances were identical to the other 8 in all respects apart
          from one ejb jar which they did not deploy (because of Solaris 2.8\JNI\JDK1.3.1 incompatiblilities).
          We figured that these new JVM could lookup this bean via the clustered JNDI and execute
          on one of the original 8 JVMs, so we did not deploy on these new servers. This worked
          fine on test (a 3 way cluster, on one box running Solaris 2.8 and SP10).
          However when we cut the new box in this morning we got javax.naming.NameNotFoundExceptions
          from the new JVMs.
          These new JVMs apeared to start fine, and everything looked as it should on the console,
          but still the error.
          so :
          what could it be :
          OS related - a clustering spanning 2.6 and 2.8 OSs
          SP 12 related ?
          Anybody encountered anything like this before ?
          Thanks in advance.
          Justin


          Yes, the EJB classes are in the server classpath.
          I assumed that JNDI replication occured as a resulting of enabling clustering.
          "Sabha" <[email protected]> wrote:
          >Are the ejb home/remote interfaces in the server classpath of the 2 newer
          >JVMs? Is jndi replication turned off?
          >
          >-Sabha
          >
          >"Justin" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Hi,
          >>
          >> We have a WL5.1 SP12 cluster that until today consisted of 2 Solaris boxes
          >running
          >> 8 WL instances on the 2.6 OS.
          >>
          >> Today we attempted to add a third Solaris box, running 2 SP12 WL instances
          >on the
          >> 2.8 OS. These two new instances were identical to the other 8 in all
          >respects apart
          >> from one ejb jar which they did not deploy (because of Solaris
          >2.8\JNI\JDK1.3.1 incompatiblilities).
          >> We figured that these new JVM could lookup this bean via the clustered
          >JNDI and execute
          >> on one of the original 8 JVMs, so we did not deploy on these new servers.
          >This worked
          >> fine on test (a 3 way cluster, on one box running Solaris 2.8 and SP10).
          >>
          >> However when we cut the new box in this morning we got
          >javax.naming.NameNotFoundExceptions
          >> from the new JVMs.
          >>
          >> These new JVMs apeared to start fine, and everything looked as it should
          >on the console,
          >> but still the error.
          >>
          >> so :
          >>
          >> what could it be :
          >>
          >> OS related - a clustering spanning 2.6 and 2.8 OSs
          >> SP 12 related ?
          >>
          >> Anybody encountered anything like this before ?
          >>
          >> Thanks in advance.
          >>
          >> Justin
          >>
          >>
          >>
          >
          >

Figuring out local JNDI names with WSAD

I have a cmp bean, with JNDI name "ejb/ebmusic2/AlbumLocalHome".
when i try to look it up from another bean it fails. i also tried to add
the prefix "java:comp/env" as i saw being done in IBM redbook in a
similar circumstances, and yet the JNDI client fails to discover everything
that is after the "java" prefix.
any thoughts ? thanks for your help.

try "local:ejb/ejb/"
so your code could say:
private String JNDI_LOCAL_PREFIX = "local:ejb/ejb/";

JMS-JNDI-QConnectionFactory lookup-WSAD 5.1

Similar Messages

Maybe you are looking for