XForms logging

Search…
XForms logging
Enabling XForms logging
Sometimes, an error message or stack trace in the Orbeon Forms log file provides enough information to a developer to figure out what went wrong, but not always. In such cases, you can turn to the XForms engine logging facility. To enable it, make sure you uncomment the following logging <Logger> (Log4j 2.x) or <Category> (Log4j 1.x):
Log4j 2.x (WEB-INF/resources/config/log4j2.xml):
1
<Logger name="org.orbeon.oxf.xforms.processor.XFormsServer" level="debug"/>
Copied!
Log4j 1.x (WEB-INF/resources/config/log4j.xml):
1
<category name="org.orbeon.oxf.xforms.processor.XFormsServer">
2
    <priority value="debug"/>
3
</category>
Copied!
Note: You must restart your Servlet container for those changes to be taken into account.
Fine-grained configuration
Two properties in WEB-INF/resources/config/properties-local.xml control exactly what is logged by the XForms engine:
1
    <property as="xs:NMTOKENS" name="oxf.xforms.logging.debug">
2
        document
3
        model
4
        submission
5
        control
6
        event
7
        action
8
        analysis
9
        server
10
        html
11
        process
12
    </property>
13
​
14
    <property as="xs:NMTOKENS" name="oxf.xforms.logging.error">
15
        submission-error-body
16
    </property>
Copied!
oxf.xforms.logging.debug controls what is logged at debug level:
Related to a particular XForms document:
model
activity related to xf:model, including instance loads, validation, and binds
submission
timing activity related to xf:submission
submission-details
detail activity related to xf:submission
requires submission to be present as well
control
activity related to controls
event
activity related to events dispatching and propagation
action
activity related to XForms actions
document
other activity related to an XForms document
this includes the output of the <xf:message> action with level xxf:log-debug
process
activity related to processes​
Not related to a particular XForms document:
analysis
activity related to the static analysis of an XForms document
server
activity related to handling Ajax requests
html
activity related to converting XForms to HTML
resources
activity related to handling XForms CSS and JavaScript resources
state
activity related to state handling
resolver
activity related to the URI resolver
utils
miscellaneous activity
cache
[SINCE Orbeon Forms 4.6]
activity of the static state cache during XForms initialization
Data:
html-static-state
requires html
outputs the static state input
analysis-xbl-tree
requires analysis
outputs the detail of the XBL shadow trees computed
submission-body
requires submission AND submission-details
outputs the detail of submission request/response bodies
model-serialized-instance
requires model
outputs the full instances serialized into the dynamic state after an Ajax request completes
server-body
requires server
outputs the full Ajax request and response bodies
oxf.xforms.logging.error controls what is logged at error level:
submission-error-body
Whether to attempt to output a submission response body when a submission error occurs
This is enabled by default, but you can turn it off, e.g. for data sensitivity reasons
Binary bodies are not logged, but the logger mentions that the type is a binary type
When the response body is NOT logged and is used for replace="instance|all", streaming is taking place. However when the response body IS logged, streaming does not take place:
The body is read in memory
The body is logged
Then the rest of the submission proceeds
server-body
output the Ajax request in case of error occurring while processing the request
Development configuration
During XForms development, you might want to enable a more aggressive debug configuration.
1.Change your Log4j2 or Log4j configuration. In your WEB-INF/resources/config, check if you have a file named log4j2.xml or log4j.xml:
If you have a file named log4j2.xml (with 2 in the file name), inside the element <Loggers>, add:
1
<Logger name="org.orbeon.oxf.xforms.processor.XFormsServer" level="debug"/>
2
<Logger name="org.orbeon.oxf.processor.DebugProcessor"      level="debug"/>
3
<Logger name="org.orbeon.relational"                        level="debug"/>
4
<Logger name="org.orbeon.auth"                              level="debug"/>
5
<Logger name="org.orbeon.lifecycle"                         level="debug"/>
Copied!
If you have a file named log4j.xml (without 2 in the file name), uncomment the following:
1
<category name="org.orbeon.oxf.xforms.processor.XFormsServer">
2
    <priority value="debug"/>
3
</category>
Copied!
2.Configure the oxf.xforms.logging.debug property in your config/properties-local.xml. You can choose precisely what the XForms engine logs. The following is the most comprehensive configuration. It will log almost everything. In most cases, this is a good configuration during development, and while troubleshooting issues in staging:
1
<property as="xs:NMTOKENS" name="oxf.xforms.logging.debug">
2
    document
