[jboss-jira] [JBoss JIRA] (WFCORE-3406) customized BlockerExtension does not block correctly for standalone server case

[Chao Wang (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chao Wang updated WFCORE-3406:
------------------------------
    Description: 
The find-non-progressing-operation operation of /core-service=management/service=management-operations doesn't return the operation id of a blocking operation on standalone. It works on domain mode.
To simulate the blocking operation, install the BlockingExtension from testsuite and call 
{code}
/subsystem=blocker-test:block(block-point=MODEL,block-time=50000}
{code}
Open another jboss-cli.sh and call 
{code}
/core-service=management/service=management-operations:find-non-progressing-operation
{code}

Update: 
The example above reveals when people manually install BlockingExtension and run in standalone mode, BlockingExtension does not correctly block and count time, as it does not acquire the exclusive lock.
In domain mode, it acquires the lock by calling [context.readResourceForUpdate|https://github.com/wildfly/wildfly-core/blob/4.0.0.Alpha2/testsuite/shared/src/main/java/org/jboss/as/test/integration/management/extension/blocker/BlockerExtension.java#L163]. This does not affect current test scenarios as the block function is tested in OperationCancellationTestCase under domain mode.  


  was:
The find-non-progressing-operation operation of /core-service=management/service=management-operations doesn't return the operation id of a blocking operation on standalone. It works on domain mode.
To simulate the blocking operation, install the BlockingExtension from testsuite and call 
{code}
/subsystem=blocker-test:block(block-point=MODEL,block-time=50000}
{code}
Open another jboss-cli.sh and call 
{code}
/core-service=management/service=management-operations:find-non-progressing-operation
{code}




> customized BlockerExtension does not block correctly for standalone server case
> -------------------------------------------------------------------------------
>
>                 Key: WFCORE-3406
>                 URL: https://issues.jboss.org/browse/WFCORE-3406
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Domain Management, Test Suite
>            Reporter: Claudio Miranda
>            Assignee: Chao Wang
>         Attachments: helloworld.war
>
>
> The find-non-progressing-operation operation of /core-service=management/service=management-operations doesn't return the operation id of a blocking operation on standalone. It works on domain mode.
> To simulate the blocking operation, install the BlockingExtension from testsuite and call 
> {code}
> /subsystem=blocker-test:block(block-point=MODEL,block-time=50000}
> {code}
> Open another jboss-cli.sh and call 
> {code}
> /core-service=management/service=management-operations:find-non-progressing-operation
> {code}
> Update: 
> The example above reveals when people manually install BlockingExtension and run in standalone mode, BlockingExtension does not correctly block and count time, as it does not acquire the exclusive lock.
> In domain mode, it acquires the lock by calling [context.readResourceForUpdate|https://github.com/wildfly/wildfly-core/blob/4.0.0.Alpha2/testsuite/shared/src/main/java/org/jboss/as/test/integration/management/extension/blocker/BlockerExtension.java#L163]. This does not affect current test scenarios as the block function is tested in OperationCancellationTestCase under domain mode.  



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)