Uploaded image for project: 'WildFly Arquillian'
  1. WildFly Arquillian
  2. WFARQ-187

CommonManagedDeployableContainer.stopInternal should handle a 'caused by' CancellationException from the 'shutdown' op

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 5.1.0.Beta5
    • None
    • None

      My WFARQ-181 fix was wrong – ok conceptually but doesn't really solve the problem.

      This is the stack trace it was attempting to handle:

      Caused by: java.io.IOException: java.util.concurrent.CancellationException: JBTHR00004: Operation was cancelled
	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:135)
	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:61)
	at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.execute(DelegatingModelControllerClient.java:52)
	at org.jboss.as.arquillian.container.CommonManagedDeployableContainer.stopInternal(CommonManagedDeployableContainer.java:202)
	... 155 more
Caused by: java.util.concurrent.CancellationException: JBTHR00004: Operation was cancelled
	at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:251)
	at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:40)
	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:133)
	... 158 more

      As you can see, CommonManagedDeployableContainer.stopInternal L202 was resulting in an IOException that's caused by a CancellationException. So a catch block for a CancellationException doesn't do anything.

            bstansbe@redhat.com Brian Stansberry
            bstansbe@redhat.com Brian Stansberry
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: