com.ibm.etools.iseries.subsystems.qsys.api
Class SystemCommunicationsDaemon.CommunicationHandlerThread
java.lang.Object
java.lang.Thread
com.ibm.etools.iseries.subsystems.qsys.api.SystemCommunicationsDaemon.CommunicationHandlerThread
- All Implemented Interfaces:
- Runnable
- Enclosing class:
- SystemCommunicationsDaemon
protected class SystemCommunicationsDaemon.CommunicationHandlerThread
- extends Thread
Inner class for running ICommunicationHandlers on a new thread. This is done
for two main reasons:
1. Allow the communication daemon to continue handling requests while
processing other requests (this is important because some requests
like the program verifiers run long.
2. Keep the communications daemon safe from crashes (unhandled exceptions)
in the communication handlers.
Method Summary |
void |
run()
|
Methods inherited from class java.lang.Thread |
activeCount, checkAccess, countStackFrames, currentThread, destroy, dumpStack, enumerate, getAllStackTraces, getContextClassLoader, getDefaultUncaughtExceptionHandler, getId, getName, getPriority, getStackTrace, getState, getThreadGroup, getUncaughtExceptionHandler, holdsLock, interrupt, interrupted, isAlive, isDaemon, isInterrupted, join, join, join, resume, setContextClassLoader, setDaemon, setDefaultUncaughtExceptionHandler, setName, setPriority, setUncaughtExceptionHandler, sleep, sleep, start, stop, stop, suspend, toString, yield |
SystemCommunicationsDaemon.CommunicationHandlerThread
protected SystemCommunicationsDaemon.CommunicationHandlerThread(ISystemCommunicationsDaemonHandler handler,
Socket socket,
int requestKey)
run
public void run()
- Specified by:
run
in interface Runnable
- Overrides:
run
in class Thread
Copyright © 2011 IBM Corp. All Rights Reserved.
Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.