thanks for sharing!
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256611#4256611
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256611
___
jboss-user mailing list
jboss-user@
OK, I've found the solution to my problem.
First, it wasn't in the configuration of the TreeCache itself, but of the
Hibernate Cache provider.
It turns out that this behaviour is by design the default in the Hibernate
JBoss Cache provider (hibernate-jbc-cacheprovider-1.0.1.GA.jar).
See:
http:
What's very curious is the fact that logs on both cluster nodes indicate that
the elements are added to the cache. E.g., after the BPEL process is executed
and transaction gets committed:
node 1 (initiator):
| 2009-09-22 15:56:04,686 DEBUG
[org.jboss.cache.eviction.BaseEvictionAlgorithm] Ad
BTW, anticipating th question: I can see that indeed the cache cluster gets
formed, I can see the IP addresses of all the members in the "Members"
attribute of the TreeCache MBean, the list of node IP addresses and their ports
is identical on all cluster members.
Only one of all the cluster nod
