My Oracle Support Banner

The "tmboot" with -p Argument for Parallel Boot up Causes Stderr Stdout to be Written to cwd/stderr and cwd/stdout and App Server Crashes when Writing to Them (Doc ID 2887399.1)

Last updated on NOVEMBER 22, 2023

Applies to:

Oracle Tuxedo - Version 12.2.2 and later
Information in this document applies to any platform.


The stdout/stderr output from app servers started with tmboot is written to cwd/stdout cwd/stderr.

If the app server is started with tmboot -p option for parallel booting, stdin/stdout/stderr handles are inherited from staring process causing that a Service when writing data to stderr gets terminated with SIGPIPE if stderr is connected to terminated process.

Below test cases describe successful scenarios and the failing scenario in Test Case 3.

Test Case 1 (No issue):

Boot the domain as normal with tmboot -y command and the .err and .out are shown as fd of the server process ID.





To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.