Arbotext Publishing Engine Programmer's Guide (《Arbortext Publishing Engine 程序员指南》) > The Arbortext Publishing Engine Request Manager > Understanding the Internal Structure of Arbortext PE Request Manager > Arbortext PE 子进程 Pool Management > Arbortext PE 子进程 Deallocation
  
Arbortext PE 子进程 Deallocation
Once it has been allocated to a dynamic component, an Arbortext PE 子进程 can only be used by the code that allocated it. To release the Arbortext PE 子进程, the component that called the allocate method must subsequently call the com.arbortext.e3.E3Subprocess.deallocate method. To ensure the Arbortext PE 子进程 is released, placing thedeallocate call inside the finally block, which releases it regardless of any exceptions that might be thrown in the try block.
Deallocation is not optional. If a dynamic component fails to deallocate an Arbortext PE 子进程, the Arbortext PE 子进程 will never become usable for other purposes.