Re: Java Monitor : what is the max number of applications it could handle?

Graham J Lee a =E9crit :
> On 9 Jan 2007, at 08:52, Cheong Hee (Datasonic) wrote:
>
>> Dear all
>>
>> I supposed I have seen someone has posted that the maximum=20
>> applications that a JavaMonitor could handle is 25 (may be I did not=20
>> get it right, optimum?). I have tried with more than 40 dummy=20
>> applications but JavaMonitor still allows me to create.  Is there=20
>> anything I missed here?
>>
>
> I've never tried that...but...
>
>> As I am doing some testing to see how WebObjects could be brought=20
>> into ASP mode.  Surely the issues of how the servers are going to be=20
>> set up cost-effectively are very relevant.  Is it a good idea to just=20
>> set one JavaMonitor and handle all different applicaitons (actual=20
>> fact is only same application)?  I have done that with a few and it=20
>> works.  Appreciate someone could share experiences.
>
> AFAICT you're not *supposed* to use more than one JavaMonitor per=20
> subnet.  In practice I've never had any problems with two JavaMonitors=20
> on the same subnet, although even so after a while I firewalled off=20
> the JavaMonitor and wotaskd ports from each other, Just In Case(TM).
>
> Cheers,
> Graham.
>
Hi,
As far as I know, there isn't limit inside JavaMonitor or WoTaskd (our=20
has ~70 running instances distributed over 3 wotaskd).
But the adaptaror for the web server can't handle more than 64 runing=20
applications ! it is hardcoded in the source code. For WO 5.2 the=20
sources comes with the install and for WO 5.3 (or if you don't have the=20
sources) you have to use the Project Wonder Adaptor (it is a patched one=20
from the original) http://wonder.sourceforge.net/WOAdaptor.html (=20
download the last version Wonder-3.0-src.zip on=20
http://sourceforge.net/project/showfiles.php?group_id=3D45176 ). Increase=
=20
value of  WA_MAX_APP_COUNT and WA_MAX_APP_INSTANCE_COUNT in=20
Adaptor/config.h and rebuild the adaptor.

Also JavaMonitor isn't mandatory, it's just an interface to manage the=20
configuration which is used by wotaskds, concurancy could be bad that's=20
why you must have only one JavaMonitor for managing a set of wotaskd (2=20
JavaMonitor could manage different wotaskd).
JavaMonitor doesn't care about subnet but your web server adaptor could,=20
cause it can do broadcast for finding running instances (look at=20
http://developer.apple.com/documentation/WebObjects/Deployment/Deploying_=
Applications/=20
for more informations)

Regards

Aur=E9lien Minet