Re: Does WO block when WOWebServiceRegister is used?
Re: Does WO block when WOWebServiceRegister is used?
- Subject: Re: Does WO block when WOWebServiceRegister is used?
- From: Hsu <email@hidden>
- Date: Tue, 2 Sep 2003 07:13:51 -0700
By default request are processed single-threaded (if you search the
archives for "WOAllowsConcurrentRequestHandling" you'll see a bunch of
discussion on it). WO does not attempt to suddenly go multi-threaded
under high load - if you want multithreaded access, you'll have to
enable it yourself (see aforementioned flag).
Note that WO is using the Axis 1.0 stack as the basic webservice
engine; I'm not entirely certain whether they run multithreaded
internally; some testing might be required.
Karl
On Tuesday, September 2, 2003, at 03:59 AM, Sergio Trejo wrote:
The 5.2 WO API documents include WOWebServiceRegistrar object. It has
a registration method (registerWebService) for exposing any Java
class's methods as webservice operations.
From the Security WO web service app demo that comes with WO 5.2, in
the Application Java class, there is this:
// Register Web service classes.
WOWebServiceRegistrar.registerWebService(LogIn.class, true);
WOWebServiceRegistrar.registerWebService(AccessData.class,
true);
I did a test and found out that a Java class when registered with this
method in the same manner as LogIn and AccessData, is instantiated
only once and run persistently (I used a global counter inside the
class which was incremented every time it processed a SOAP request as
an RPC). I can't tell how WO handles multiple SOAP requests of such a
registered Java class when the SOAP messages are received by the WO
app at instantaneously the same time when using a basic WO deployment
set up (nothing fancy -- no load balancing or distributed app server
hosts). If a WO WebServices app like this gets bombarded with tons of
SOAP requests at the same time, how does it handle the flow of SOAP
traffic? Does it block and process sequentially, or is this somehow
handled in a multithreaded way? It doesn't appear to be multithreaded
with a few back-to-back tests from a few clients sending SOAP requests
rather swiftly one after another which I tested, but I wonder if a WO
app like this starts to get flooded with mega SOAP requests, does the
WO app change its approach and go from a blocking approach to a
multithreaded approach? If this is so, then how does it clean up after
the flood is finished and the multiple instances of Java classes are
no longer needed in memory? Thanks for any suggestion.
ST
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
--
Better living through denial.
Homepage:
http://homepage.mac.com/khsu/index.html
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.