Can you not use Java 7 on your client? Java 7 was released over 3 years ago now and Java 6 reached its end-of-life over a year ago (February 2013).
Client is weblogic 10.3.5, running application developed by external company. We are considering using weblogic 12 with messaging bridge. Actually big companies like Alcatel and Ericsson (I am familiar with their products) have their solutions running on older application servers and have just roadmaps for the future where they are considering moving to newer servers (and by that to newer java versions).
Maybe you could try compiling hornetq client with java 1.6.
in wildfly we made sure that wildfly-controller-client, the library that is used to remotely connect to wildfly is still complied.
I am not sure if hornetq can be compiled with target 1.6 but it is worth a try.
what is the stack trace when QueueConnectionFactory.createQueueConnection fails?
This is the entire stacktrace:
javax.jms.JMSException: Failed to create session factory
Caused by: java.lang.IllegalStateException: The following keys are invalid for configuring a connector: http-upgrade-endpoint, http-upgrade-enabled
... 8 more
You have this failure because it is likely that the connection-factory that you have configured in the messaging subsystem is still referencing the http-connector that defines these keys (http-upgrade-endpoint, http-upgrade-enabled).
If you have defined a remote-connector, you need to reference it from the connection-factory, it should work using an older HornetQ client.
Jeff, thank you. The problem was indeed with the connection factory. I had to configure a new socket binding (messaging), attach new connector and acceptor (I called it netty as it is called on jboss 7) onto hornetq server and then I configured a new connection factory. Now it works. Thank you again.