WLS 12c JMS & HermesJMS

Question

Has anyone been able to get HermesJMS working with WLS 12c?
I have followed the setup instructions on various blog posts and such and have basically done the following:
1. Generated the wlfullclient.jar and created a new CLASSPATH group named "WLS12.1".
2. Added a new session using the above classpath.
3. Attempted to discover queues & topics on my WLS instance, and I get a stack trace.
java.lang.NoClassDefFoundError: weblogic/management/WebLogicObjectName
     at hermes.ext.weblogic.WebLogicJMSAdminFactory.createSession(WebLogicJMSAdminFactory.java:63)
     at hermes.impl.HermesAdminAdapter.getAdmin(HermesAdminAdapter.java:64)
     at hermes.impl.HermesAdminAdapter.discoverDestinationConfigs(HermesAdminAdapter.java:82)
     at hermes.impl.DefaultHermesImpl.discoverDestinationConfigs(DefaultHermesImpl.java:1356)
     at hermes.browser.tasks.DiscoverDestinationsTask.invoke(DiscoverDestinationsTask.java:77)
     at hermes.browser.tasks.TaskSupport.run(TaskSupport.java:175)
     at hermes.browser.tasks.ThreadPool.run(ThreadPool.java:170)
     at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException: weblogic.management.WebLogicObjectName
     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)
     ... 8 more
I found some references to including "-Dsun.lang.ClassLoader.allowArraySyntax=true" in the options to Java, but that had no effect.
I am using HermesJMS 1.14, Oracle JDK (1.6.0_35), running on RHEL 5 x86_64.
Here is the classpath section from my hermes-config.xml:
<classpathGroup id="WLS12.1">
<library noFactories="true" jar="/home/wkorb/oracle/middleware/wlserver_12.1/server/lib/wlfullclient.jar"/>
</classpathGroup>
Here is the section that defines my session:
<factory classpathId="WLS12.1">
<provider className="hermes.JNDIConnectionFactory">
<properties>
<property name="initialContextFactory" value="weblogic.jndi.WLInitialContextFactory"/>
<property value="t3://localhost:7001" name="providerURL"/>
<property value="javax/jms/QueueConnectionFactory" name="binding"/>
<property value="weblogic" name="securityPrincipal"/>
<property value="weblogic" name="securityCredentials"/>
</properties>
</provider>
<connection connectionPerThread="false" clientID="">
<session useConsumerForQueueBrowse="false" audit="false" transacted="true" reconnects="0" id="wls12c"/>
</connection>
<extension className="hermes.ext.weblogic.WebLogicJMSAdminFactory">
<properties/>
</extension>
</factory>
Any insight or suggestions would be much appreciated.
Thanks,
Bill

Answer 1

For the "No destinations found" situation, I'm confused. In the WLS console I did the following:
1. Created a JMS server.
2. Created a JMS module.
3. Added to resources to the module: a QueueConnectionFactory & a Queue.
If I am indeed getting connected to the JMS service, should I not see those resources when I try to discover them?You may have missed a few steps during configuration that are required to make sure the Queue is active.
Assuming non-clustered WebLogic:
- The JMS Server target needs to be configured to specify a WL server.
- The JMS module target needs to be set to the same WL server as the JMS server.
- You should configure a "subdeployment" for the module that references the JMS Server.
- You should reference the name of this subdeployment as part of configuring the Queue.
(Using a subdeployment for setting up the association between a Queue and its JMS Server(s) isn't strictly required but is a highly recommended best practice, per http://docs.oracle.com/cd/E24329_01/web.1211/e24385/best_practice.htm#JMSAD455)
To verify the queue is up, you should be able to see the queue on one of the console's monitoring screens, and you should also be able to write a simple thin-t3-jar JMS client that looks up the CF and Q in JNDI and sends a message. The console also provides "message management" screens that allow an admin to inject a test message and/or view messages...
HTH,
Tom