can you please show the exception you get?
It's working now, very cool. Well done.
I've tested various combinations of calls to the BMP Entity Beans and ejbLoad is being correctly called on, say, Machine B, when Machine A receives an update.
The clustering capability opens up a number of projects to us that we can now approach, i.e. where clustering is a mandatory customer specified capability.
I think I was getting errors when I'd uncommented the duplicate definitions of the jboss.cache:service=InvalidationBridge that seems to be defined in both of:
a) cache-invalidation-service.xml, and
In my current working configuration, I have left the InvalidationBridge service commented out in cache-invalidation-service.xml.
I may also have received errors on startup of JBoss when I'd forgotten to make sure that all machines in the cluster were not configured identically, but can't seem to reproduce this error again.
Question: Which InvalidationBridge definition does JBoss recommend is used from the two above mentioned files?
...don't worry about my last question.
I re-read the manual (RTFM) and found the section describing the difference between the two invalidation bridge choices.
JMS -> async
Java Groups -> synchronous
+ the various other differences.