org.jboss.as.test.integration.domain.management.cli.CloneProfileTestCase

org.jboss.as.test.integration.domain.management.cli.DomainDeployWithRuntimeNameTestCase.testDeployWithDifferentRuntimeNameOnDifferentServerGroup: java.lang.AssertionError: Failed to execute line 'deploy --server-groups=main-server-group /opt/buildAgent/work/a31d203e70e89f90/testsuite/domain/target/HelloServlet.war --runtime-name=SimpleServlet.war --name=simple1': org.jboss.as.cli.CommandFormatException: The command is not available in the current context (e.g. required subsystems or connection to the controller might be unavailable).

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web3

  • via GitHub by wildfly-ci
    ,
  • via GitHub by wildfly-ci
    ,
  • via GitHub by wildfly-ci
    ,
  • Stack trace

    • org.jboss.as.test.integration.domain.management.cli.CloneProfileTestCase: org.jboss.as.test.integration.domain.management.cli.DomainDeployWithRuntimeNameTestCase.testDeployWithDifferentRuntimeNameOnDifferentServerGroup: java.lang.AssertionError: Failed to execute line 'deploy --server-groups=main-server-group /opt/buildAgent/work/a31d203e70e89f90/testsuite/domain/target/HelloServlet.war --runtime-name=SimpleServlet.war --name=simple1': org.jboss.as.cli.CommandFormatException: The command is not available in the current context (e.g. required subsystems or connection to the controller might be unavailable). at org.jboss.as.test.integration.management.util.CLIWrapper.sendLine(CLIWrapper.java:165) at org.jboss.as.test.integration.management.util.CLIWrapper.sendLine(CLIWrapper.java:187) at org.jboss.as.test.integration.domain.management.cli.DomainDeployWithRuntimeNameTestCase.testDeployWithDifferentRuntimeNameOnDifferentServerGroup(DomainDeployWithRuntimeNameTestCase.java:130)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.