Both programming models let you create pooled and daemon threads to run J2EE business logic.
两种编程模式都允许您创建池线程和守护程序线程，以便运行J2EE业务逻辑。
All threads in a component-scoped thread pool are asynchronous bean daemon threads and have the same lifecycle of the application that created it.
组件范围的线程池中的所有线程都是异步bean守护程序线程，并且具有与创建它的应用程序相同的生命周期。
All threads that are not daemon threads have died, either by returning from the call to the run method or by throwing an exception that propagates beyond the run method.
非守护线程的所有线程都已停止运行，无论是通过从对run方法的调用中返回，还是通过抛出一个传播到run方法之外的异常。
While biod self-tunes the number of threads (the daemon process creates and kills threads as needed), the maximum number of biod threads can be tuned, depending on the overall load.
当biod自我优化线程数量(该守护进程根据需要创建和删除线程)时，可以根据整体负载，对biod线程的最大数目进行优化。
While biod self-tunes the number of threads (the daemon process creates and kills threads as needed), the maximum number of biod threads can be tuned, depending on the overall load.
当biod自我优化线程数量(该守护进程根据需要创建和删除线程)时，可以根据整体负载，对biod线程的最大数目进行优化。
应用推荐