I a using ehcache with JMS replication and ActiveMQ as a JMS server. It is currently used to cache database results with Hibernate 3.6.7
My cacheManager is configured as above:
<cacheManagerPeerProviderFactory
class="net.sf.ehcache.distribution.jms.JMSCacheManagerPeerProviderFactory" properties="initialContextFactoryName=br.com.sonner.iss.jms.ExampleActiveMQInitialContextFactory,
providerURL=failover:tcp://localhost:6969,userName=XXX,password=YYYY,
replicationTopicConnectionFactoryBindingName=topicConnectionFactory,
replicationTopicBindingName=ehcache,
getQueueConnectionFactoryBindingName=queueConnectionFactory,
getQueueBindingName=ehcacheGetQueue"
propertySeparator=","
/>
复制和失败正在发挥应有的作用。 如果联合管理系统缩小(复制站),并在联合管理系统服务器再次启用时再次启动。
我面临的唯一问题是,如果联几支助处的服务器在我服用时倒台的话。 这并不是一开始。
Probably because when Spring goes up it reads the hibernate configurations and when hibernate is loading the app just freezes waiting for the broker.
是否有人围绕这一问题开展工作?
我想到的是,是否有办法利用春 j球的组合来混淆切除。