anchor.diff:  
   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 `maxEventLoopExecuteTime` to a sufficiently long time.
  +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!
  
positive.code: 
  *IntelliJ* Edit Configurations -> Select Application -> Configuration -> VM Options
  
  TIP: Setting maxEventLoopExecuteTime via system properties is likely the best approach; avoiding debug-specific behaviour leaking into your code.
  
  === Directly in VertxOptions
  
  
negative.code: Whether you're using {vertx-launcher}[Launcher] (which has supplanted Starter) or the Vert.x CLI, pass the following VM argument:
  
  ```java
  -Dvertx.options.blockedThreadCheckPeriod=200000000 // <1>
  ```
  <1> Some sufficiently large integer (milliseconds).
  
  