aspose file tools*
The moose likes Websphere and the fly likes Problem looking up remote JMS queue from standalone app  Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Problem looking up remote JMS queue from standalone app  " Watch "Problem looking up remote JMS queue from standalone app  " New topic
Author

Problem looking up remote JMS queue from standalone app

Benson Fung
Ranch Hand

Joined: Apr 10, 2003
Posts: 207
Hi,

I've written a standalone Java application (JDK1.4) to access Websphere (V6) embedded JMS queue on WinXP.

Here's the command line to run:
>launchClient.bat JmsApplClientEAR.ear -CCBootstrapPort=9953 -CCBootstrapHost=130.22.112.143

I want to lookup multiple remote JMS queues from 3 machines.

It is OK to lookup and read the local websphere JMS queue. But I can't read a queue that is located in another host, e.g. 130.22.112.222.

Here's the code segment for jndi lookup:
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
p.put(Context.PROVIDER_URL, "iiop://130.22.112.222:9953");
p.put("java.naming.provider.url", "iiop://130.22.112.222:9953");
context = new InitialContext(p);
//then lookup connection factory...

When I run the application, I cannot read the message in 130.22.112.222. There is no error, so I don't know how to trace the problem. Would you please help?

130.22.112.143 settings:
bus name: TestBus
Connection factory: jms/TestQCF1
Queue: jms/TestQ1

130.22.112.222 settings:
bus name: TestBus
Connection factory: jms/TestQCF2
Queue: jms/TestQ2


Regards
Benson
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Problem looking up remote JMS queue from standalone app
 
Similar Threads
Jboss5.1 integrating with remote ActiveMQ
Session facade
about jndi lookup problem
Failed to initialize the ORB using websphere.
JNDI lookup for JMS...URGENT!