Hi if you can share some jstack dump in the "slow" period it could help to tackle that. Also maybe try previous releases - know they fixed some inheritance bugs so maybe they added some overhead by side effect. Bean validation scanning should be limited to CDI during startup so same tricks as for CDI should work.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2016-02-24 18:11 GMT+01:00 Gropp Volker <[email protected]>: > Hi, > > we are upgrading our openejb-based unit-tests of a fairly large JEE-app to > OpenEjb 7.0.0-M1 and I noticed a very slow startup while scanning all > classes for Bean Validation with Hibernate Validator 5 5.2.2.Final. Is > there any way to limit classes/packages which are scanned by Hibernate > Validator or to disable it completely (in our tests)? Maybe this is not a > problem solely in 7.0.0-M1, but I noticed it because of lot of > warnings/errors while starting up the container. > > Regards, > > Volker Gropp >
