I'll give that a try.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3845220#3845220
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3845220
---
SF.Net email is sponsor
Can you reproduce this problem with the standard standalone TreeCaches ?
Bela
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3845089#3845089
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3845089
--
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 TreeCach
looks like they don't find each other; check in the jmx-console (DefaultPartition)
whether you see a cluster of 2.
Bela
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844350#3844350
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mo
looks like this happens when the standalone cache modifies the cache i.e. does a put.
Any pointers would be appreciated.
Thanks.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844278#3844278
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=pos
