Structure of the WebOffice Log File
WebOffice writes its messages to the file WebOffice.log. By default it is located at:
<WebOffice application>\WEB-INF\work\WebOffice.log
When the file reaches 10 MB, it is saved as WebOffice.log.1 and a new WebOffice.log is started. Up to nine backups are kept (WebOffice.log.1 is the most recent, WebOffice.log.9 the oldest). The file is UTF-8 encoded.
Structure of an entry
Each entry starts with a header line beginning with # and the time stamp. The following lines up to the next header line are the actual message, e.g. a stack trace.
#2026-09-30 10:12:22,431 GS ERROR [http-nio-8443-exec-3 ] Leitungskataster 11C7E6DB5FA0FF76D9C54C567191A0B6 5408760 E334507610T34707
request to https://gis.example.com/arcgis/rest/services/Leitungen/MapServer/export failed: Read timed out (30000 ms)
java.net.SocketTimeoutException: Read timed out
Field |
Example |
Meaning |
|---|---|---|
Time stamp |
2026-09-30 10:12:22,431 |
Date and time with milliseconds (time zone of the server) |
Logging category |
GS |
2-letter code of the logging category, see the table below. Missing in the previous log format. |
Log level |
ERROR |
FATAL, ERROR, WARN, INFO, DEBUG or TRACE |
Thread |
http-nio-8443-exec-3 |
Name of the thread that wrote the message (user requests, background threads, initialization) |
Project |
Leitungskataster |
WebOffice project, if the message belongs to a project |
Session |
11C7E6DB… |
Session ID of the user session, if any |
Elapsed |
5408760 |
Milliseconds since the application was started |
Error ID |
E334507610T34707 |
The error ID that is also shown to the user in the client's error message. It identifies a reported error in the log unambiguously. |
Previous log format
Older log files do not contain a category code yet; the header line continues with the log level right after the time stamp. The Log Explorer reads both formats, also mixed in one file (e.g. if the log file was written across an update). Entries without category are listed as none in the category filter.
Logging categories and their codes
The code corresponds to the logging category the message was written with. Most categories can be set to DEBUG in SynAdmin on the Logging tab; the categories are described in the chapter Troubleshooting and problem solution.
Code |
Logging category |
Adjustable on the Logging tab |
|---|---|---|
AU |
AUTHORIZATION |
yes |
BR |
BRIDGE |
yes |
CL |
CLIENT |
yes |
CF |
CONFIG |
yes |
CO |
CONTROLLER |
yes |
CU |
CUSTOM |
yes |
FI |
FULLTEXTSEARCH.INDICES |
yes |
FQ |
FULLTEXTSEARCH.SEARCH |
yes |
ED |
FUNCTIONS.EDITING |
yes |
NT |
FUNCTIONS.NETTRACE |
yes |
GS |
GEOSERVER |
yes |
DB |
JDBC |
yes |
LD |
LDAP |
yes |
ME |
MEMORY |
yes |
NE |
NET |
yes |
RE |
REST |
yes |
TH |
THREAD |
yes |
TA |
THREAD.ACTIVITY |
yes |
US |
USER |
yes |
UM |
USERMANAGEMENT |
yes |
UT |
UTIL |
yes |
SE |
SELECTION |
no |
GU |
GUI |
no |
GE |
GUI_EVENT |
no |
XM |
XML |
no |
EN |
ENCODING |
no |
WO |
(other WebOffice messages) |
no |
?? |
(unknown) |
no |