List of usage examples for java.lang Thread subclass-usage
From source file com.glaf.core.startup.DBNativeCmdThread.java
public class DBNativeCmdThread extends Thread { protected final static Log logger = LogFactory.getLog(DBNativeCmdThread.class); protected String cmd;
From source file com.karpenstein.signalmon.NetConnHandler.java
/**
* Protocol: client throttles data by sending ticks (1 char 'G')
* sends 'S' to disconnect.
* on each receipt of the G, this sends the current state if it has changed, otherwise it sends {}.
*
* JSON Object: dataActivity int
From source file com.comcast.video.dawg.show.key.SendKeyThread.java
/** * Thread that sends a key to a device. This is so we can send keys to multiple devices in parallel * @author Kevin Pearson * */ public class SendKeyThread extends Thread {
From source file com.twitlinks.parser.Parser.java
/** * @author raunak * @version 1.0 */ public class Parser extends Thread { /**
From source file org.apache.roller.weblogger.business.runnable.WorkerThread.java
/** * A generic worker thread that knows how execute a Job. */ public class WorkerThread extends Thread { private static Log log = LogFactory.getLog(WorkerThread.class);
From source file org.huahinframework.manager.queue.RunHiveQueue.java
/** * */ public class RunHiveQueue extends Thread { private static final Log log = LogFactory.getLog(RunHiveQueue.class);
From source file pipeserver.Data.java
public class Data extends Thread implements ClientData, PoolableObject { private static Logger logger = Logger.getLogger(Data.class.getName()); private Socket socket; private ClientHandler handler; private BufferedInputStream bin;
From source file com.symbian.driver.core.processors.EmulatorPostProcessor.java
/** * @author EngineeringTools * */ public class EmulatorPostProcessor extends Thread implements PostProcessor {
From source file com.ksc.http.IdleConnectionReaper.java
/**
* Daemon thread to periodically check connection pools for idle connections.
* <p/>
* Connections sitting around idle in the HTTP connection pool for too long will
* eventually be terminated by the AWS end of the connection, and will go into
* CLOSE_WAIT. If this happens, sockets will sit around in CLOSE_WAIT, still