Sessionmanager.isSessionActive() is executed in a loop
Issue #570
resolved
I added one line to the method
LOG.warn("checking " + sessionFile.getAbsolutePath() + " " + sessionFile.exists());
resulting in this output :
12:39:31.117 [qtp1859118601-21 - //localhost:4567/opstatus] WARN - checking /Users/advanced/.nubot/NuBot_session.tmp true [c.n.n.l.MainLaunch:172]
12:39:31.140 [qtp1859118601-23 - //localhost:4567/opstatus] WARN - checking /Users/advanced/.nubot/NuBot_session.tmp true [c.n.n.l.MainLaunch:172]
12:39:31.549 [qtp1859118601-22 - //localhost:4567/opstatus] WARN - checking /Users/advanced/.nubot/NuBot_session.tmp true [c.n.n.l.MainLaunch:172]
12:39:31.572 [qtp1859118601-21 - //localhost:4567/opstatus] WARN - checking /Users/advanced/.nubot/NuBot_session.tmp true [c.n.n.l.MainLaunch:172]
12:39:32.050 [qtp1859118601-22 - //localhost:4567/opstatus] WARN - checking /Users/advanced/.nubot/NuBot_session.tmp true [c.n.n.l.MainLaunch:172]
12:39:32.071 [qtp1859118601-21 - //localhost:4567/opstatus] WARN - checking /Users/advanced/.nubot/NuBot_session.tmp true [c.n.n.l.MainLaunch:172]
12:39:32.287 [qtp1859118601-28 - //localhost:4567/opstatus] WARN - checking /Users/advanced/.nubot/NuBot_session.tmp true [c.n.n.l.MainLaunch:172]
12:39:32.305 [qtp1859118601-23 - //localhost:4567/opstatus] WARN - checking /Users/advanced/.nubot/NuBot_session.tmp true [c.n.n.l.MainLaunch:172]
12:39:32.317 [qtp1859118601-22 - //localhost:4567/opstatus] WARN - checking /Users/advanced/.nubot/NuBot_session.tmp true [c.n.n.l.MainLaunch:172]
12:39:32.327 [qtp1859118601-23 - //localhost:4567/opstatus] WARN - checking /Users/advanced/.nubot/NuBot_session.tmp true [c.n.n.l.MainLaunch:172]
12:39:32.552 [qtp1859118601-22 - //localhost:4567/opstatus] WARN - checking /Users/advanced/.nubot/NuBot_session.tmp true [c.n.n.l.MainLaunch:172]
for some reason this function is called up to 7 times per second ?
Comments (3)
-
reporter -
reporter - changed status to resolved
-
reporter - changed milestone to 0.3.0 - UI
- Log in to comment
This is caused by the UI calling opstatus continuously!