org.jboss.as.test.integration.beanvalidation.hibernate.validator.BootStrapValidationTestCase

java.lang.AssertionError: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0216: Management resource '[ (\"subsystem\" => \"batch-jberet\"), (\"jdbc-job-repository\" => \"batch-ds\") ]' not found"}}

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

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

Solutions on the web2

  • via GitHub by wildfly-ci
    , 11 months ago
    java.lang.AssertionError: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0216: Management resource '[ (\"subsystem\" => \"batch-jberet\"), (\"jdbc-job-repository\" => \"batch-ds\") ]' not found"}}
  • via GitHub by wildfly-ci
    , 11 months ago
    java.lang.AssertionError: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0216: Management resource '[ (\"subsystem\" => \"batch-jberet\"), (\"jdbc-job-repository\" => \"batch-ds\") ]' not found"}}
  • Stack trace

    • org.jboss.as.test.integration.beanvalidation.hibernate.validator.BootStrapValidationTestCase: java.lang.AssertionError: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0216: Management resource '[ (\"subsystem\" => \"batch-jberet\"), (\"jdbc-job-repository\" => \"batch-ds\") ]' not found"}} at org.jboss.as.test.integration.batch.deployment.DeploymentDescriptorTestCase$JdbcJobRepositorySetUp.execute(DeploymentDescriptorTestCase.java:202) at org.jboss.as.test.integration.batch.deployment.DeploymentDescriptorTestCase$JdbcJobRepositorySetUp.tearDown(DeploymentDescriptorTestCase.java:190) at org.jboss.as.arquillian.container.ServerSetupObserver.handleAfterUndeploy(ServerSetupObserver.java:166)

    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

    You’re the first here who have seen this exception.