Subversion Repositories SmartDukaan

Last modification

• Rev 37674 2026-09-17 13:13:15
• Author: amit

• Log message:

  Hold the browser lane around the knowlarity scrapes
  
  These run Chrome inside the tomcat JVM, on the same box as the cron jar's
  oppo/realme imei lane, with nothing coordinating the two. isScraping only guards
  this JVM and cannot see the cron's driver, so the interlock has to be the
  OS-level one -- BrowserLane, common r37672.
  
  Fifteen minutes rather than the cron side's five: the insights scrape runs only
  8 times a day against a lane that is busy ~96% of the time, so a short timeout
  here would mean the insights never refreshed. On contention it serves cache.
  
  The break-log scraper takes the lane around its freshDriver, which has a clean
  try/finally bracket. setupDriver()'s long-lived field driver is deliberately left
  alone -- its lifetime spans init to @PreDestroy and holding an OS lock that long
  would starve the imei lane.