Tolerance of slow App Server boot January 22, 2008
Posted by Duncan in Infrastructure, Oracle, PeopleSoft, PeopleTools, PS Admin, Tuxedo.trackback
In one of the more recent versions of Tools (8.49 is the first time I’ve noticed it, but that doesn’t mean it hasn’t been around in prior versions) I’ve noticed that occasionally the boot of an Application Server will fail with an error.
Booting admin processes ...
exec BBL -A :
CMDTUX_CAT:1863: INFO: Process ID=2636 Assume failed (timeout).
At the time of writing, there is nothing in Customer Connection for this, and a google search wasn’t particularly helpful either. So I had to resort to a technique from pre-Google days – i.e. work it out myself. Thankfully it wasn’t too difficult.
The config setting we’re after is TM_BOOTTIMEOUT at by default it is 60 seconds. This can be changed in psappsrv.ubx (which serves as a template for the App Server config). Scroll to the bottom and look for:
# ----------------------------------------------------------------------
*PS_ENVFILE
TM_BOOTTIMEOUT=60
TM_RESTARTSRVTIMEOUT=60
TM_BOOTPRESUMEDFAIL=Y
The line in Red is the one which requires changing, I’ve set mine to 120 seconds. Reconfigure your App Server (you don’t have to make any changes, it just needs to re-read the UBX file) and you’re good to go. If you have doubts as to whether it’s picked up the altered value, look in the TUXLOG.xxxxxx file in your App Server logs directory. The TM_BOOTTIMEOUT is logged there every time you boot an App Server.
Comments
Sorry comments are closed for this entry
The PeopleSoft Tipster Blog 
I have not came across this yet but it is good to know a solution exist just in case!
Note: Davies, I have sent you an email, did you get it?
Yes, you should have a reply by now.
Interesting…
thanks for sharing it.
Something new that I learned today!
THANK U VERYMUCH SHARE UR IDEAS I FEEL PROUD
Thanks for your sharing this infor.
I’m getting same error as above but my settings already setup for TM_BOOTTIMEOUT=120. It still fails for me
Shobna,
I guess the first thing is to increment it even further and make sure it does boot (eventually). Once you know it does actually boot, then you can troubleshoot why it’s taking so long.
Duncan
interesting. Thanks for giving solution for new issue.