[JBoss JIRA] Created: (JBCOMMON-124) Expose getPoolSize() method in ThreadPoolMBean
by Stuart White (JIRA)
Expose getPoolSize() method in ThreadPoolMBean
----------------------------------------------
Key: JBCOMMON-124
URL: https://issues.jboss.org/browse/JBCOMMON-124
Project: JBoss Common
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: common-core (2.x)
Affects Versions: 2.2.18.GA
Reporter: Stuart White
Assignee: Stuart White
Priority: Trivial
Fix For: 2.2.19.GA
The jboss.jca:WorkManagerThreadPool mbean does not expose a getPoolSize() method, even though the method is available on the underlying object. A request was received to expose this method so the pool size can be retrieved via JMX.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (AS7-2246) Log level change doesn't show error
by Kevin Barfield (Created) (JIRA)
Log level change doesn't show error
-----------------------------------
Key: AS7-2246
URL: https://issues.jboss.org/browse/AS7-2246
Project: Application Server 7
Issue Type: Bug
Reporter: Kevin Barfield
I changed the log level for the root-logger from info to fatal. I didn't see any change in the web console. I went to the command window and saw the following:
11:15:50,641 ERROR [org.jboss.as.controller] (HttpManagementService-threads - 3) Operation ("change-root-log-level") failed - address: ([("subsystem" => "logging")]) - failure description: "JBAS011528: Log level FATAL is invalid."
- Is this a valid error?
- If so, the error message should show in the web console
- In general, there should be a success or error message any time there is a change
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months