anchor.diff:  
   ```java
   VertxOptions vxOptions = new VertxOptions()
  -	.setblockedThreadCheckPeriod(200000000); // <1>
  +	.setblockedThreadCheckInterval(200000000); // <1>
   Vertx myVertx = Vertx.vertx(vxOptions); // <2>
   ```
   <1> Set interval in `VertxOptions`.
  
positive.code: 
  The exceptions occur because the interactive debugger repeatedly _halts the event loop thread_ while you use it: browsing around, poking at variables, stepping through your program, etc. The length of time it takes to execute the event being debugged will be drastically longer than normal; hence the watchdog starts barking.
  
  Mercifully there's a simple solution, which involves setting `blockedThreadCheckPeriod` to a sufficiently long time. footnote:[Had this as maxEventLoopExecuteTime in a previous revision of the blog, but this doesn't work consistently.]
  
  [IMPORTANT]
  .The following should only be used for debugging purposes!
  
negative.code: 
  *IntelliJ* Edit Configurations -> Select Application -> Configuration -> VM Options
  
  TIP: Setting blockedThreadCheckInterval via system properties is likely the best approach; avoiding debug-specific behaviour leaking into your code.
  
  === Directly in VertxOptions
  
  