If the application was invoked by a short-running request, when it terminates, whether normally or due to a run-time system
error occurring, the application container returns itself to its initial state before a response is generated and sent back
to the client.
Normally, having sent a response back to the client, the service execution process waits for the enterprise server to notify
it to process another request. However, there are some circumstances where the service execution process is terminated following
the execution of an application:
- The integrity of the container has been compromised in some way (for example, a run-time system error, such as a 114 error,
occurred or an executable file loaded by the application could not be unloaded; etc.).
- You unchecked Reuse container after application termination on the Deployment Characteristics tab of the Enterprise Server Run-time Configuration dialog box before you deployed the
service. You should uncheck this if the application is likely to leave the application container in a state that will compromise
its ability to be safely reused, for example, if your application is mixed-language and the non-COBOL modules do not clean
up resources before the application terminates.
- You unchecked Reuse container after non-fatal run-time system error on the Deployment Characteristics tab of the Enterprise Server Run-time Configuration dialog box before you deployed the
service, and the application has terminated due to a non-fatal run-time system error (for example. 173 error "Program not
found"). You should uncheck this if you decide that any run-time error that occurs while running the application indicates
a major failure that compromises the integrity of the container.
When such a circumstance occurs, the enterprise server will start a new service execution process to replace the one just
terminated.