Uploaded image for project: 'Thorntail'
  1. Thorntail
  2. THORN-656

Stopping WF-Swarm shows ERROR in log: because no Bean Validation provider could be found

    Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 2016.8
    • Fix Version/s: 2016.9
    • Component/s: None
    • Labels:
      None

      Description

      When I stop WF-Swarm using ctrl + c to quit the JVM then I get an error in the LOG (red color).

      I have a basic Camel with WF-Swarm example here
      https://github.com/camelinaction/camelinaction2/tree/master/chapter7/wildfly-swarm-spring

      This example only uses Spring and not CDI etc.
      And notice how the pom.xml only uses a few WF fragments.

      I wonder if the ERROR logging with stacktrace, can be made a WARN and with no stacktrace? Or maybe the logic can better detect if a javax validator is on the classpath or not.

      2016-09-03 16:16:08,146 INFO  [org.apache.camel.spring.SpringCamelContext] (MSC service thread 1-8) Apache Camel 2.17.2 (CamelContext: camel-1) is shutdown in 0.016 seconds
      2016-09-03 16:16:08,150 ERROR [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0043: Deployment unit processor org.jboss.as.ee.beanvalidation.BeanValidationFactoryDeployer@697ecfc0 unexpectedly threw an exception during undeploy phase POST_MODULE of deployment "hello-spring.war": javax.validation.ValidationException: Unable to create a Configuration, because no Bean Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath.
             	at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:271)
             	at org.jboss.as.ee.beanvalidation.LazyValidatorFactory.initFactory(LazyValidatorFactory.java:80)
             	at org.jboss.as.ee.beanvalidation.LazyValidatorFactory.getDelegate(LazyValidatorFactory.java:58)
             	at org.jboss.as.ee.beanvalidation.LazyValidatorFactory.close(LazyValidatorFactory.java:126)
             	at org.jboss.as.ee.beanvalidation.BeanValidationFactoryDeployer.undeploy(BeanValidationFactoryDeployer.java:120)
             	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:272)
             	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:230)
             	at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
             	at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
             	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
             	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
             	at java.lang.Thread.run(Thread.java:745)
      
      2016-09-03 16:16:08,155 INFO  [org.jboss.gravia.runtime] (MSC service thread 1-4) Runtime released: org.wildfly.extension.gravia.service.WildFlyRuntime@4af20e30
      2016-09-03 16:16:08,216 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment hello-spring.war (runtime-name: hello-spring.war) in 122ms
      2016-09-03 16:16:08,221 INFO  [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: WildFly Core 2.0.10.Final "Kenny" stopped in 126ms
      

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                gastaldi George Gastaldi
                Reporter:
                davsclaus Claus Ibsen
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: