Solved

Websphere Remote Jndi Lookup - ClassCastException javax.naming.Reference cannot be cast to javax.jms.QueueConnectionFactory

Posted on 2009-07-01
6
7,706 Views
Last Modified: 2013-12-11
Hi,

Someone has asked a similar question to this previously, but they didn't really reveal how they solved it.

I'm doing a Remote JNDI Lookup for a QueueConnectionFactory. The QueueConnectionFactory and the ear I'm working with are deployed on Websphere. Im also using Websphere MQ. I'm pretty sure my InitialContext is set up correctly. It retrieves my queues without problem.

However, when I do a lookup of the QueueConnectionFactory, my attempt to cast the object returns a ClassCastException.

Exception in thread "main" java.lang.ClassCastException: javax.naming.Reference cannot be cast to javax.jms.QueueConnectionFactory at queue.RemoteExecutionServerRunner.setUpWASQueue(RemoteExecutionServerRunner.java:101)
at queue.ExecutionServerTest.main(ExecutionServerTest.java:23)

Googling around leads me to things its something to do with the classpath.

Any help would be greatly appreciated.

Thank you
jndiContext = getJndiContext();
 
connectionFactory = (QueueConnectionFactory)   jndiContext.lookup("jms/BRESQueueConnectionFactory");
sendQueue = (Queue) jndiContext.lookup("queue/BRESQueueIn");
replyQueue = (Queue) jndiContext.lookup("queue/BRESQueueOut");
 
 
private Context getJndiContext() {
		
	Context ctx = null;
		
	try {
		Properties properties = new Properties();
		properties.setProperty(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
		properties.setProperty(Context.PROVIDER_URL, "corbaloc:iiop:idassysapp2:2811");
		properties.setProperty(Context.URL_PKG_PREFIXES,"com.ibm.ws.naming");
		
		properties.setProperty("com.ibm.CORBA.ORBInit", "com.ibm.ws.sib.client.ORB");
		
		ctx = new InitialContext(properties);
			
	} catch (NamingException e) {
		e.printStackTrace();
	}
		
	return ctx;
}

Open in new window

0
Comment
Question by:fuzzydunlop
  • 3
  • 3
6 Comments
 
LVL 4

Assisted Solution

by:Tuno85
Tuno85 earned 500 total points
ID: 24752614
I would suggest using InitialContext as return type.

Make sure you have the IBM JDK libraries on the classpath.

And eventually check this link:

http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14008677
0
 

Author Comment

by:fuzzydunlop
ID: 24752657
Hi Tuno,

Thanks for the response.

I have three IBM jars on my application build path.

sibc.jms.jar
sibc.jndi.jar
sibc.orb.jar

Are these enough? I've tried adding all the jars from my Websphere 6 installation directory to the build path but that doesn't seem to solve it.

Thanks
0
 
LVL 4

Assisted Solution

by:Tuno85
Tuno85 earned 500 total points
ID: 24752933
How do you execute this. On the server or unit test?

Do you use the IBM JVM?

Did you try InitialContext as return type?
0
3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

 

Author Comment

by:fuzzydunlop
ID: 24753720
I've written a standalone application, accessing Websphere remotely. My class is executed within a main method.

I did try the InitialContext as a return type, the error still occurs. I'm using the Sun JVM.
0
 
LVL 4

Accepted Solution

by:
Tuno85 earned 500 total points
ID: 24760591
I am looking at the similar code I am using. Nothing wrong. Should be working.

Try using the IBM JVM, maybe that this works. Although same mechanism should be working with Sun JVM.

I was also looking around and also found this:

http://forums.sun.com/thread.jspa?threadID=5225537
0
 

Author Comment

by:fuzzydunlop
ID: 24761175
Hi,

Thanks for the link. I have allowed access to the Internal Server Classes on the Websphere Application Server.

I have managed to figure it out. It's not a very elegant solution but it works. This probably ties in with using the IBM JVM, but I imported a host of Jars from the Application Server into my client application. The directories were:

${WAS_HOME}\AppServer\lib
${WAS_HOME}\AppServer\plugins

Having these jars on my application classpath seemed to fix the problem.

Hope this helps anyone who comes across this problem. Thanks for the help Tuno.
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
for loop with Set 4 49
maven project clean install and build and adding as war web plugin 4 55
pairs challenge 5 76
eclipse buid path vs tomcat lib path 10 22
Configure Web Service (server application) I. Configure security for Web Services methods First, we need to protect Session bean which implements the service: 1. Open EJB deployment descriptor (ejb-jar.xml) in the EJB project that contains you…
This article is about some of the basic and important steps to be used to improve the performance in web-sphere commerce application development. 1) Always leverage the Dyna-caching facility provided by the product 2) Remove the unwanted code …
The viewer will learn how to implement Singleton Design Pattern in Java.
This tutorial covers a practical example of lazy loading technique and early loading technique in a Singleton Design Pattern.

813 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now