View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820238#3820238

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820238

You'll need to review using the "all" jboss configuration instead of the "default" 
configuration (if you're not already doing so).



If you're using the "the appserver owns the DB" caching policy (policy A??), you'll 
need to ensure that your entity caches are sync'ed.



Jboss has made this pretty easy to do, but you'll need to configure a few things in 
the various xml files -- described in the pay-for doco.



I believe that using the "appserver owns the DB" caching policy may offer the best 
performance -- if you can live with it's limitations.



Regards,

Greg.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to