Yes, 4.1.0 is not released yet, but I saw that it is fixed in that build (Currently in Dev).
I also remembered something else, if you change the replication type from REPL_SYNC to REPL_ASYNC, the message goes away and the replication algorithm is more efficient as well. That is what I did to take care of the problem. Even though replication was working properly, my logs were getting large b/c of the stack trace. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871983#3871983 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871983 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
