anchor.diff:  Whether you're using {vertx-launcher}[Launcher] (which has supplanted Starter) or the Vert.x CLI, pass the following VM argument:
   
   ```java
  --Dvertx.options.maxEventLoopExecuteTime=200000000 // <1>
  +-Dvertx.options.blockedThreadCheckPeriod=200000000 // <1>
   ```
   <1> Some sufficiently large integer (milliseconds).
   
  
positive.code: 
  == Caveats & Conclusion
  
  It's worth remembering that by halting executing thread(s) in the debugger you may not encounter timing-related issues you otherwise would. So, it is wise to ensure you aren't altering `maxEventLoopExecuteTime` unless you really need to.
  
  Needless to say, seeing BlockedThreadChecker warnings in production is a symptom of pathological code behaviour, indicating that the event loop is being blocked for excessive periods; you should fix it rather than altering timeouts.
  
  
negative.code: 
  *IntelliJ* Edit Configurations -> Select Application -> Configuration -> VM Options
  
  TIP: Setting blockedThreadCheckPeriod via system properties is likely the best approach; avoiding debug-specific behaviour leaking into your code.
  
  === Directly in VertxOptions
  
  