Hi I will take a look. That’s probably a race condition with the broker service.
Regards JB > Le 5 oct. 2021 à 21:21, Miguel Anzo Palomo <miguel.a...@wizeline.com> a écrit > : > > > Hi, I've been working on checking out why is this issue happening (flaky test > in JmsIO). The logs in this example indicate that the problem is a > NullPointerException, specifically in this receiveNoWait() operation at this > line of the test. The only way I see that a NullPointerException is being > caused there, is if the consumer is closed at that point, and the only way I > have been able to reproduce a NullPointerException locally in the lines > mentioned in the log is by closing the consumer before that read operation. > > My idea right now is that there could be some intermittency with ActiveMQ > that caused the flaky test at that moment, is there a way to know if that was > the case? Right now I only have two known instances of the flake, this one on > August 23, and another one on September 9 (that jenkins link is no longer > available). From what I’ve been told it is running on the cloud compute > instance apache-ci-beam-jenkins. > > Thanks > > -- > Miguel Angel Anzo Palomo | WIZELINE > Software Engineer > miguel.a...@wizeline.com > Remote Office > > This email and its contents (including any attachments) are being sent to > you on the condition of confidentiality and may be protected by legal > privilege. Access to this email by anyone other than the intended recipient > is unauthorized. If you are not the intended recipient, please immediately > notify the sender by replying to this message and delete the material > immediately from your system. Any further use, dissemination, distribution > or reproduction of this email is strictly prohibited. Further, no > representation is made with respect to any content contained in this email.
