Timeout in Bootstrap Phase 1 step 2 - BBOU0713W
 Technote (FAQ)
 
Problem
Timeout in Bootstrap Phase 1 step 2, message given:
msgBBOU0713W THE TRANSACTION WITH URID ....... HAS TIMED OUT AFTER PROCESSING FOR MORE THAN 300 SECONDS...
 
 
Solution
Problem:
See Abstract.

Possible Solution:
- Make sure there aren’t any unnecessary traces on (ex. TRACEALL=3 instead of 1). In addition to creating lots of trace entries and taking up spool space. it slows things down.

- Make sure there are no negative SQL errors in the WebSphere logstream error log indicating a problem accessing DB2.

- Increase the environment variables OTS_DEFAULT_TIMEOUT and OTS_MAXIMUM_TIMEOUT from the default of 300 to 1800. The system might not have been getting enough CPU cycles which could've contributed to 300 second not being enough. During this step, lots of WebSphere runtime objects are being created and stored in DB2. All of these objects are being created under one transaction, thus, depending on your system and system workload, it may take longer than the default 300 seconds to run.
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > System Management/Repository
Operating system(s): OS/390
Software version: 4.0.1
Software edition:
Reference #: 1050643
IBM Group: Software Group
Modified date: Mar 25, 2002