Nevermind, the configuration was not the issue. My problem was related to my producer being in WebLogic. It is an MDB listening to a Queue in WebLogic meant to forward the message to another server running ActiveMQ. ActiveMQ would obviously not have the WebLogic JMS implementation classes available, and thus could not process the message, though why it did not throw an Exception or otherwise indicate a problem caused me to waste a couple of days trying to figure why my messages were not getting through. My solution was to "rebuild" the message (I use a bunch of JMS properties in addition to using an object body) using the target ActiveMQ objects which was kind of painful but it works.
It would be nice if there were a "copy" or "duplicate" facility that worked at the JMS API level instead of the implementation level (there is an ActiveMQ implementation-side copy, but that won't work with a WebLogic message implementation). -Mike -- View this message in context: http://activemq.2283324.n4.nabble.com/Newbie-confusion-regarding-JNDI-configuration-tp2582968p2716011.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
