Wrong target. class org.jboss.jms.client.delegate.ClientConn

[pierods]

I get an error when trying to retrieve a remote connection:

Properties prop = new Properties();
prop.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
prop.put(Context.PROVIDER_URL, "jnp://*****:64115");
prop.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");


Context jndiContext = new InitialContext(prop);

ConnectionFactory factory = (ConnectionFactory)

jndiContext.lookup("java:/ConnectionFactory");
Queue queue = (Queue) jndiContext.lookup("java:/queue/A");

Connection connection = factory.createConnection();

On createConnection() I get:

Exception in thread "main" java.lang.IllegalArgumentException: Wrong target. class org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate for public org.jboss.jms.delegate.CreateConnectionResult org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(java.lang.String,java.lang.String,int) throws javax.jms.JMSException
at org.jboss.aop.joinpoint.MethodInvocation.handleErrors(MethodInvocation.java:141)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:116)
at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:81)
at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:87)
at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:82)
at simple.JMSLauncher.(JMSLauncher.java:55)
at simple.JMSLauncher.main(JMSLauncher.java:65)

[gaohoward]

Please give the exact version of JBM being used. Thanks.

[peterj]

Are you sure that the JAR files in your client's classpath are those from the client directory of the server?

[anilit99]

Not quite helpful info.

But I got a similar error sometime back. I re arranged the jar files here and there and it got resolved magically. Just to make you feel better - you are not alone in this whole jar conflicts thing. I can vividly recall the countless nights resolving the correct jar files, just because some other version of the jar is lying somewhere.

[pierods]

I actually found out the problem, I was using the wrong jar version.

but then another problem arose: how do i recover with maven this file, given that it has dots in the directory name:

http://repository.jboss.com/jboss/messaging/1.4.0.SP3/lib/jboss-messaging-client.jar

If I do:

<dependency>
 <groupId>org.jboss.client</groupId>
 <artifactId>jbossall-client</artifactId>
 <version>4.0.5.GA</version>
 <scope>compile</scope>
</dependency>

then maven tries for

http://repository.jboss.com/jboss/messaging-client/1/4/0-SP3/lib/jboss-messaging-client/1.4.0-SP3/jboss-mesaging-client-1.4.0-SP3.jar

How do I do that?