3
    model
4
    submission
5
    control
6
    event
7
    action
8
    analysis
9
    server
10
    server-body
11
    html
12
    process
13
    submission-details
14
    submission-body
15
</property>
Copied!
Production configuration
No debug output
In production, you probably don't want any debug information coming out to your logs. So set this in log4j.xml:
1
<category name="org.orbeon.oxf.xforms.processor.XFormsServer">
2
    <priority value="info"/>
3
</category>
Copied!
Alternatively, remove or comment-out the lines above. When this is done, the oxf.xforms.logging.debug property is no longer used, so it does not matter what it contains. However, the oxf.xforms.logging.error is still relevant. Configure it appropriately, depending on whether you want to see submission responses bodies logged or not.
Just submission timings
If you only want to see submission timings, in your log4j.xml use:
1
<category name="org.orbeon.oxf.xforms.processor.XFormsServer">
2
    <priority value="debug"/>
3
</category>
Copied!
And in your properties-local.xml:
1
<property as="xs:NMTOKENS" name="oxf.xforms.logging.debug">
2
    submission
3
</property>
Copied!
Example output
The following shows a sample XForms logging session:
1
XForms server - start handling external events
2
  XForms server - start handling external event {target id: "age-input-control", event name: "xxforms-value-change-with-focus-change"}
3
    setvalue - setting instance value {value: "36", changed: "true", instance: "instance"}
4
    event - start dispatching {name: "xxforms-value-changed", id: "instance"}
5
    event - end dispatching {time (ms): "0"}
6
    event - start dispatching {name: "xforms-recalculate", id: "main-model"}
7
        model - start performing recalculate {model id: "main-model"}
8
          setvalue - setting instance value {value: "A", changed: "false", instance: "instance"}
9
          setvalue - setting instance value {value: "A", changed: "false", instance: "countries-instance"}
10
          setvalue - setting instance value {value: "", changed: "false", instance: "country-details-instance"}
11
        model - end performing recalculate {time (ms): "9"}
12
    event - end dispatching {time (ms): "9"}
13
    event - start dispatching {name: "xforms-revalidate", id: "main-model"}
14
        model - start performing revalidate {model id: "main-model"}
15
          event - start dispatching {name: "xxforms-invalid", id: "instance"}
16
          event - end dispatching {time (ms): "0"}
17
          event - start dispatching {name: "xxforms-valid", id: "resources-instance"}
18
          event - end dispatching {time (ms): "0"}
19
          event - start dispatching {name: "xxforms-valid", id: "flavors-instance"}
20
          event - end dispatching {time (ms): "0"}
21
          event - start dispatching {name: "xxforms-valid", id: "carriers-instance"}
22
          event - end dispatching {time (ms): "0"}
23
          event - start dispatching {name: "xxforms-valid", id: "countries-names-instance"}
24
          event - end dispatching {time (ms): "0"}
25
          event - start dispatching {name: "xxforms-valid", id: "countries-instance"}
26
          event - end dispatching {time (ms): "0"}
27
          event - start dispatching {name: "xxforms-valid", id: "country-details-instance"}
28
          event - end dispatching {time (ms): "0"}
29
        model - end performing revalidate {time (ms): "4"}
30
    event - end dispatching {time (ms): "4"}
31
    event - start dispatching {name: "xforms-refresh", id: "main-model"}
32
        model - start performing refresh {model id: "main-model"}
33
          controls - start cloning
34
          controls - end cloning {time (ms): "0"}
35
          controls - start updating bindings
36
          controls - end updating bindings {time (ms): "11", controls updated: "91", repeat iterations: "0"}
37
          event - start dispatching {name: "xforms-value-changed", id: "age-input-control"}
38
          event - end dispatching {time (ms): "0"}
39
          event - start dispatching {name: "xforms-enabled", id: "age-input-control"}
40
          event - end dispatching {time (ms): "0"}
41
        model - end performing refresh {time (ms): "17"}
42
    event - end dispatching {time (ms): "17"}
43
  XForms server - end handling external event {time (ms): "33"}
44
XForms server - end handling external events {time (ms): "33"}
Copied!
See also
​Logging​
​Relational database logging​
SAP Hybris Module
Troubleshooting
Last modified 2mo ago
Copy link
Contents
Enabling XForms logging
Fine-grained configuration
Development configuration
Production configuration
No debug output
Just submission timings
Example output