Class BuildExecutor

  • All Implemented Interfaces:

    class BuildExecutor
    extends Object
    implements Runnable
    Single threaded controller of the tunnel creation process, spanning all tunnel pools. Essentially, this loops across the pools, sees which want to build tunnels, and fires off the necessary activities if the load allows. If nothing wants to build any tunnels, it waits for a short period before looping again (or until it is told that something changed, such as a tunnel failed, new client started up, or tunnel creation was aborted). Note that 10 minute tunnel expiration is hardcoded in here. As of 0.8.11, inbound request handling is done in a separate thread.
    • Method Detail

      • restart

        public void restart()
      • shutdown

        public void shutdown()
        Cannot be restarted.
      • run

        public void run()
        Specified by:
        run in interface Runnable
      • isRunning

        public boolean isRunning()
      • buildComplete

        public void buildComplete​(PooledTunnelCreatorConfig cfg)
        This wakes up the executor, so call this after TunnelPool.addTunnel() so we don't build too many.
      • wasRecentlyBuilding

        public boolean wasRecentlyBuilding​(long replyId)
      • repoll

        public void repoll()
      • removeFromBuilding

        PooledTunnelCreatorConfig removeFromBuilding​(long id)
        This returns the PTCC up to a minute after it 'expired', thus allowing us to still use a tunnel if it was accepted, and to update peer stats. This means that manager.buildComplete() could be called more than once, and a build can be failed or successful after it was timed out, which will affect the stats and profiles. But that's ok. A peer that rejects slowly gets penalized twice, for example.
        ptcc or null