[JBoss JIRA] (JBCOMMON-119) BasicThreadPool stops using RestoreTCCLThreadPoolExecutor when setMaximumPoolSize is called
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/JBCOMMON-119?page=com.atlassian.jira.plug... ]
Brian Stansberry updated JBCOMMON-119:
--------------------------------------
Assignee: (was: Brian Stansberry)
> BasicThreadPool stops using RestoreTCCLThreadPoolExecutor when setMaximumPoolSize is called
> -------------------------------------------------------------------------------------------
>
> Key: JBCOMMON-119
> URL: https://issues.jboss.org/browse/JBCOMMON-119
> Project: JBoss Common
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: common-core (2.x)
> Affects Versions: 2.2.18.GA
> Reporter: James Livingston
> Attachments: jbcommon-119.diff
>
>
> JBCOMMON-41 modified BasicThreadPool to use a new class RestoreTCCLThreadPoolExecutor, so that the classloader wasn't leaked. However only the code in the constructor was changed, not the code in setMaximumQueueSize() which re-creates the executor.
> This means that if you call setMaximumQueueSize(), it will switch back to the standard executor and so the special code in RestoreTCCLThreadPoolExecutor will not run.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6664) Unable to turn on/off logging handlers using enable()/disable() in CLI
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6664?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated AS7-6664:
-----------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=915317
> Unable to turn on/off logging handlers using enable()/disable() in CLI
> ----------------------------------------------------------------------
>
> Key: AS7-6664
> URL: https://issues.jboss.org/browse/AS7-6664
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, Logging
> Affects Versions: 7.2.0.Alpha1
> Reporter: Brian Stansberry
> Assignee: James Perkins
> Fix For: 8.0.0.Alpha1
>
>
> Peter Kremens reports:
> I am unable to use enable/disable operation in logging handlers.
>
> {code}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => true,
> ...
> }
> }
> {code}
> Calling disable() won't affect enabled attribute
> {code}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:disable()
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => true,
> ...
> }
> }
> {code}
> Must use write-attribute instead
> {code}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE/:write-attribute(name=enabled, value=false)
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => false,
> ...
> }
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6664) Unable to turn on/off logging handlers using enable()/disable() in CLI
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6664?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6664:
----------------------------------------------
Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 915317|https://bugzilla.redhat.com/show_bug.cgi?id=915317]
James, please assign bz 915317 to yourself. Thanks.
> Unable to turn on/off logging handlers using enable()/disable() in CLI
> ----------------------------------------------------------------------
>
> Key: AS7-6664
> URL: https://issues.jboss.org/browse/AS7-6664
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, Logging
> Affects Versions: 7.2.0.Alpha1
> Reporter: Brian Stansberry
> Assignee: James Perkins
> Fix For: 8.0.0.Alpha1
>
>
> Peter Kremens reports:
> I am unable to use enable/disable operation in logging handlers.
>
> {code}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => true,
> ...
> }
> }
> {code}
> Calling disable() won't affect enabled attribute
> {code}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:disable()
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => true,
> ...
> }
> }
> {code}
> Must use write-attribute instead
> {code}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE/:write-attribute(name=enabled, value=false)
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => false,
> ...
> }
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6664) Unable to turn on/off logging handlers using enable()/disable() in CLI
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-6664:
-------------------------------------
Summary: Unable to turn on/off logging handlers using enable()/disable() in CLI
Key: AS7-6664
URL: https://issues.jboss.org/browse/AS7-6664
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Logging
Affects Versions: 7.2.0.Alpha1
Reporter: Brian Stansberry
Assignee: James Perkins
Fix For: 8.0.0.Alpha1
Peter Kremens reports:
I am unable to use enable/disable operation in logging handlers.
{code}
[standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource
{
"outcome" => "success",
"result" => {
"autoflush" => true,
"enabled" => true,
...
}
}
{code}
Calling disable() won't affect enabled attribute
{code}
[standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:disable()
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource
{
"outcome" => "success",
"result" => {
"autoflush" => true,
"enabled" => true,
...
}
}
{code}
Must use write-attribute instead
{code}
[standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE/:write-attribute(name=enabled, value=false)
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource
{
"outcome" => "success",
"result" => {
"autoflush" => true,
"enabled" => false,
...
}
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months