Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JMS Clustering

 
syed aliarshad
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

I guess I have the same situation here..

I am using Toplink as ORM. I have implemented caching too using cache coordination.

Below are the lines that I have added in Toplink-session.xml file for caching.

------------------------------------------------------------------------------------------------------------------------

<remote-command>
<commands>
<cache-sync>true</cache-sync>
</commands>
<transport xsi:type="jms-topic-transport">
<topic-host-url>tcp://someurl.com:61616</topic-host-url>
<topic-connection-factory-name>java:comp/env/jms/CacheTopicConnectionFactory</topic-connection-factory-name>
<topic-name>java:comp/env/jms/topicname</topic-name>
<jndi-naming-service>
<initial-context-factory-name>org.apache.activemq.jndi.ActiveMQInitialContextFactory</initial-context-factory-name>
</jndi-naming-service>
</transport>
</remote-command>
------------------------------------------------------------------------------------------------------------------------


The above settings are working fine for one node cache. I want to make the JMS Cluster having more than one cache node. How can I achieve this?


Thanks
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic