You should be able to exhaust your tomcat thread pool using BlazeDS, something else is going wrong.
-Josh 2009/5/20 Aldo Bucchi <aldo.buc...@gmail.com> > > > foobone9, > > Are you saying that this is a known built-in limitation of BlazeDS? > > Thanks, > A > > > On Tue, May 19, 2009 at 6:58 PM, foobone9 > <foobo...@yahoo.com<foobone9%40yahoo.com>> > wrote: > > > > > > I think you need to invest in Live Cycle Data Servies. > > > > --- In flexcoders@yahoogroups.com <flexcoders%40yahoogroups.com>, Aldo > Bucchi <aldo.buc...@...> wrote: > >> > >> ( I copy this email from an internal communication I received ) > >> > >> <quote> > >> > >> Hello, > >> > >> I've found a serious performance problem on an application written on > >> Flex/AIR and using BlazeDS v3.0.0.544. By looking at the logs I can > >> see that the server side method (invoked via RemoteObject on the > >> client side) never executes in more than two threads at the same time. > >> What I mean is that if I fire 5 simultaneous requests to the method > >> using RemoteObject from the flex side, and log when the method is > >> executed and when it returns, I get something like this: > >> > >> 12:00:00 Method Executed > >> 12:00:00 Method Executed > >> 12:00:01 Method Exiting > >> 12:00:01 Method Executed > >> 12:00:04 Method Exiting > >> 12:00:04 Method Executed > >> 12:00:10 Method Exiting > >> 12:00:10 Method Executed > >> 12:00:11 Method Exiting > >> 12:00:13 Method Exiting > >> > >> While on the client side I see that all the 5 invocations were fired > >> at 12:00:00. > >> > >> As you can see, the method tend to take a while to run. But the big > >> problem is that the log suggest that some queuing is happening on the > >> server side, allowing only a maximum of two threads to run in parallel > >> at any given time. > >> > >> I thought it could be a problem with the thread pool of the servlet > >> container, but my Tomcat has the following configuration: > >> > >> <Executor name="tomcatThreadPool" namePrefix="catalina-exec-" > >> maxThreads="150" minSpareThreads="4"/> > >> > >> So I guessed that the limit could be imposed by BlazeDS itself. But > >> haven't found anything on the documentation. Of course, I could be > >> wrong and the problem may be something else. > >> > >> Any ideas? > >> > >> Thanks, > >> Leo > >> > >> </quote> > >> > >> Note: The Remote Object destination has "application" scope, which > >> means that there is only one instance of the Java object per > >> application. > >> > >> Regards, > >> A > >> > >> -- > >> Aldo Bucchi > >> U N I V R Z > >> Office: +56 2 795 4532 > >> Mobile:+56 9 7623 8653 > >> skype:aldo.bucchi > >> http://www.univrz.com/ > >> http://aldobucchi.com/ > >> > >> PRIVILEGED AND CONFIDENTIAL INFORMATION > >> This message is only for the use of the individual or entity to which it > >> is > >> addressed and may contain information that is privileged and > confidential. > >> If > >> you are not the intended recipient, please do not distribute or copy > this > >> communication, by e-mail or otherwise. Instead, please notify us > >> immediately by > >> return e-mail. > >> INFORMACIÓN PRIVILEGIADA Y CONFIDENCIAL > >> Este mensaje está destinado sólo a la persona u organización al cual > está > >> dirigido y podría contener información privilegiada y confidencial. Si > >> usted no > >> es el destinatario, por favor no distribuya ni copie esta comunicación, > >> por > >> email o por otra vía. Por el contrario, por favor notifíquenos > >> inmediatamente > >> vía e-mail. > >> > > > > > > -- > Aldo Bucchi > U N I V R Z > Office: +56 2 795 4532 > Mobile:+56 9 7623 8653 > skype:aldo.bucchi > http://www.univrz.com/ > http://aldobucchi.com/ > > PRIVILEGED AND CONFIDENTIAL INFORMATION > This message is only for the use of the individual or entity to which it is > addressed and may contain information that is privileged and confidential. > If > you are not the intended recipient, please do not distribute or copy this > communication, by e-mail or otherwise. Instead, please notify us > immediately by > return e-mail. > INFORMACIÓN PRIVILEGIADA Y CONFIDENCIAL > Este mensaje está destinado sólo a la persona u organización al cual está > dirigido y podría contener información privilegiada y confidencial. Si > usted no > es el destinatario, por favor no distribuya ni copie esta comunicación, por > email o por otra vía. Por el contrario, por favor notifíquenos > inmediatamente > vía e-mail. > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." Josh 'G-Funk' McDonald - j...@joshmcdonald.info - http://twitter.com/sophistifunk - http://flex.joshmcdonald.info/
