Log processing of orbeon form


Sometimes, when we visit the demo page of orbeon form, such as URL:http://localhost:8080/orbeon/…

Log processing of orbeon form

An error message is encountered:

Log processing of orbeon form

403 error:

Log processing of orbeon form

Log file location:
Log processing of orbeon form


When you receive unexpected behavior, such as an error message from form builder or when running a form, you can usually find more information about the cause of the error in the orbeon forms log file (commonly known as orbeon. Log). To check this log:
Find your orbeon Log location. Out of the box, it’s written in/ logs/orbeon. Log, relative to the current directory when you started the servlet container or application server. For example, if you start Tomcat from the bin directory, the log files will be located in Tomcat’s log directory. If you can’t find orbeon Log, or if you want to create it elsewhere, edit WEB-INF / resources / config / log4j. In orbeon forms XML, find the singlefileappender, and then in \ < param name = “file” value = “.. / logs / orbeon. Log” / \ >/ logs/orbeon. Log is replaced by the orbeon. Log you want to store Log location. Use an absolute path, such as / opt / Tomcat / logs / orbeon Log is usually a good idea.

Some log fragment analysis:

2021-12-18 10:18:12,169 INFO ProcessorService – Context listener – Context initialized.
2021-12-18 10:18:12,192 INFO form-runner-auth – initializing
2021-12-18 10:18:12,196 INFO form-runner-auth – configuring: FilterSettings(None)
2021-12-18 10:18:12,200 INFO limiter – initializing

This context listener is java at first sight.

The contextlistener class is the default context listener class that instantiates the ApplicationContext object. On the web Register this class in the JSP / java servlet. XML to call it when the JSP / java servlet application starts.

2021-12-18 10:18:19,491 INFO ProcessorService – Servlet initialized.

Servlets are small Java programs that run in a web server. Servlets receive and respond to requests from web clients, usually through HTTP (Hypertext Transfer Protocol). The servlet handles any call from the client to the service method.

2021-12-18 10:18:19,532 INFO lifecycle – event: {“request”: “1”, “source”: “limiter”, “message”: “start: chain”, “path”: “/fr/orbeon/controls/new”, “method”: “GET”, “wait”: “0”}

This indicates that the client initiated a get request to open the new data form.

2021-12-18 10:18:19,572 INFO ProcessorService – Session listener – Session created.

When the session object changes, httpsessionevent is notified. The listener interface corresponding to this event is HttpSessionListener. We can perform some operations in this event, such as counting the total number and current login users, and maintaining the log of user details such as login time and logout time.

2021-12-18 10:18:19,625 INFO lifecycle – event: {“request”: “1”, “session”: “FF9852F8D7883C80F1F8D8ADA1231ADC”, “source”: “service”, “message”: “start: handle”}

Generate the first session and end with ADC.

2021-12-18 10:18:19,625 INFO ProcessorService – /fr/orbeon/controls/new – Received request
2021-12-18 10:18:21,810 INFO lifecycle – event: {“request”: “2”, “session”: “FF9852F8D7883C80F1F8D8ADA1231ADC”, “source”: “service”, “message”: “start: handle”, “path”: “/fr/service/persistence/crud/orbeon/controls/form/form.xhtml”, “method”: “GET”}

Read the form under orbeon / controls / form XHTML file.

More Jerry’s original articles are: “Wang Zixi”:
Log processing of orbeon form