[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on AS7-3446:
-----------------------------------
That's odd. I still get no error at all.
{noformat}
/subsystem=threads/queueless-thread-pool=myqueless/:add(max-threads=1)
{
"outcome" => "success",
"response-headers" => {"process-state" =>
"reload-required"}
}
/subsystem=threads/thread-factory=myfactory/:add
{
"outcome" => "success",
"response-headers" => {"process-state" =>
"reload-required"}
}
/subsystem=threads/queueless-thread-pool=myqueless/:write-attribute(name=thread-factory,value=myfactory)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
/subsystem=threads/thread-factory=myfactory/:remove
{
"outcome" => "success",
"response-headers" => {"process-state" =>
"reload-required"}
}
{noformat}
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL:
https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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