2:15 p.m.
The following is my perception of what we really want to offer in terms
of management use cases on a per subsystem basis. In some cases we offer
these today in DMR, in others we do not, and need to get them in ASAP.
As a first though, I wanted to make sure that everyone is on the same
page about what we need. I tried to list these in order of importance.
Please offer your thoughts and/or make corrections
Infinispan
----------
1. Start/stop cache
2. Adjust expiration/eviction settings
3. Create new cache configs
4. Modify all other settings (write attribute)
JCA Core
---
1. Adjust work manager defaults
2. Modify all other settings (write attribute)
JCA Resource Adapters & Datasources
---------------------------------
1. Define new resource adapters / DS
2. Adjust pool settings
3. Pool metrics
4. Flush pools
5. Secure existing resource adapters
6. Change JNDI name (possibly a copy and expiration to allow hot changes)
7. Modify all other settings (write attribute)
Deployment Scanner
------------------
1. Disable/Enable
2. Modify all other settings (write attribute)
EE
--
1. Modify global module list
2. Dump all naming information for an EE deployment
3. Modify all other settings (write attribute)
EJB3
----
1. Manage pool settings
2. Pool metrics
3. Flush pools
4. Adjust default MDB resource adapter
5. Configure scheduler service
6. Scheduler service metrics
7. Modify all other settings (write attribute)
8. Manually remove/add scheduled events
JAX-RS
------
Nothing to do here?
JMX
---
1. Add/remove connection configuration
2. Security domain configuration
JPA
---
1. Setting the default data source
2. Enable/Disable and expose Hibernate Entity Manager metrics (note
these probably belong underneath the deployment)
Logging
-------
1. Define a new logger
2. Change log level (hot)
3. Edit all attributes on an existing logger
4. Add a custom handler
5. Add a custom formatter
Naming
------
1. Dump all jndi bindings
OSGi
----
1. Anything beyond Enable/Disable is a nice to have
POJO
----
Nothing to do here?
Remoting
--------
1. Add/Edit all connectivity information
2. Modify thread pool settings
3. Modify all other settings (write attribute)
SAR
---
Perhaps some combatibility settings?
Security
--------
1. Define a new security domain
2. Flush authentication cache on the domain
3. Edit all attributes on a domain (write attribute)
4. Authentication metrics
Transactions
------------
1. Edit recovery manager settings
2. Toggle JTA/JTS (restart required ok)
3. All other writable attributes
4. Transaction metrics
Web
---
1. Add / Remove connector configs
2. Edit all connector settings
3. Connection metrics
4. Add / Remove virtual server configurations
5. Add / Remove virtual server aliases and edit all settings
6. Specify a custom executor
Weld
----
Nothing to do here?
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
4:07 p.m.
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
On 9/13/11 2:15 PM, Jason T. Greene wrote:
The following is my perception of what we really want to offer in
terms
of management use cases on a per subsystem basis. In some cases we offer
these today in DMR, in others we do not, and need to get them in ASAP.
As a first though, I wanted to make sure that everyone is on the same
page about what we need. I tried to list these in order of importance.
Please offer your thoughts and/or make corrections
Infinispan
----------
1. Start/stop cache
2. Adjust expiration/eviction settings
3. Create new cache configs
4. Modify all other settings (write attribute)
JCA Core
---
1. Adjust work manager defaults
2. Modify all other settings (write attribute)
JCA Resource Adapters& Datasources
---------------------------------
1. Define new resource adapters / DS
2. Adjust pool settings
3. Pool metrics
4. Flush pools
5. Secure existing resource adapters
6. Change JNDI name (possibly a copy and expiration to allow hot changes)
7. Modify all other settings (write attribute)
Deployment Scanner
------------------
1. Disable/Enable
2. Modify all other settings (write attribute)
EE
--
1. Modify global module list
2. Dump all naming information for an EE deployment
3. Modify all other settings (write attribute)
EJB3
----
1. Manage pool settings
2. Pool metrics
3. Flush pools
4. Adjust default MDB resource adapter
5. Configure scheduler service
6. Scheduler service metrics
7. Modify all other settings (write attribute)
8. Manually remove/add scheduled events
JAX-RS
------
Nothing to do here?
JMX
---
1. Add/remove connection configuration
2. Security domain configuration
JPA
---
1. Setting the default data source
2. Enable/Disable and expose Hibernate Entity Manager metrics (note
these probably belong underneath the deployment)
Logging
-------
1. Define a new logger
2. Change log level (hot)
3. Edit all attributes on an existing logger
4. Add a custom handler
5. Add a custom formatter
Naming
------
1. Dump all jndi bindings
OSGi
----
1. Anything beyond Enable/Disable is a nice to have
POJO
----
Nothing to do here?
Remoting
--------
1. Add/Edit all connectivity information
2. Modify thread pool settings
3. Modify all other settings (write attribute)
SAR
---
Perhaps some combatibility settings?
Security
--------
1. Define a new security domain
2. Flush authentication cache on the domain
3. Edit all attributes on a domain (write attribute)
4. Authentication metrics
Transactions
------------
1. Edit recovery manager settings
2. Toggle JTA/JTS (restart required ok)
3. All other writable attributes
4. Transaction metrics
Web
---
1. Add / Remove connector configs
2. Edit all connector settings
3. Connection metrics
4. Add / Remove virtual server configurations
5. Add / Remove virtual server aliases and edit all settings
6. Specify a custom executor
Weld
----
Nothing to do here?
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
4:26 a.m.
On 13 Sep 2011, at 22:07, 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
I have added the code for the example subsystem to git:
https://github.com/jbossas/archetypes/tree/master/jboss-as-subsystem-example
10:39 a.m.
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
1:06 p.m.
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
4:33 p.m.
POJO
----
Nothing to do here?
I'm actually thinking of adding some reflection based management layer.
* it should be lazy as possible
* only added / enabled if explicitly defined in -jboss-beans.xml descriptor
Similar to what we had in AS5/6, but more lazy - only building this on demand (if
possible).
9:47 p.m.
On Wednesday 14 September 2011 12:45 AM, Jason T. Greene wrote:
EJB3
----
1. Manage pool settings
This is currently available since 7.0.1. Adding/removing pool
configurations as well as editing them from the CLI. David B is working
on making this available in the web console
https://issues.jboss.org/browse/AS7-753.
4. Adjust default MDB resource adapter
Available since 7.0.1 and can currently be done via CLI
5. Configure scheduler service
6. Scheduler service metrics
7. Modify all other settings (write attribute)
8. Manually remove/add scheduled events
9. Adjust the default pool config used by SLSB and MDB : This is
available since 7.0.1 via CLI.
-Jaikiran
3:31 a.m.
On 09/14/2011 04:47 AM, Jaikiran Pai wrote:
On Wednesday 14 September 2011 12:45 AM, Jason T. Greene wrote:
> EJB3
> ----
> 1. Manage pool settings
This is currently available since 7.0.1. Adding/removing pool
configurations as well as editing them from the CLI. David B is working
on making this available in the web console
https://issues.jboss.org/browse/AS7-753.
> 4. Adjust default MDB resource adapter
Available since 7.0.1 and can currently be done via CLI
> 5. Configure scheduler service
> 6. Scheduler service metrics
> 7. Modify all other settings (write attribute)
> 8. Manually remove/add scheduled events
What is this bit? The timers?
9. Adjust the default pool config used by SLSB and MDB : This is
available since 7.0.1 via CLI.
Subsection of 1?
10. Manage (SFSB) caches
- query sessions
- flush individual / all (passivated) sessions
- configure active count
- configure passivation timeout
Carlo
-Jaikiran
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
4:52 a.m.
On Wednesday 14 September 2011 02:01 PM, Carlo de Wolf wrote:
>> ----
>> 1. Manage pool settings
> This is currently available since 7.0.1. Adding/removing pool
> configurations as well as editing them from the CLI. David B is working
> on making this available in the web console
> https://issues.jboss.org/browse/AS7-753.
> 9. Adjust the default pool config used by SLSB and MDB : This is
> available since 7.0.1 via CLI.
Subsection of 1?
Oh yeah, that would indeed be part of managing pool settings.
-Jaikiran
2:16 a.m.
Speaking in terms of the console:
The management operations for AS 7.1 need to be provided by 26. Sept.
Most important subsystems (my point of view, leaning on Jason's list)
- Infinispan
- EJB
- Security
- Transactions
- Remoting
We really need get this done within the next two weeks.
Otherwise we can not deliver a feature complete console for AS 7.1
and the EAP versions that derive from it.
Ike
On Sep 13, 2011, at 9:15 PM, Jason T. Greene wrote:
In some cases we offer
these today in DMR, in others we do not, and need to get them in ASAP.
4851
days inactive
4852
days old
9 comments
8 participants
participants (8)
-
Ales Justin -
Brian Stansberry -
Carlo de Wolf -
Heiko Braun -
Jaikiran Pai -
Jason T. Greene -
Kabir Khan -
Scott Stark