[
https://issues.jboss.org/browse/WFCORE-923?page=com.atlassian.jira.plugin...
]
Filippe Spolti commented on WFCORE-923:
---------------------------------------
Hi, sometimes I getting this:
{code:shell}
[standalone@localhost:9999 /]
/core-service=management/service=management-operations:find-non-progressing-operation
{
"outcome" => "success",
"result" => "-340841891"
}
[standalone@localhost:9999 /]
/core-service=management/service=management-operations/active-operation=-340841891:read-resource
{
"outcome" => "success",
"result" => {
"access-mechanism" => "undefined",
"address" => [],
"caller-thread" => "management-handler-thread - 1",
"cancelled" => false,
"exclusive-running-time" => 205574507121L,
"execution-status" => "executing",
"operation" => "composite",
"running-time" => 205575446309L
}
}
{code}
Seems the blocking-timeout does not take effect on those kind of operations, there is a
way to terminate long running management operations of any kind?
This behaviour leads the thread in the waiting tatus:
"main" #1 prio=5 os_prio=0 tid=0x00007f22f0009800 nid=0x78d9 in Object.wait()
[0x00007f22f7e19000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at org.jboss.threads.AsyncFutureTask.await(AsyncFutureTask.java:192)
- locked <0x000000079899cba8> (a
org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl)
at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:266)
- locked <0x000000079899cba8> (a
org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl)
Thanks.
PS, it is EAP 6.4.5
Execution timeout for CLI operations
------------------------------------
Key: WFCORE-923
URL:
https://issues.jboss.org/browse/WFCORE-923
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Affects Versions: 2.0.0.Beta4
Reporter: Lyle Wang
Assignee: Alexey Loubyansky
Labels: cli, timeout
It will be great if we could have a timeout setting to
"stop-the-CLI-execution-after-nnn-seconds" , for all general CLI operations.
Specifically, during some CLI operations, for example "deploy" or
"reload", it is possible that things get stuck and hang-up, CLI cannot get back
/ return to the user after a long waiting. In this case, if we're able to setup an
"execution timeout" and let CLI return with an error message, that would be much
better. User should be able to know command execution results by viewing the related logs
or checking the status.
Currently there is "--timeout" setting when running "jboss-cli.sh",
but that seems only effective on "connect" operation, tried to use this timeout
with a CLI script file, which has "deploy" inside (./jboss-cli.sh
--file=test.cli --timeout=xxx), it doesn't work when the deployment takes a long time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)