HP-UX Workload Manager Toolkits A.01.06 Release Notes for HP-UX 11.0, HP-UX 11i V1.0 and HP-UX 11i V2.0

HP-UX WLM Toolkits (WLMTK) Release Notes
Known problems and workarounds
Chapter 1 11
ODBTK: Debug clean_exit code is not useful
Issue
If wlmoradc detects a command-line error and debugging is enabled, the
code reported by clean_exit may not be useful. For example:
Mar 26 22:57:16 mytestmachine WLMTK: wlmoradc[p8686] INFO starting
wlmoradc
Mar 26 22:57:16 mytestmachine WLMTK: wlmoradc[p8686] ERROR bad oracle home
passed to -h or --home argument
Mar 26 22:57:16 mytestmachine WLMTK: wlmoradc[p8686] INFO ending wlmoradc
Mar 26 22:57:16 mytestmachine WLMTK: wlmoradc[p8686] DEBUG clean_exit
with exit value:Not a typewriter
Workaround
If the ERROR message and the DEBUG message disagree, ignore the
DEBUG message.
ApacheTK: Elapsed time reported may not be for a successful page fetch
Issue If you use the ApacheTK tool time_url_fetch with a URL that Apache
cannot serve (such as http://mytestmachine/misspelllllled_url.htm) the ab
tool and time_url_fetch report the elapsed time for Apache to serve up a
“Not found” msg. Neither tool considers this an error, although an individual
trying to access this URL might.
Workaround Always check your target URL by hand with your browser, the ab tool,
and/or the time_url_fetch tool to ensure you are really getting a page
fetch.