Re: [jboss-as7-dev] Important Subsystem Management Use-Cases
Jason has replied separately ("Limiting Server Thread Usage") about the
more interesting aspect of this -- actually enforcing an overall limit.
Beyond that there's a general issue of making sure all subsystems or
core services are properly exposing their threading configurations so
they can be managed. I know you committed a fix in this area for the
core server a while back.
On 9/14/11 10:39 AM, Scott Stark wrote:
The other big cross cutting concern is controlling the total number
of
threads in use by the application server. When running under a
constrained environment that uses something like pam_limits module to
control how many process(==java threads) a user can have, it is
difficult to know what the server max thread usage is right now.
On 9/13/11 2:07 PM, Brian Stansberry wrote:
> This is a good list.
>
> There are also some cross-cutting concerns that we need to address in
> all subsystems:
>
> 1) Validation of parameters by the OperationStepHandler impls
> 2) Properly dealing with default values.
> 3) Properly dealing with expressions (i.e.<inet-address
> value="${jboss.bind.address.public:127.0.0.1}"/>
>
> I'm in the process of updating Kabir's "Extending JBoss AS 7"
guide[1]
> to include some fairly straightforward techniques for all of these things.
>
> [1] https://docs.jboss.org/author/display/AS7/Extending+JBoss+AS+7
>
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat