No, it doesn't replicate at the start of the request. In releases prior to 4.0.4, calling session.getAttributeNames() would mark the session as dirty, thus causing replication at the end of the request. That's why your "dump" call causes replication. I believe I changed that in 4.0.4.
I figured out a hack you can try to get immediate replication upon change of an attribute. This may or may not work. You'd need to use 4.0.4, with this in your jboss-web.xml | <replication-config> | <replication-granularity>FIELD</replication-granularity> | <replication-trigger>(whatever you want)</replication-trigger> | <replicationFieldBatchMode>false</replicationFieldBatchMode> | </replication-config> | With FIELD granularity and no batching, you'll get immediate replication. You don't need to instrument your classes to use FIELD; you just don't get the benefits of fine-grained replication if you don't. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949902#3949902 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949902 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
