Error running com.evermind.server.jms.JMSUtils

Question

I'm running the following from the Developer prompt command window of a 10.1.2 midtier install.
java -classpath C:\OraHome_AppServ\j2ee\home\oc4j.jar com.evermind.server.jms.JMSUtils destinations
This gives the following error:
Oracle Application Server Containers for J2EE 10g (10.1.2.0.0) (build "041223.1874"), OC4J JMS 1.0.2b
javax.jms.JMSException: Unable to create a connection to "/0.0.0.0:9,127" as user "null".
at com.evermind.server.jms.JMSUtils.makeJMSException(JMSUtils.java:1843)
at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1859)
at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:114)
at com.evermind.server.jms.EvermindConnectionFactory.createConnection(EvermindConnectionFactory.java:118)
at com.evermind.server.jms.EvermindConnectionFactory.createConnection(EvermindConnectionFactory.java:110)
at com.evermind.server.jms.JMSUtils.dest(JMSUtils.java:679)
at com.evermind.server.jms.JMSUtils.main(JMSUtils.java:265)
I'm running this to see if my Queue to Topic sample is working correctly. I suspect this is a configuration error but I'm not sure how to fix it.
Thanks,
Craig

Answer 1

These objects are created on the server when the oc4j.jms.debug property is true. They are used to track DMS phases that have been started but not yet completed. DMS phases are started (and these objects created) when operations on various OC4J JMS server-side objects (representing JMS connections, sessions, producers, consumers, browsers) are started, and are (supposed to be) ended (and these objects released) when those operations complete. Specifically, allocation is done via JMSObject.lock and release is via JMSObject.unlock. It's possible that you are hitting some case where one of these operations is calling lock() and then failing to call unlock(). Note that, despite the name, in most cases the lock() method doesn't check that the given JMS object isn't already locked, so multiple calls to lock() without an unlock() will typically not generate any kind of error or warning (but will produce a memory leak).
At least for debugging purposes, a modified JMSObject.class file could be used which had a member variable isLocked, set isLocked in lock(), cleared it in unlock(), and verified it is clear before setting it (throwing/logging otherwise). If you are unable (or are legally prevented) from doing such a temporary modification yourself, you should suggest that support provide you with such a modified class file as it will likely be the fastest way to find the root cause. (Note that it would not necessarily flag an error on the faulty operation, but rather on the next attempted operation on the given object or one of its "children", so you would need to backtrack to figure out what the last operation was. "children" is defined as "session is child of connection" and "consumer/producer/browser" are child of session" -- locking/unlocking a child also locks/unlocks the parent.)
As a workaround, you might try just not using oc4j.jms.debug.
-Jeff