Web Troubleshooting - Enable HTTP Server Instance tracing
| Date: | 12 September 2002 |
|---|---|
| Product/Release: | LANSA for the Web |
| Abstract: | Web HTTP Server Instance Log Tracing |
| Submitted By: | LANSA Technical Support |
| Last Review: | November 2010 |
To further help with troubleshooting LANSA for the Web applications, you can start the HTTP Server Instance with tracing.
Add the parameter '-vv' as an instance startup value:
STRTCPSVR SERVER(*HTTP) HTTPSVR(MYINST '-vv')
Extract from HTTP server (HTTPSVR) - Help:
-vv [verbose level service trace] Turn on verbose level service tracing.
Note: the letter 'v' must be in lowercase
When the instance starts, there will be Instance logs under the user profile of QTMHHTTP. ie:
QPZHBTRC QTMHHTTP QPRINT MYINST RDY 11 1
QPZHBTRC QTMHHTTP QPRINT MYINST RDY 0 1
QPZHBTRC QTMHHTTP QPRINT MYINST RDY 0 1
QPZHBTRC QTMHHTTP QPRINT MYINST RDY 0 1
QPZHBTRC QTMHHTTP QPRINT MYINST RDY 0 1
The first log on the list contains the logging information.
Note: The user profile that will start the Server Instance with logging must have *IOSYSCFG authority.
An example of the log:
HTTP SERVER SERVICE TRACE OUTPUT
TIMESTAMP THREAD MODULE MESSAGE
-------------- --------- ---------- -------------------------------------------------
1031731836 0000066A HTDaemon MAIN Job = MYINST QTMHHTTP 222279; Thread =
............................ [11/Sep/2002:18:10:36 +0000, 1031731836] 00000001
1031731836 0000066A HTDaemon ............ This is IBM HTTP Server 1.0
1031731836 0000066A HTDaemon ............ Built on Dec 18 2001 at 13:11:19.
1031731836 0000066A HTDaemon ............ Started at Wed Sep 11 18:10:36 2002
1031731836 0000066A HTDaemon ............ Running as "QTMHHTTP", UID:-196583,
1031731836 0000066A HTDaemon Initial messages will be retrieved from the "/MRI
1031731836 0000066A HTNLS.c Successfully opened message catalog "/QIBM/ProdDa
1031731836 0000066A HTHash.c HTHASH.c: HashAdd table=80000000 key=0 value=edc5
1031731836 0000066A HTDaemon Starting.. httpd
1031731836 0000066A HTWorkT. Added....... thread-init functions for module "HT
1031731836 0000066A HTWorkT. ............ 0
1031731836 0000066A HTWorkT. ............ 0
&
1031731836 0000066A HTConfig DNS-lookup.. Off
1031731836 0000066A HTConfig Enabled..... method GET
1031731836 0000066A HTConfig Enabled..... method POST
1031731836 0000066A HTConfig Disabled.... method HEAD
1031731836 0000066A HTRuleDB Map......... "/CGI-BIN/LANSAWEB*" --> "/QSYS.LIB/
1031731836 0000066A HTRuleDB Map......... "/cgi-bin/lansaweb*" --> "/QSYS.LIB/
1031731836 0000066A HTRuleDB Map......... "/CGI-BIN/LANSAXML*" --> "/QSYS.LIB/
1031731836 0000066A HTRuleDB Map......... "/cgi-bin/lansaxml*" --> "/QSYS.LIB/
1031731836 0000066A HTRuleDB Map......... "/CGI-BIN/WML/LANSAXML*" --> "/QSYS.
1031731836 0000066A HTRuleDB Map......... "/cgi-bin/wml/lansaxml*" --> "/QSYS.
1031731836 0000066A HTRuleDB Map......... "/authlib/LANSAWEB*" --> "/QSYS.LIB/
1031731836 0000066A HTRuleDB Map......... "/AUTHLIB/LANSAWEB*" --> "/QSYS.LIB/
1031731836 0000066A HTRuleDB Map......... "/authlib/LANSAXML*" --> "/QSYS.LIB/
1031731836 0000066A HTRuleDB Map......... "/AUTHLIB/LANSAXML*" --> "/QSYS.LIB/
1031731836 0000066A HTRuleDB Service..... "/QSYS.LIB/SUPQGPL01.LIB/*"
1031731836 0000066A HTRuleDB Service..... "/cgi-bin/jsmdirect" --> "/QSYS.LIB/