We're prototyping open source replacements for a legacy application.
When we're running a prototype again ActiveMQ, we don't have any problems. Well, we ended up running spring on the
applet side(!) because of an initialization issue with the naked activemq client libraries, but that was a mere annoyance.
When we're running a prototype against the Oracle JMS wrapper on ActiveQueues, we run into a brick wall. (The legacy app uses AQ, we're prototyping on new AQ queues with JMS support enabled.) With the help of some online resources we've been able to get a
test case to the point where the JMS calls throw a generic "corrupt data" exception, and the corresponding AQ-specific calls throw a NPE when writing to a HashTable in a 'convertPropertyListToHashtable' call. We're pretty confident that the JMS exception is just a wrapper for this NPE.
This suggests that we haven't specified some message property, but we're coming up blank since it works with ActiveMQ and there's no mention of this in the AQ JMS resources.
BTW this happens with test payloads of Date,
String and a String containing XML text.
Ideas?
P.S., we're running 11.1g and saw a similar problem reported about 6 months ago, but no resolution was discussed.