I wonder if somebody could enlighten me with regards to the fairness of
processing requests in Glassfish / Grizzly under load.
Is there some some guarantee that one heavily loaded application will not
hog all the resources from another using the same grizzly instance?
Is the only way to "partion" the resources to create separate HTTP
listeners?
Will these threads configured for the HTTP-listener run through the servlet
container and down into the EJB-container?
It would be great to be able to specify a weight for an application in the
deployment descriptor and have the request processing scheduled accordingly.
/Jesper