I am using jboss cache 1.2 inside of a JBoss 4.0 cluster (I just replaced the JBoss-Cache.jar).
I have a single external client who is doing remote calls to a stateless session bean inside the appserver which in turn is calling TreeCacheAOP to put a serializable into the cache. In the same thread in my external client I then do a read (which from what I understand should be blocked until the previous write has been replicated to all nodes in the cluster). This read is hitting a different JBoss instance than where the write occured and I end up pulling a null instance of my Serialiable object from the cache... Which would seem to indicate that it has not yet been replicated to that node. I am using transactions and I have tried both "REAPEATABLE_READ" and "SERIALIZABLE" I get no exceptions. Is there a bug in the blocking or is my session bean/reflection stuff interfering? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859614#3859614 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859614 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
