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