Tracing and Diagnostics
The following sections are included:
Forms Trace
Forms Trace allows you to record information about a precisely defined part of forms functionality or a class of user actions. This is accomplished by defining events for which you want to collect trace information.
For example, you can record information about trigger execution, mouse-clicks, or both. From the Enterprise Manager Fusion Middleware Control, you can use trace output to diagnose performance and other problems with Oracle Forms applications.
Forms Trace replaces the functionality that was provided with Forms Runtime Diagnostics (FRD) and Performance Event Collection Services (PECS), which were available in earlier releases of Oracle Forms. Forms Trace allows you to trace the execution path through a form, for example, the steps the user took while using the form.
Difference between Tracing and Debugging
You use Forms debugging to find out what happens when a user presses a button. Debugging allows a remote developer to connect to an existing Forms user session and to trace the user actions as the application runs or to debug on a local machine. Forms Trace provides information about the timing of specific events. Oracle Support uses tracing to isolate and analyze issues. For example, you use Forms trace to find out which query takes the longest time to execute, or which trigger causes performance issues with Oracle Forms.
Enable and Configure Forms Trace
An event is something that happens inside a Forms application as a direct or indirect result of a user action. An event set specifies a group of events that you can trace simply by specifying the event set name rather than each event number individually when you start the trace.
An example is when a user presses a button that executes a query. Use the Trace Configuration selection in the Forms menu of Fusion Middleware Control page to define the events that you want to trace. This page manages all changes in the ftrace.cfg
file for you.
Note the following items when working with Forms Trace:
-
If you first switch off trace, and then switch it on again with new settings, then trace is enabled with the new trace group.
-
Backup the
ftrace.cfg
anddefault.env
files before editing them with Fusion Middleware Control. -
As with most Web applications, it is easy to lose unsaved changes by switching pages. Be sure to save any changes you make through Fusion Middleware Control to Forms configuration, trace, or environment files before proceeding to other pages.
The length of time it takes for changes to be saved is affected by the number of lines you have changed. For example, an additional fifty lines of comments will take longer to save than just deleting a single entry.
For a list of events and their corresponding event numbers, see List of Traceable Events.
Configuring Forms Trace
To access the Trace Configuration page:
-
Start Fusion Middleware Control.
-
From the Fusion Middleware Control main page, click the Oracle Forms Services instance link that you want to configure.
-
From the Forms menu list, select Trace Configuration. The Trace Configuration page is displayed.
To create a new trace group:
-
From the Fusion Middleware Control main page, click the link to the Oracle Forms Services instance that you want to configure.
-
From the Forms menu list, select Trace Configuration.
The Trace Configuration page is displayed.
-
Click Add.
The Add dialog is displayed.
-
Enter the information for the new trace group:
Name: Enter a name for the trace group.
Value: See Table -36 for the values of traceable events.
Comment : Enter a comment.
-
The trace group name must not contain spaces. For example, a_b_c is an acceptable trace group name.
-
There must be a comma between each event number you specify in the Value. For example, 65,66,96,194 is an acceptable value.
-
You can use a range of numbers. For example, 32-46 is an acceptable range.
-
-
Click Add.
The new trace group is added.
-
Click Apply to save the changes, or Revert to discard them.
To delete a trace group:
-
In the Trace Configuration page, select the group you want to delete.
-
Click Delete.
The trace group is deleted and the Trace Configuration page reappears.
-
Click Apply to save the changes, or Revert to discard them.
To edit an existing trace group:
- In the Trace Configuration page, select the group you want to edit.
- Enter the value and description for the trace group.
- Click Apply to save the changes, or Revert to discard them.
Specify URL Parameter Options
The following command line parameters are used to configure Forms Trace:
Record = Tracegroup = Log = <filename>
The following table describes the parameter values:
Table -35 Forms Trace Command Line Parameters
Parameter | Values | Description |
---|---|---|
|
forms |
Enables Forms Trace. |
|
Name, event number, or event range |
Indicates which events should be recorded and logged.
Tracegroup=<keyword>, where <keyword> is specified in ftrace.cfg (for example, Tracegroup=MyEvents). This lets you log the events in the named set MyEvents.
|
Starting and Stopping Forms Trace
You start a trace by specifying trace entries in the URL or from Fusion Middleware Control. Entries should include the grouping of events to collect and the trace file name. Trace collection starts when the form executes.
The following are sample URLs to start a trace:
http://example.com/forms/frmservlet?form=cxl&record=forms&tracegroup=0-199 http://example.com/forms/frmservlet?form=cxl&record=forms&tracegroup=mysql
To start tracing a session from Fusion Middleware Control:
-
From the Forms menu, select User Sessions.
The User Sessions page appears.
-
Select the row containing the Forms user session for which you want to enable tracing.
-
Click Enable Tracing.
The Enable Tracing dialog appears.
-
From the Select Trace Group list, select an available trace group and click OK.
The Enable Tracing dialog is dismissed and tracing is now enabled for the selected Forms user session.
To stop tracing a session from Fusion Middleware Control:
-
From the Forms menu, select User Sessions.
The User Sessions page appears.
-
Select the row containing the Forms user session for which you want to disable tracing.
-
Click Disable Tracing.
The Disable Tracing dialog is displayed.
-
Click OK.
The Disable Tracing dialog is dismissed and tracing is now stopped for the selected Forms user session.
To switch between trace groups for a session:
Viewing Forms Trace Output
Only administrators or a user belonging to administrators' group can view trace log files. Once the user has logged in, he or she does not have to log in again in the same browser session to view trace log files for different sessions.
Trace data is stored in a binary file with a *.trc
extension. The default location of the trace log is $ORACLE_INSTANCE/FormsComponent/forms/trace/forms_pid.trc
where pid is the process ID of the user session. If you are not using Enterprise Manager Fusion Middleware Control, you need to use the Translate utility, as described in Running the Translate Utility.
To view trace data:
- From the Forms menu in Fusion Middleware Control, select the User Sessions menu item.
- Select a User Session row and click Trace Log to see the contents of the trace log.
- Log in to view the trace file.
Running the Translate Utility
The Translate utility converts trace data to XML, HTML, or text formats. You need to specify an additional parameter "OutputClass" which has three legal values: "WriteOutTEXT", "WriteOutXML" and "WriteOutHTML". If you do not specify the outputclass
, the output file is in text format. These values are case-sensitive.
Note:
To use the Translate Utility:
-
Set the PATH variable to include the path to the directory containing the Java executable.
-
Set the CLASSPATH variable to include the path to frmxlate.jar.
To convert trace data to Text format:
-
At the command line, enter:
java oracle.forms.diagnostics.Xlate datafile=a.trc outputfile=myfile.txt outputclass=WriteOutTEXT
This creates a file called myfile.txt in text format.
To convert trace data to HTML format:
-
At the command line, enter:
java oracle.forms.diagnostics.Xlate datafile=a.trc outputfile=myfile.html outputclass=WriteOutHTML
This creates a file called myfile.html in HTML format.
To convert trace data to XML format:
-
To create
myfile.xml
, at the command line, enter:java oracle.forms.diagnostics.Xlate datafile=a.trc outputfile=myfile.xml outputclass=WriteOutXML
This creates a file called myfile.xml in XML format.
List of Traceable Events
The table provided in this section, lists the events that can be defined for tracing. In future releases of Forms, more events may be added to this list.
Event types are as follows:
-
Point event: An event that happens in Oracle Forms as the result of a user action or internal signal for which there is no discernible duration, for example, displaying an error message on the status line. Each instance of this event type creates one entry in the log file.
-
Duration event: An event with a start and end, for example, a trigger. Each instance of this event type creates a pair of entries in the log file (a start and end event).
-
Built-in event: An event associated with a built-in. Each instance of this event type provides a greater quantity of information about the event (for example, argument values).
Table -36 List of Traceable Events
Event Number | Definition | Type |
---|---|---|
0 |
Abnormal Error |
point |
1 |
Error during open form |
point |
2 |
Forms Died Error |
point |
3 |
Error messages on the status bar |
point |
4-31 |
Reserved for future use |
NA |
32 |
Startup |
point |
33 |
Menu |
point |
34 |
Key |
point |
35 |
Click |
point |
36 |
Double-click |
point |
37 |
Value |
point |
38 |
Scroll |
point |
39 |
LOV Selection |
point |
40 |
not used |
not used |
41 |
Window Close |
point |
42 |
Window Activate |
point |
43 |
Window Deactivate |
point |
44 |
Window Resize |
point |
45 |
Tab Page |
point |
46 |
Timer |
point |
47 |
DB Event |
point |
48 |
Reserved for future use |
NA |
49-63 |
Reserved for future use |
NA |
64 |
Form (Start & End) |
duration |
65 |
Program Unit (Start & End) |
duration |
66 |
Trigger (Start & End) |
duration |
67 |
LOV (Start & End) |
duration |
68 |
Opening a Editor |
point |
69 |
Canvas |
point |
70 |
Alert |
duration |
71 |
GetFile |
point |
72-95 |
Reserved for future use |
NA |
96 |
Builtin (Start & End) |
builtin |
97 |
User Exit (Start & End) |
duration |
98 |
SQL (Start & End) |
duration |
99 |
MenuCreate (Start & End) |
duration |
100 |
DB PU (Start & End) |
duration |
101 |
Execute Query |
duration |
102-127 |
Reserved for future use |
NA |
128 |
Client Connect |
point |
129 |
Client Handshake |
point |
130 |
Heartbeat |
point |
131 |
HTTP Reconnect |
point |
132 |
Socket (Start & End) |
duration |
133 |
HTTP (Start & End) |
duration |
134 |
SSL (Start & End) |
duration |
135 |
DB Processing (Start & End) |
duration |
136 |
DB Logon (Start & End) |
duration |
137 |
DB Logoff (Start & End) |
duration |
138-159 |
Reserved for future use |
NA |
160-168 |
Reserved for internal use |
NA |
169-191 |
Reserved for future use |
NA |
192* |
Environment Dump |
N/A |
193* |
State Delta |
N/A |
194* |
Builtin Arguments |
N/A |
195* |
UserExit Arguments |
N/A |
196* |
Program Unit Arguments |
N/A |
256 and higher |
User defined |
NA |
1024 and higher |
Reserved for internal use |
NA |
Note:
These event numbers do not have aTYPE
because they are not really events, but rather details for events. For example, the State Delta is something you can choose to see - it is triggered by a real action or event.
List of Event Details
The following tables list event details that can be defined for tracing.
Remember:
Event names are case sensitive.
Table -37 User Action Event Details
Action | Details | Number |
---|---|---|
Menu Selection |
Menu Name, Selection |
33 |
Key |
Key Pressed, Form, Block, Item |
34 |
Click |
Mouse/Key, Form, Block, Item |
35 |
DoubleClick |
Form, Block, Item |
36 |
Value |
Form, Block, Item |
37 |
Scroll |
Form, Up, Down, Page, Row |
38 |
LOV Selection |
LOV Name, Selection Item |
39 |
Alert |
AlertName, Selection |
40 |
Tab |
Form |
45 |
DB Event |
Queue Name |
47 |
Window Activate, Deactivate,Close, Resize |
WindowName, FormName, Size |
41,42,43,44 |
Table -38 Forms Services Event Details
Event Name | Details | Number |
---|---|---|
Form |
Form ID, Name, Path, Attached Libraries, Attached Menus |
64 |
Program Unit |
Program Unit Name, FormID |
65 |
Trigger |
TriggerName, FormName, BlockName, ItemName, FormID |
66 |
LOV |
LOV name, FormId |
67 |
Editor |
FormId, Editor Name |
68 |
Canvas |
FormId, Canvas Name |
69 |
Table -39 Detailed Events
Event Name | Details | Number |
---|---|---|
Builtin |
BuiltinName, FormId |
96 |
User Exit |
UserExitName, FormId |
97 |
MenuCreate |
MenuName, FormID |
99 |
PLSQL |
PLSQLSTmt, FormID |
100 |
ExecQuery |
Block Name |
101 |
Table -40 Three-Tier Event Details
Event Name | Details | Number |
---|---|---|
Client Connect |
Timestamp |
128 |
Client Handshake |
Timestamp |
129 |
Heartbeat |
Timestamp |
130 |
HTTP Reconnect |
NA |
131 |
Socket |
FormId, Packets, Bytes |
132 |
HTTP |
FormId, Packets, Bytes |
133 |
HTTPS |
FormId, Packets, Bytes |
134 |
DB Processing |
FormId, Statement |
135 |
DB Logon |
FormId |
136 |
DB Logoff |
FormId |
137 |
Table -41 Miscellaneous Event Details
Event Name | Details | Number |
---|---|---|
Environment Dump |
Selected environment information |
192 |
State Delta |
Changes to internal state caused by last action/event |
193 |
Builtin Args |
Argument values to a builtin |
194 |
Userexit args |
Arguments passed to a userexit |
195 |
Procedure Args |
Arguments (in|out) passed to a procedure. |
196 |
Taking Advantage of Oracle Diagnostics and Logging Tools
Oracle Diagnostics and Logging (ODL) is a feature of Oracle Fusion Middleware that enables administrators to keep a record of all Oracle Forms sessions, monitor Oracle Forms-related network traffic, and debug site configuration problems.
Some features of Oracle Diagnostics and Logging available to Forms Services include:
-
Recording of all Oracle Forms sessions, including session start and end times, and the user's IP address and host name (session-level logging)
-
Monitoring of Oracle Forms-related network traffic and performance (session-performance and request-performance-level logging)
-
Generating debugging information for site configuration issues (debug-level logging)
-
Logging handled through Fusion Middleware Control
-
Correlating events in these log files with events in the database
-
Automatic handling of log file rotation.
-
Handling of log size restriction by the mechanism rather than by OS level scripts as was done previously
The following sections are included:
Enabling Oracle Diagnostics and Logging
When you turn on logging, the Listener Servlet writes log messages to the servlet log file.
To view examples of output for the various levels of logging, see Example Output for Each Level of Servlet Logging.
The following table describes the supported logging capabilities. If no string is appended to serverURL, then default logging is supported. To start other loggers, they must be specified in serverURL as described in the next section.
Table -42 Supported logging capabilities
String appended to serverURL client parameter | Description of logging |
---|---|
(none) |
During Forms servlet initialization, a message is written to the log file stating the name and path of the configuration file being used. Messages of levels higher and equal to the log level set for the default logger in logging.xml are logged. Default Value is set to NOTIFICATION:1 and levels NOTIFICATION:1, WARNING:1, ERROR:1 and INTERNAL_ERROR are logged. |
/session |
Log messages are written whenever a Forms session starts or ends. These give the host name and IP address of the client (the computer on which the user's Web browser is running), the runtime process id, and a unique internal session id number. |
/sessionperf |
Performance summary statistics are included with the session end message. |
/perf |
A performance message is written for every request from the client. |
/debug |
Full debug messages. Other debug messages are written in addition to the messages mentioned above. This logging level is verbose and is intended mainly for debugging and support purposes. |
Specifying Logging
To specify logging for all users, change the serverURL entry, in the Web Configuration page default section, to the following entry:
serverURL=/forms/lservlet/<string>
The <string>, the above entry, specifies the logging capability, as described in Table -42. If no string is provided, the default logging, for example, if you want to start session-level logging, modify the serverURL as follows:
serverURL=/forms/lservlet/session
Specifying Logging Levels Using Fusion Middleware Control
To set the log levels for Forms servlet logging using Fusion Middleware Control, perform the following:
Viewing Diagnostics Logs
You view the contents of diagnostics logs from Fusion Middleware Control.
To view the contents of diagnostics logs:
Using the Servlet Page
From the Forms menu, select Monitoring and then Servlet Logs. Use this page to search, sort, view, download, and export collected server diagnostics logs.
For information on managing and viewing the log files, see Managing Log Files and Diagnostic Data in Administering Oracle Fusion Middleware.
Location of Log Files
The default servlet log file is named formsapp-diagnostic.log
. It is written to the WLS_FORMS/logs
directory of the Oracle WebLogic Managed Server to which Forms is deployed.
In Oracle Forms Services, the full path is:
$DOMAIN_HOME/servers/WLS_FORMS/logs/<application name>-diagnostic.log
The trace logs are stored in files named forms_pid.trc
by default, where pid
is the process ID of the user session. The default location of the trace log is:
$DOMAIN_HOME/system_components/FORMS/forms1/trace/forms_pid.trc
Use the Translate Utility, as described in Running the Translate Utility to view them.
Example Output for Each Level of Servlet Logging
The following are examples of the type of output you get when you use the following levels of logging.
(none)
[2008-09-10T06:58:47.106-07:00] [WLS_FORMS] [NOTIFICATION] [FRM-93100]
[oracle.forms.servlet] [tid: 11] [ecid: 0000HlCYKnmD4i8nvgy0V118lx4u000000,0]
[APP: formsapp] [arg:
configFileName: <configfilename>
testMode: false] Initializing the Forms Servlet. Initialization
parameters are:[[
configFileName: <configfilename>
testMode:
false
]]
[2008-09-10T06:58:53.517-07:00] [WLS_FORMS] [NOTIFICATION] [FRM-93180]
[oracle.forms.servlet] [tid: 11] [ecid: 0000HlCZfTDD4i8nvgy0V118lx4u000003,0]
[APP: formsapp] [arg:
envFile: null
executable: null
WaitTime: 500
MaxBlockTime: 1000]
Initializing ListenerServlet. Initialization parameters
are:[[
envFile: null
executable: null
WaitTime: 500
MaxBlockTime: 1000
]]
/session
[2008-09-11T07:35:01.507-07:00] [WLS_FORMS] [NOTIFICATION:16] [FRM-93251]
[oracle.forms.servlet.session] [tid: 14] [ecid:
0000HlHpYGDD4i8nvgy0V118mFuv00000V,0] [SRC_CLASS:
oracle.forms.servlet.RunformSession] [APP: formsapp] [SRC_METHOD: <init>] [FORMS
SESSION_ID: ..8] [arg: sup-pc1] [arg: xxx.xxx.xxx.xxx] Runtime session started
for client <pc1> (IP address <ip address>).
2008-09-11T07:35:01.798-07:00] [WLS_FORMS] [NOTIFICATION:16] [FRM-93548]
[oracle.forms.servlet.session] [tid: 14] [ecid:
0000HlHpYGDD4i8nvgy0V118mFuv00000V,0] [SRC_CLASS:
oracle.forms.servlet.RunformProcess] [APP: formsapp] [SRC_METHOD: connect] [FORMS
SESSION_ID: ..8] [arg: 7765] Runtime process ID is 7765.
2008-09-11T07:38:11.372-07:00] [WLS_FORMS] [NOTIFICATION:16] [FRM-93252]
[oracle.forms.servlet.session] [tid: 14] [ecid:
0000HlHpYGDD4i8nvgy0V118mFuv00000V,0] [SRC_CLASS:
oracle.forms.servlet.RunformSession] [APP: formsapp] [SRC_METHOD: stop] [FORMS
SESSION_ID: ..8] Forms session ended.
/sessionperf
[2008-09-11T07:40:25.923-07:00] [WLS_FORMS] [NOTIFICATION:16] [FRM-93251]
[oracle.forms.servlet.sessionperf] [tid: 17] [ecid:
0000HlHqlS9D4i8nvgy0V118mFuv00000Y,0] [SRC_CLASS:
oracle.forms.servlet.RunformSession] [APP: formsapp] [SRC_METHOD: <init>] [FORMS
SESSION_ID: ..9] [arg: <pc1>] [arg: xxx.xxx.xxx.xxx] Runtime session started
for client <pc1> (IP address xxx.xxx.xxx.xxx).
2008-09-11T07:40:26.223-07:00] [WLS_FORMS] [NOTIFICATION:16] [FRM-93548]
[oracle.forms.servlet.sessionperf] [tid: 17] [ecid:
0000HlHqlS9D4i8nvgy0V118mFuv00000Y,0] [SRC_CLASS:
oracle.forms.servlet.RunformProcess] [APP: formsapp] [SRC_METHOD: connect] [FORMS
SESSION_ID: ..9] [arg: 8023] Runtime process ID is 8023.
2008-09-11T07:40:43.593-07:00] [WLS_FORMS] [NOTIFICATION:16] [FRM-93252]
[oracle.forms.servlet.sessionperf] [tid: 17] [ecid:
0000HlHqlS9D4i8nvgy0V118mFuv00000Y,0] [SRC_CLASS:
oracle.forms.servlet.RunformSession] [APP: formsapp] [SRC_METHOD: stop] [FORMS
SESSION_ID: ..9] Forms session ended.
[2008-09-11T07:40:43.594-07:00] [WLS_FORMS] [TRACE] [FRM-93710]
[oracle.forms.servlet.sessionperf] [tid: 17] [ecid:
0000HlHqlS9D4i8nvgy0V118mFuv00000Y,0] [SRC_CLASS:
oracle.forms.servlet.RunformSession] [APP: formsapp] [SRC_METHOD: stop] [FORMS
SESSION_ID: ..9] [arg: 1.557] [arg: 6] [arg: 0] [arg: 1.000] [arg: 0.259] [arg:
5106] [arg: 352] Total duration of network exchanges is 1.557.[[
Total number of network exchanges is 6 (0 long ones over 1.000 sec).
Average time for one network exchange (excluding long ones) is 0.259.
Total number of bytes sent is 5106.
Total number of bytes received is 352.
]]
/perf
[2008-09-11T07:42:46.560-07:00] [WLS_FORMS] [NOTIFICATION:16] [FRM-93251]
[oracle.forms.servlet.perf] [tid: 14] [ecid: 0000HlHrJmWD4i8nvgy0V118mFuv00000^,0]
[SRC_CLASS: oracle.forms.servlet.RunformSession] [APP: formsapp] [SRC_METHOD:
<init>] [FORMS_SESSION_ID: ..10] [arg: <pc1>] [arg: xxx.xxx.xxx.xxx] Runtime
session started for client <pc1> (IP address <ip address>).
[2008-09-11T07:42:46.854-07:00] [WLS_FORMS] [NOTIFICATION:16] [FRM-93548]
[oracle.forms.servlet.perf] [tid: 17] [ecid: 0000HlHqlS9D4i8nvgy0V118mFuv00000Y,0]
[SRC_CLASS: oracle.forms.servlet.RunformProcess] [APP: formsapp] [SRC_METHOD:
connect] [FORMS_SESSION_ID: ..10] [arg: 8149] Runtime process ID is 8149.
[2008-09-11T07:42:46.865-07:00] [WLS_FORMS] [TRACE:16] [FRM-93700]
[oracle.forms.servlet.perf] [tid: 17] [ecid: 0000HlHqlS9D4i8nvgy0V118mFuv00000Y,0]
[SRC_CLASS: oracle.forms.servlet.ListenerServlet] [APP: formsapp] [SRC_METHOD:
doPost] [FORMS_SESSION_ID: ..10] [arg: 0.011] [arg: 8] [arg: 8] [arg: null]
Request duration is 0.011 seconds. Request size is 8 bytes; response size is 8
bytes.
[2008-09-11T07:42:47.921-07:00] [WLS_FORMS] [TRACE:16] [FRM-93700]
[oracle.forms.servlet.perf] [tid: 17] [ecid: 0000HlHqlS9D4i8nvgy0V118mFuv00000Y,0]
[SRC_CLASS: oracle.forms.servlet.ListenerServlet] [APP: formsapp] [SRC_METHOD:
doPost] [FORMS_SESSION_ID: ..10] [arg: 0.438] [arg: 272] [arg: 5022] [arg: null]
Request duration is 0.438 seconds. Request size is 272 bytes; response size is
5022 bytes.
/debug
[2009-02-11T14:39:03.016+00:00] [WLS_FORMS] [NOTIFICATION:16] [FRM-93250]
[oracle.forms.servlet] [tid: [ACTIVE].ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Hx
_lhDcD4i8nvgy0V119Xz350000HZ,0] [APP: formsapp#12.2.1] Forms session started.
[2009-02-11T14:39:03.017+00:00] [WLS_FORMS] [TRACE:32] [FRM-94200]
[oracle.forms.servlet] [tid: [ACTIVE].ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Hx
_lhDcD4i8nvgy0V119Xz350000HZ,0] [SRC_CLASS: oracle.forms.servlet.FormsServlet]
[APP: formsapp#12.2.1] [SRC_METHOD: doRequest] [FORMS_SESSION_ID: ..43] [arg:
GET] [arg:
cmd: frmservlet
config: null
requestCharset: null
QueryString: null
Content-Type: null
Accept-Charset: null
responseCharset: null] FormsServlet receiving GET request. Details:[[
cmd: frmservlet
config: null
requestCharset: null
QueryString: null
Content-Type: null
Accept-Charset: null
responseCharset: null
]]
[2009-02-11T14:39:03.017+00:00] [WLS_FORMS] [TRACE:32] [FRM-94281]
[oracle.forms.servlet] [tid: [ACTIVE].ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Hx
_lhDcD4i8nvgy0V119Xz350000HZ,0] [SRC_CLASS: oracle.forms.servlet.ListenerServlet]
[APP: formsapp#12.2.1] [SRC_METHOD: printSessionDetails] [FORMS_SESSION_ID: ..43]
No current servlet session ID.
[2009-02-11T14:39:03.017+00:00] [WLS_FORMS] [TRACE:32] [FRM-94170]
[oracle.forms.servlet] [tid: [ACTIVE].ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Hx
_lhDcD4i8nvgy0V119Xz350000HZ,0] [SRC_CLASS: oracle.forms.servlet.FormsServlet]
[APP: formsapp#12.2.1] [SRC_METHOD: findFile] [FORMS_SESSION_ID: ..43] [arg:
basejpi.htm] [arg: <config folder>] File basejpi.htm is missing from the
current directory, looking in <config folder>
[2009-02-11T14:39:21.460+00:00] [WLS_FORMS] [TRACE:32] [FRM-94200]
[oracle.forms.servlet] [tid: [ACTIVE].ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Hx
_llhoD4i8nvgy0V119Xz350000Hd,0] [SRC_CLASS: oracle.forms.servlet.FormsServlet]
[APP: formsapp#12.2.1] [SRC_METHOD: doRequest] [FORMS_SESSION_ID: ..43] [arg:
GET] [arg:
cmd: startsession
config: null
requestCharset: null
QueryString: ifsessid=..43&acceptLanguage=en-us&ifcmd=startsession&iflocale=en-US
Content-Type: null
Accept-Charset: null
responseCharset: null]
FormsServlet receiving GET request. Details:[[
cmd: startsession
config: null
requestCharset: null
QueryString: ifsessid=..43&acceptLanguage=en-us&ifcmd=startsession&iflocale=en-US
Content-Type: null
Accept-Charset: null
responseCharset: null
]]
.
.
.
.
[2009-02-11T14:39:21.716+00:00] [WLS_FORMS] [TRACE:32] [FRM-94201]
[oracle.forms.servlet] [tid: [ACTIVE].ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Hx
_llloD4i8nvgy0V119Xz350000Hf,0] [SRC_CLASS: oracle.forms.servlet.ListenerServlet]
[APP: formsapp#12.2.1] [SRC_METHOD: doGet] [FORMS_SESSION_ID: ..43] [arg: GET]
[arg:
cmd: getinfo
QueryString: ifcmd=getinfo&ifhost=sup-pc1&ifip=xxx.xxx.xxx.xxx]
ListenerServlet receiving GET request. Details:[[
cmd: getinfo
QueryString: ifcmd=getinfo&ifhost=sup-pc1&ifip=xxx.xxx.xxx.xxx
]]
[2009-02-11T14:39:21.717+00:00] [WLS_FORMS] [TRACE:32] [FRM-94282]
[oracle.forms.servlet] [tid: [ACTIVE].ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Hx
_llloD4i8nvgy0V119Xz350000Hf,0] [SRC_CLASS: oracle.forms.servlet.ListenerServlet]
[APP: formsapp#12.2.1] [SRC_METHOD: printSessionDetails] [FORMS_SESSION_ID: ..43]
[arg:
HyLhJSjZ85F5GWbZLDgwp1MY02FK5tC6yVDP1LylbCvgmv9y3CfK!126690176!1234363161461]
Existing servlet session, ID =
HyLhJSjZ85F5GWbZLDgwp1MY02FK5tC6yVDP1LylbCvgmv9y3CfK!126690176!1234363161461
[2009-02-11T14:39:21.717+00:00] [WLS_FORMS] [TRACE:32] [FRM-94286]
[oracle.forms.servlet] [tid: [ACTIVE].ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Hx
_llloD4i8nvgy0V119Xz350000Hf,0] [SRC_CLASS: oracle.forms.servlet.ListenerServlet]
[APP: formsapp#12.2.1] [SRC_METHOD: printSessionDetails] [FORMS_SESSION_ID: ..43]
Session ID is not from cookie.
[2009-02-11T14:39:21.717+00:00] [WLS_FORMS] [TRACE:32] [FRM-94430]
[oracle.forms.servlet] [tid: [ACTIVE].ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Hx
_llloD4i8nvgy0V119Xz350000Hf,0] [SRC_CLASS: oracle.forms.servlet.RunformSession]
[APP: formsapp#12.2.1] [SRC_METHOD: <init>] [FORMS_SESSION_ID: ..43] Trying to
get a prestarted process.
[2009-02-11T14:39:21.717+00:00] [WLS_FORMS] [TRACE:32] [FRM-94432]
[oracle.forms.servlet] [tid: [ACTIVE].ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Hx
_llloD4i8nvgy0V119Xz350000Hf,0] [SRC_CLASS: oracle.forms.servlet.RunformSession]
[APP: formsapp#12.2.1] [SRC_METHOD: <init>] [FORMS_SESSION_ID: ..43] Prestarted
process is not available.
[2009-02-11T14:39:21.718+00:00] [WLS_FORMS] [TRACE:32] [FRM-94522]
[oracle.forms.servlet] [tid: [ACTIVE].ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Hx
_llloD4i8nvgy0V119Xz350000Hf,0] [SRC_CLASS: oracle.forms.servlet.RunformSession]
[APP: formsapp#12.2.1] [SRC_METHOD: <init>] [FORMS_SESSION_ID: ..43] [arg: null]
Creating new runtime process using default executable.
[2009-02-11T14:39:21.718+00:00] [WLS_FORMS] [TRACE:32] [FRM-94532]
[oracle.forms.servlet] [tid: [ACTIVE].ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Hx
_llloD4i8nvgy0V119Xz350000Hf,0] [SRC_CLASS: oracle.forms.servlet.RunformProcess]
[APP: formsapp#12.2.1] [SRC_METHOD: startProcess] [FORMS_SESSION_ID: ..43] [arg:
frmweb webfile=HTTP-0,default] RunformProcess.startProcess(): executing frmweb
webfile=HTTP-0,default
.
.
.
.