looks like this happens when the standalone cache modifies the cache i.e. does a put.
Any pointers would be appreciated.
looks like they don't find each other; check in the jmx-console (DefaultPartition) whether you see a cluster of 2.
Bela, let me explain the setup little more detail.
besides what i orginall mentioned, on the server I have a custom Mbean which extends ServiceMBeanSupport class, this mbean has an instance of TreeCache & starts it.
Note if i stop and start the server while the client still up,
the client TreeCache replicates it's state to the server and vice versa i.e. if i stop and start client while the server is still running the client gets the state from the server. So far so good, but while running whenever i say put an object into the cache either from the server or the client i get that message that i mention in my first post.
From what i understand looking at the message is that the client and the server caches cannot communicate, but that seems incorrect as they are able to update each other of any state changes.
Can you reproduce this problem with the standard standalone TreeCaches ?
I'll give that a try.