Standalone JMS client in SJS App Server 8.0

Question

Hi
I am trying to retrieve a message from a JMS queue from astandalone client.
The code the client uses to lookup JMS resources is:
try
          /* Create the object of InitialContext interface */
Properties env = new Properties( );
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
env.put(Context.PROVIDER_URL,"iiop://localhost:3700");
     jndiContext = new InitialContext(env);
          /* Find the connection factory object */
     QConnectionFactory = (QueueConnectionFactory)jndiContext.lookup("jms/QConnectionFactory");
     /* Find the queue */      
          queue = (Queue) jndiContext.lookup("jms/Queue");
catch (NamingException e)
     System.out.println("Error: " + e.toString());
The code throws the following exception:
Error: javax.naming.NameNotFoundException [Root exception is org.omg.CosNaming.N
amingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
Exception in thread "main" java.lang.NullPointerException
at QReceiver.main(QReceiver.java:51)
What might be the problem? Pls help. The code works fine when executed as an Application client of SJS Appserver without using the JNDI Context part.
Thanks in advance
JLRocky

Answer 1

Also have a problem similar to this. I have found that
1. JMS between beans on the same server work fine
2. JMS between standalone client and server work fine if you start the bundled imq as a standalone message server
3. If you are using the Appserver then standalones cannont connect, but it you are using the imq beans cannot connect.
so i haven't had time to try this yet but my possible solution is:
configure the app server to use an external JMS server (its in the admin console some place) make the external server to be an imq running as a standalone, hopefully it can be started on localhost with out any port changes.
I think rather than bundling the two so both could be used they embeded the imq in the appserver and shielded it from outside comminication