Bug 1042746 - EAP 5 client can't create connection on EAP 6's connection factory
Summary: EAP 5 client can't create connection on EAP 6's connection factory
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Clebert Suconic
QA Contact: Miroslav Novak
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-13 09:24 UTC by Miroslav Novak
Modified: 2014-04-11 01:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-13 14:43:19 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Issue Tracker JBPAPP-10925 Critical Closed EAP 5 client can't create connection on EAP 6's connection factory 2014-04-11 06:24:19 UTC

Description Miroslav Novak 2013-12-13 09:24:07 UTC
When standalone JMS client with EAP 5 client libraries lookups CF from EAP 6 server then it can't create connection on it. It fails with:

Exception in thread "main" java.lang.NoClassDefFoundError: org/hornetq/core/server/HornetQComponent
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
        at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
        at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
        at org.hornetq.core.remoting.impl.invm.InVMConnectorFactory.createConnector(InVMConnectorFactory.java:40)
        at org.hornetq.core.client.impl.ClientSessionFactoryImpl.getConnection(ClientSessionFactoryImpl.java:1127)
        at org.hornetq.core.client.impl.ClientSessionFactoryImpl.getConnectionWithRetry(ClientSessionFactoryImpl.java:1001)
        at org.hornetq.core.client.impl.ClientSessionFactoryImpl.connect(ClientSessionFactoryImpl.java:225)
        at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:767)
        at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:601)
        at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:119)
        at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:114)
        at org.jboss.jms.client.TestConsumerSimple.main(TestConsumerSimple.java:51)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
Caused by: java.lang.ClassNotFoundException: org.hornetq.core.server.HornetQComponent
        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
        ... 26 more

This is not affecting use cases which are using MDB/EJBs with (local) JmsXA connection factory but there is another customer who needs standalone JMS clients with EAP 5 libraries to connect to EAP 6 server.

Note there is new module for EAP 6 which allows EAP 5 client to do JNDI lookup to EAP 6. More info: https://mojo.redhat.com/docs/DOC-929745

Comment 1 JBoss JIRA Server 2013-12-13 14:43:02 UTC
Miroslav Novak <mnovak@redhat.com> updated the status of jira JBPAPP-10925 to Closed

Comment 2 Miroslav Novak 2013-12-13 14:43:19 UTC
This was caused by my bad configuration of EAP 6 server. Closing.

Comment 3 JBoss JIRA Server 2014-04-11 01:05:13 UTC
Russell Dickenson <rdickens@redhat.com> updated the status of jira JBPAPP-10925 to Reopened

Comment 4 JBoss JIRA Server 2014-04-11 01:05:47 UTC
Russell Dickenson <rdickens@redhat.com> updated the status of jira JBPAPP-10925 to Closed


Note You need to log in before you can comment on or make changes to this bug.