My Oracle Support Banner

TUX6.4 - CR013237 Bad syntax in ubb can cause processes to hang CPU (Doc ID 764979.1)

Last updated on SEPTEMBER 06, 2022

Applies to:

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



Bad syntax in ubb can cause processes to hang CPU

Routines that parse the UBB assume that user input is syntactically correct.  Consequently, in some cases, a user's
typo can result in server processes going into infinite loops.  Although there are no core dumps or error messages of
any kind to indicate a syntax error, the CPU use climbs and it can hang the system.    Tracking the source of this
kind of problem  to a typo in the UBB file is extremely arduous work.  Given that the UBB is generated by people and
subject to human error,  either the UBB input should be thoroughly checked  by software for syntax errors before being
parsed for values or the routines that parse the UBB must be made more robust so that they will catch the errors and
report them.    This problem should be addressed for the entire UBB file, not just the CLOPT -p options of the SERVER
section as indicated in the specifics below.

A customer had the following syntax for a server in the server section of their ubb: 
  CLOPT="-p 1,300:4:120 -A" 
- the colon after 4 causes the setsvropts()  routine in the tmrunsvr.c file to go into an infinite loop trying to
parse this string.   


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.