Jms upgrade from oc4j 10.1.2.2 to 10.1.3

Question

hello,
I have recently upgraded from oc4j 10.1.2 to 10.1.3 - and everything works ok within my apps apart from JMS messaging.
I have 2 apps within the same oc4j container, the first produces topic messages
ObjectMessage message = session.createObjectMessage(obj);
The second receives the messages - by implementing the MessageListener onMessage interface.
Everything worked perfectly under oc4j 10.1.2 but although I find no errors under 10.1.3 - the receiver never gets the message.
Can you help direct me how to debug this? - or provide probable areas of investigation?
thank you

Answer 1

Thanks Rocky. It was your thorough discussion that prompted me to look at my TopLink sessions.xml configuration more closely, since my existing config did not utilize the transport class you mentioned. As it turns out, I was utilizing the depricated cache coordination mechanism (<cache-synchronization-manager> instead of <remote-command>). With a new configuration as follows, everything is working well:
<remote-command>
<commands>
<cache-sync>true</cache-sync>
</commands>
<transport xsi:type="jms-topic-transport">
<topic-host-url>ormi://localhost:23791/ems</topic-host-url>
<topic-connection-factory-name>jms/Topic/ToplinkCacheSyncConnectionFactory</topic-connection-factory-name>
<topic-name>jms/Topic/ToplinkCacheSync</topic-name>
<jndi-naming-service>
<user-name>oc4jadmin</user-name>
<password>oc4j</password>
<initial-context-factory-name>com.evermind.server.rmi.RMIInitialContextFactory</initial-context-factory-name>
</jndi-naming-service>
</transport>
</remote-command>
Thanks for your contribution,
--Todd