Concurrency should not be an issue as long as you are doing pooling correctly. Don't allow access to handles across threads (e.g. storing them in static fields or shared objects). Even then, this is only really an issue if you support transactions, it depends upon what constraints you use outside a transaction. e.g. jdbc allows concurrent access -it requires internal synchronization. JMS says you must use external synchronization on the jms session.
I would say the JavaMail spec requires internal synchronization. "When sharing the session object, all applications share authentication information, properties, and the rest of the state of the object." Regards, Adrian View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830819#3830819 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830819 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
