What you describe sounds correct. I'm assuming here the client for your SLSB is the web tier. Adding @Clustered to your SLSB allows the web tier to make calls on beans on another server. The benefit of this is if the bean is unavailable on the local machine, the web tier can still work. The downside is calls will be remote, therefore serialized. If your SLSB is going to have the same lifecycle as the web app (i.e. deployed as a unit), you're better of not using @Clustered and ensuring all calls remain in the same VM.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910992#3910992 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910992 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
