My execute/perform methods aren't normally synchronized. The javadocs don't indicate they expect it to be, so, calls to that methods shouldn't get "blocked". However, you could have concurrency problems if you're using static, class, or instance variables. The execute/perform method should limit itself to using local variables or data passed by reference and you won't have this problem. Unless you explicitly declare some class methods synchronized, in which case you're exactly right. If you do that, however, you ought to mean to produce that effect and limit your critical section to a small block of code-- ideally one that doesn't block on anything. ;-)
Maybe I'm out to lunch, though. Its been a while since I've coded java threads.
-nash
On Tuesday, March 11, 2003, at 12:52 PM, Whitmire, Jeffrey wrote:
I'll have to look into it, but it seems to me that if the action is doing a
non-trivial amount of work (which mine is), then if there are multiple
requests, they will get serialized through the single instance of the
action. It may be that I need to redesign how my action works, but
currently it will submit a job and block until it completes. If there were
a pool of actions instead of a single one it seems like it would be more
efficient.
Jeff.
*********************************************************************** This message is intended only for the use of the intended recipient and may contain information that is PRIVILEGED and/or CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any use, dissemination, disclosure or copying of this communication is strictly prohibited. If you have received this communication in error, please destroy all copies of this message and its attachments and notify us immediately. ***********************************************************************
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
