What additional information can be provided about the Gen 8.6 CFB Server tracing output?
The tracing output will contain information from several threads:
[main] - this is the CFB Server's main thread. This thread should remain active until the CFB Server is shutdown.
[Control[control port #]] - this is the listener thread for incoming requests from the Control client. This thread should remain active until the CFB Server is shutdown.
[Listener[listener port #]] - this is the listener thread for incoming requests from the application clients. There could be multiple of these listener threads depending upon the listen.ports value in the CFBServer.properties file. These threads should remain active until the CFB Server is shutdown.
[Thread-#] - this is the thread used to process requests from application clients. This thread performs the RMI call to the EJB. There could be multiple of these threads depending upon the volume of incoming application clients. These threads should remain active until the CFB Server is shutdown, unless they are ended due to certain error conditions.
[XC[listener port #:application client port #]] - this is the worker thread that does the work of reading/writing the request/response from/to the application client. These threads should go away when the application client closes, but can be impacted by the connection_persistence flag in the commcfg.ini file. If the connection_persistence flag is not specified (e.g., TCP localhost 8901), then the connection will be persistent and this thread will not go away until the application client closes. If the connection_persistence flag is set to N (e.g., TCP localhost 8901 N), then the connection will not be persistent and this thread will go away at the end of each application client transaction.
So, in general, see the [main], [Control[control port #]], [Listener[listener port #]], and [Thread-#] threads created upon CFB Server startup. Additionally, find other [Thread-#] threads created as the volume of incoming application client requests increases. Also, it can be found that the [XC[listner port #:application client port #]] threads are created and destroyed as application client requests are processed.