So I have a Tomcat deployment environment and system that handles JMS messages.
Behaviour that I've been seeing is that a conditional breakpoint which HAS to be true is intermittently triggered. This is to say that it's triggered on some test runs but not others. I know it's true at least once in all test runs though because afterwards I can see the result in the database. The break point conditional is a particular recordId and if I can see that the record is copied to the target table, then I know it went through the code path in question. There is some chaining to get to it but none of those items can possibly be null without causing big noticable problems earlier in the code. Note that there's no indication of an error, i.e. there is no red underline and the block of code is green.
Conditional looks like this: something.getSomethingelse().getSomeEntityFieldOfStringType().equals("SOMERECORDID")
Question: What would happen to the breakpoint evaluation if something.getSomethingelse() took a long time?
Has anyone else seen this behaviour or know anything about it?
For the record, I have not one but two licenses. One from work for my current contract and one for when the org I'm working for uses Eclipse and won't provide a license.