[jboss-jira] [JBoss JIRA] (AS7-4036) JCA subsystem doesn't unregister <short-running-threads> and <long-running-threads> workmanager subelements after removing

Wed Mar 7 06:04:36 EST 2012

    [ https://issues.jboss.org/browse/AS7-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674302#comment-12674302 ] 

Stefano Maestri commented on AS7-4036:
--------------------------------------

It will work if you reload the server after remove operation as expected.
You can also remove explicitly short-running. I've found a little problem in persisting config in this case for which I'm sending a pull request 

> JCA subsystem doesn't unregister <short-running-threads> and <long-running-threads> workmanager subelements after removing
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-4036
>                 URL: https://issues.jboss.org/browse/AS7-4036
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JCA
>    Affects Versions: 7.1.0.Final
>            Reporter: Vladimir Rastseluev
>            Assignee: Stefano Maestri
>             Fix For: 7.1.1.Final
>
>
> [standalone at localhost:9999 /] /subsystem=jca/workmanager=newWM:add(name=newWM)
> {
> "outcome" => "success",
> "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" }
> }
> [standalone at localhost:9999 /] /subsystem=jca/workmanager=newWM/short-running-threads=newWM:add(name=newWm,core-threads=20,max-threads=20,queue-length=20)
> {
> "outcome" => "success",
> "response-headers" => {"process-state" => "reload-required"}
> }
> [standalone at localhost:9999 /] /subsystem=jca/workmanager=newWM:remove
> {
> "outcome" => "success",
> "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } }
> }
> [standalone at localhost:9999 /] /subsystem=jca/workmanager=newWM:add(name=newWM)
> {
> "outcome" => "success",
> "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" }
> }
> [standalone at localhost:9999 /] /subsystem=jca/workmanager=newWM/short-running-threads=newWM:add(name=newWm,core-threads=20,max-threads=20,queue-length=20)
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014749: Operation handler failed: Service jboss.thread.executor.newWM.thread-factory is already registered",
> "rolled-back" => true,
> "response-headers" => {"process-state" => "reload-required"}

--
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