Forms Servlet Logging Explained [ID 219471.1] | |
|
|
|
|
PURPOSE
-------
To explain the Forms Servlet logging and trace options
SCOPE & APPLICATION
-------------------
To give an overview of the servlet logging features available with the forms
services which provide the following:
* A record of all Forms sessions, including session start and end times,
and the user's IP address and host name (session-level logging).
* Monitoring of Oracle9i Forms-related network traffic and performance
(session-performance and request-performance-level logging).
* Information for debugging site configuration problems (debug-level logging).
This article is specific to:
Oracle 9iAS Rel 2 Forms Services (Forms 9i (9.0.2))
Oracle 9iDS Rel 2 (Forms 9i (9.0.2))
Oracle Application Server 10g (9.0.4) Forms Services (Forms 10g (9.0.4))
Oracle Developer Suite 10g (9.0.4) (Forms 10g (9.0.4))
Oracle Forms 10.1.2.0.2
Target Audience: Support Engineers, Consultants, Developers, System
Administrators
Forms Servlet Logging
=====================
You can cause the Listener Servlet to write log messages to the servlet log
file by appending one of the following strings to the serverURL client
parameter:
/session
/sessionperf
/perf
/debug
You can either do this in the URL used to start the Forms application, or in the
formsweb.cfg file. For example, to get a performance trace you might start the
Forms application using a URL like the following:
http://yourserver/forms90/f90servlet?serverURL=/forms90/l90servlet/perf
or
http://yourserver/forms/frmservlet?serverURL=/forms/lservlet/perf
To turn on session level logging for all users you might change the serverURL
entry in the default section of the formsweb.cfg file to the following:
serverURL=/forms90/l90servlet/session
or
serverURL=/forms/lservlet/session
You can also append "/debug" to the URL used to invoke the Forms Servlet.
The Forms Servlet will then output debug messages to the log file.
So to get full diagnostics you could start the application by going to a URL
like the following:
http://yourserver/forms90/f90servlet/debug?serverURL=/forms90/l90servlet/debug
or
http://yourserver/forms/frmservlet/debug?serverURL=/forms/lservlet/debug
.
Location and Name of log files
==============================
Oracle 9iAS Rel 2 (9.0.2) / Oracle Application Server 10g (9.0.4)
[ORACLE_HOME]/j2ee/OC4J_BI_Forms/application-deployments/forms90app/
OC4J_BI_Forms_default_island_[no]/application.log
Oracle 9iDS Rel 2 (9.0.2)
[ORACLE_HOME]/j2ee/iDS/application-deployments/forms90app/application.log
Oracle Developer Suite 10g (9.0.4) or 10.1.2.0.2
[ORACLE_HOME]/j2ee/DevSuite/application-deployments/forms/application.log
The log levels and example output for each String appended to serverURL
=======================================================================
1. (none)
No log messages are produced. However, during Forms Servlet initialisation,
a message is written to the log file stating the name and path of the
configuration file being used, for example:
FormsServlet init():
configFileName: d:\orant9i/forms90/server/formsweb.cfg
testMode:
false
2. /session
Log messages are written whenever a Forms session starts or ends. These give
the host name and IP address of the client (the machine on which the user's
web browser is running), the runtime process id and a unique internal session
id number.
example:
Session start messages (example):
Forms session <10> started for test-pc.mycompany.com ( 138.56.98.72 )
Forms session <10> runtime process id = 373
Session end message (example):
Forms session <10> ended
3. /sessionperf
Performance summary statistics are included with the session end message,
for example:
Forms session <3> started for test-pc.mycompany.com ( 138.56.98.72 )
Forms session <3> runtime process id = 460
Forms session <3> ended
Total duration of network exchanges: 1.041
Total number of network exchanges: 2 (1 "long" ones over 1.000 sec)
Average time for one network exchange (excluding long ones): 0.030
Total bytes: sent 1,110, received 316
4. /perf
A performance message is written for every request from the client:
for example:
Forms session <3> started for test-pc.mycompany.com ( 138.56.98.72 )
Forms session <3> runtime process id = 460
Forms session <3>: request processed in 1.011 sec. Received 8 bytes,returned 8
bytes.
Forms session <3>: request processed in 0.030 sec. Received 308 bytes, returned
1,102 bytes.
Forms session <3> ended
Total duration of network exchanges: 1.041
Total number of network exchanges: 2 (1 "long" ones over 1.000 sec)
Average time for one network exchange (excluding long ones): 0.030
Total bytes: sent 1,110, received 316
5. /debug
Full debug messages. Copious debug messages are written in addition to the
messages mentioned above. This is very verbose and is intended mainly for
debugging and support purposes. For information regards how to interpret the
debug output, reference:
Note:271095.1 How to Interpret Forms Listener Servlet Debug / Log
Information?
Here is an example run by going to a URL like
http://test-machine:8888/forms90/f90servlet/debug&config=ienative&serverURL
=/forms90/l90servlet/debug):
=============== FormsServlet ===============
GET request received, cmd=debug,
qstring=config=ienative&serverURL=/forms90/l90servlet/debug
No current servlet session
File baseie.htm not found, looking in d:\orant9i/forms90/server
The SSO_USERID is: null
=============== FormsServlet ===============
GET request received, cmd=startsession, qstring=config=ienative&serverURL=
/forms90/l90servlet/debug&ifcmd=startsession
No current servlet session
New servlet session started
SSO_USERID in startSession: null
SSO_AuthType in startSession: null
User DN: null
Subscriber DN: null
EM mode in the config file: 0
File default.env not found, looking in d:\orant9i/forms90/server
envFile = d:\orant9i\forms90\server\default.env
serverURL: /forms90/l90servlet/debug
rewrittenURL: /forms90/l90servlet/debug;jsessionid=27f6412da05c
426ab47db4ae77636113
=============== ListenerServlet ===============
GET request received, cmd=getinfo,
qstring=ifcmd=getinfo&ifhost=test-pc.mycompany.com&ifip=130.35.96.71
Existing servlet session, id = 27f6412da05c426ab47db4ae77636113, not from cookie
Creating new Runtime Process using default executable
Starting Forms Server in EM mode
startProcess: executing ifweb90 server webfile=HTTP-0,0,1
Getting stdin, stdout and stderr of child process
Writing working directory to stdin: d:\orant9i\forms90
New server process created
Forms session <4> started for test-pc.mycompany.com ( 138.56.98.72 )
***********************************************
Got POST request, length = 8
HTTP request headers:
ACCEPT-LANGUAGE: en
PRAGMA: 1
CONTENT-TYPE: application/x-www-form-urlencoded
ACCEPT: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
USER-AGENT: Mozilla/4.0 (compatible; MSIE 5.0; Win32)
HOST:test-machine:8888
CONTENT-LENGTH: 8
CONNECTION: Keep-Alive
Existing servlet session, id = 27f6412da05c426ab47db4ae77636113, not from cookie
Forms session <4> runtime process id = 474
Port number is 2791
RunformProcess.connect(): connected after 1 attempts
Connected to ifweb process at port 2791
Forms session <4>: request processed in 1.032 sec. Received 8 bytes,
returned 8 bytes.
***********************************************
Niciun comentariu:
Trimiteți un comentariu