Chris,
This is precisely why we are proposing a new solution which enables
users to have prioritized access to shared resources for all kinds of
requests. It is based on resource management principles and all the
following objects are considered resources in the new proposal:
- Connector Work Thread
- ORB Thread
- HTTP Acceptor and Worker thread
- JDBC/JMS/Connector(JCA) connection
- EJB/Servlet instance
At this point, I can't provide more information, as I am busy in some
other projects. We shall make the functional specification available in
our wikipage when we have one. Please feel free to provide your comments
in RFE #4147. Your feedback is most welcome.
Thanks,
Sahoo
[1]
https://glassfish.dev.java.net/issues/show_bug.cgi?id=4147
Chris Mellard wrote:
> Thanks Jean-Francois,
>
> I've read the articles but there seems to be emphasis on the web
> container. Would the techniques described still work if I were trying to
> balance resource consumption between a web application and an EJB
> message driven bean in the EJB container?
>
> The situation we have is our Web app is outputting Log4J messages to a
> JMS queue using AspectJ. There is then a JMS log consumer MDB on the
> same Glassfish servers as our web-app that then takes these messages and
> logs them to a DB table.
>
> We obviously don't want any log parsing or manipulation to impact the
> main web-app so we need it to be dynamically throttled if the web-app is
> requesting resource - to the point that the MDB effectively stands still
> if need be.
>
> Hope this provides a bit more context to our problem.
>
> Cheers
> Chris
>
> -----Original Message-----
> From: Jeanfrancois.Arcand_at_Sun.COM [mailto:Jeanfrancois.Arcand_at_Sun.COM]
> Sent: 05 March 2009 15:25
> To: Chris Mellard
> Cc: Simon Cook; grizzly-tech_at_Sun.COM; Sanjeeb Kumar Sahoo; Sivakumar
> Thyagarajan
> Subject: Re: Glassfish resource management
>
> Hi,
>
> Chris Mellard wrote:
>
>> Simon/Jean-Francois,
>>
>>
>>
>> Just a quick question regarding Glassfish. Does it have the ability to
>>
>
>
>> manage resource (cpu, memory, IO) amongst competing applications?
>>
>
> Yes we support such mechanism since GlassFish v1. Take a look at:
>
> http://weblogs.java.net/blog/jfarcand/archive/2006/04/resource_consum.ht
> ml
> http://weblogs.java.net/blog/jfarcand/archive/2007/06/improving_ajax_1.h
> tml
> http://weblogs.java.net/blog/jfarcand/archive/2008/10/preventing_rogu.ht
> ml
> http://blogs.sun.com/sduv/entry/resource_management_in_enterprise_applic
> ation
>
>
> The
>
>> only alternative I see to this is to have multiple Glassfish instances
>>
>
>
>> running with an application on each and then using Solaris thread
>> priority to handle the cpu time and also capping memory to a specific
>> value. If there's a smarter way than this then please shout up as it
>> would greatly simplify our deployments (I've done some quick searches
>>
> of
>
>> the documentation for resource management but didn't get any hits)
>>
>
> Siva and Sahoo (CC) are working a new solution for GlassFish v3, but the
>
> current version works well :-)
>
> Thanks
>
> -- Jeanfrancois
>
>
>
>
>>
>>
>> Cheers
>>
>> Chris
>>
>>
>>
>> *Chris Mellard*
>>
>> *Xchanging*
>>
>> 34 Leadenhall Street
>>
>> London EC3A 1AX
>>
>>
>>
>> Tel:
>>
>>
>>
>> +44 (0) 20 7780 5375
>>
>>
>>
>> Ins-sure Services Limited
>>
>> Registered Office: 34 Leadenhall Street, London, EC3A 1AX, UK
>>
>> Registered Number: Registered in England and Wales no. 4124846
>>
>>
>>
>> CONFIDENTIALITY NOTICE
>> This message and any attachment are confidential and may also be
>> privileged. If you are not the intended recipient of this e-mail you
>>
> may
>
>> not copy, forward, disclose or otherwise use it or any part of it in
>>
> any
>
>> form whatsoever. If you are not the intended recipient please
>>
> telephone
>
>> or e-mail the sender and delete this message and any attachment from
>> your system.
>>
>>
>>
>>