Ok, so I went over to EC2 and launched up a 48 core m5d.12xlarge machine. Very interestingly, I got 3 failures from this example. Ran it again and got 1 failure.
There appears to be a race condition. A bit too early to say what conditions lead to it, but it appears to surface when bean validation composition is used -- one annotation reuses another annotation. Seems to indicate a result is returned before the other constraint executes. I'm going to see if I can reproduce with a plain bean validation example. -- David Blevins http://twitter.com/dblevins http://www.tomitribe.com > On May 16, 2019, at 5:47 PM, David Blevins <[email protected]> wrote: > > Not quite sure what the issue is with that test. It runs and passes locally. > > Trying on another machine to see if I can reproduce. > > > -- > David Blevins > http://twitter.com/dblevins > http://www.tomitribe.com > >> On May 15, 2019, at 11:01 PM, Jonathan Gallimore >> <[email protected]> wrote: >> >> Awesome, thanks! Sounds like its related to the JWT work. If I get a chance >> at some point today I'll try and take a look to try and help out. >> >> On Wed, May 15, 2019 at 2:56 PM j4fm <[email protected]> wrote: >> >>> Apache TomEE + MicroProfile JWT Bean Validation, Strongly-typed Annotations >>> 1.0-SNAPSHOT >>> mp-jwt-bean-validation-strongly-typed >>> >>> >>> >>> -- >>> Sent from: >>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html >>> >
