Arbotext Publishing Engine Programmer's Guide (《Arbortext Publishing Engine 程序员指南》) > The Arbortext Publishing Engine Request Manager > Understanding the Internal Structure of Arbortext PE Request Manager > Terminating the Arbortext PE Request Manager
  
Terminating the Arbortext PE Request Manager
The Arbortext PE Request Manager servlet terminates when the servlet container calls the method com.arbortext.e3.E3servlet.destroy. The Arbortext PE Request Manager passes the termination request to each Arbortext PE 子进程 pool, and each pool sends a signal to every running Arbortext PE 子进程. Idle Arbortext PE 子进程 terminate silently. Allocated busy Arbortext PE 子进程 return an error to the calling thread in the Arbortext PE Request Manager, which is returned to the requesting client. If an Arbortext PE 子进程 is allocated but not yet busy, an error is returned immediately when it starts processing.
Each pool work thread waits for Arbortext PE 子进程 to terminate so it can delete their temporary directories. If all Arbortext PE 子进程 have not terminated before the time configured by the pool's maxShutdownInterval attribute (explained in The maxShutdownInterval Attribute), the work thread terminates, leaving some temporary storage still allocated.