[JBoss JIRA] (SWSQE-48) Test Service Mesh's
by Matt Mahoney (JIRA)
[ https://issues.jboss.org/browse/SWSQE-48?page=com.atlassian.jira.plugin.s... ]
Matt Mahoney updated SWSQE-48:
------------------------------
Sprint: SWS QE Sprint 2
> Test Service Mesh's
> -------------------
>
> Key: SWSQE-48
> URL: https://issues.jboss.org/browse/SWSQE-48
> Project: Swift Sunshine QE
> Issue Type: Task
> Reporter: Matt Mahoney
> Assignee: Michael Foley
>
> "As a SWS UI developer I want to make sure that we can visualize various different network topology meshes in the service graph"
> "As a SWS backend developer I want to make sure that we can generate correct JSON from various network topology meshes"
> We need to be able to quickly and easily deploy a bunch of different network topography examples in various namespaces in OpenShift/K8S for testing purposes.
> There are a bunch of different posible combinations of how things can be arranged and we need to be able to verify that they are render correctly in our UI and that our backend JSON is generating them correctly.
> We should be able to easily just generate these different types of setups by deploying a template in a namespace.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (SWSQE-48) Test Service Mesh's
by Matt Mahoney (JIRA)
Matt Mahoney created SWSQE-48:
---------------------------------
Summary: Test Service Mesh's
Key: SWSQE-48
URL: https://issues.jboss.org/browse/SWSQE-48
Project: Swift Sunshine QE
Issue Type: Task
Reporter: Matt Mahoney
Assignee: Michael Foley
"As a SWS UI developer I want to make sure that we can visualize various different network topology meshes in the service graph"
"As a SWS backend developer I want to make sure that we can generate correct JSON from various network topology meshes"
We need to be able to quickly and easily deploy a bunch of different network topography examples in various namespaces in OpenShift/K8S for testing purposes.
There are a bunch of different posible combinations of how things can be arranged and we need to be able to verify that they are render correctly in our UI and that our backend JSON is generating them correctly.
We should be able to easily just generate these different types of setups by deploying a template in a namespace.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9941) :shutdown cli operation throws java.util.concurrent.CancellationException: Operation was cancelled
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9941?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-9941:
----------------------------------------
If you are using the CLI do not use the low level ':shutdown' operation, use the high level 'shutdown' command. It's analogous to "do not use the low level ':reload' operation, use the high level 'reload' command."
> :shutdown cli operation throws java.util.concurrent.CancellationException: Operation was cancelled
> --------------------------------------------------------------------------------------------------
>
> Key: WFLY-9941
> URL: https://issues.jboss.org/browse/WFLY-9941
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 12.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Jean-Francois Denise
> Attachments: manu-trace.log
>
>
> There is intermittent failure on CLI client when CLI operation {{ :shutdown() }} is called. Sometimes happens that CancellationException is thrown:
> {code}
> 2018-03-01 09:36:59,188 ERROR pool-1-thread-1 org.jboss.manu.eap.services.server.EapModularServerBase - Can't stop server gracefully
> java.io.IOException: java.util.concurrent.CancellationException: Operation was cancelled
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
> at org.wildfly.extras.creaper.core.online.OnlineManagementClientImpl.execute(OnlineManagementClientImpl.java:180) ~[creaper-core-1.6.1.jar:na]
> at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:600) ~[manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:638) ~[manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.eap.services.server.EapServerStandalone.executeStopOperation(EapServerStandalone.java:348) ~[manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.eap.services.server.EapModularServerBase.stop(EapModularServerBase.java:238) ~[manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.eap.units.server.StopServer.execute(StopServer.java:57) [manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:33) [manu-core-impl-1.1.43.jar:na]
> at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:14) [manu-core-impl-1.1.43.jar:na]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_151]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151]
> at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]
> Caused by: java.util.concurrent.CancellationException: Operation was cancelled
> at org.jboss.threads.AsyncFutureTask.operationCancelled(AsyncFutureTask.java:70) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final]
> at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:267) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final]
> at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:57) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
> ... 13 common frames omitted
> {code}
> WF12 server shutdowns but it seems that it does not send response for {{:shutdown}} call to client before shutdwon and closes connection. This causes that AsyncFutureTask on client is cancelled.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months