Search: log

…MariaDB (SPE 3.46+) or MySQL (up to SPE 3.45), the built-in SQLite is not supported for logging. server.logging.file # Path to file where log is stored server.logging.file = ${application.dir}log/phxspe.log Path and filename to write the log to, if the server.logging.destination setting contains file value. Default value is ${application.dir}log/phxspe.log, i.e. a phxspe.log file in a log subdirectory of the SPE application…

…server.port = 8600 # Server logging # Level (trace, debug, information, warning, error, fatal) server.logging.level = information # Destination (console, file, database) # Logging to database is supported only for MySQL server.logging.destination = file # Path to file where log is stored server.logging.file = ${application.dir}log/phxspe.log Did you notice the server.logging.file directive? They present the first example of using variables in…

…which created the log record Thread identifier of thread which created the log record ThreadId numeric ID of thread which created the log record Priority priority of the operation which created the log record Text raw log text as it would be written into log file or console DateTime log record creation timestamp Example of SPE log in MySQL database…

…may cause the initialization to actually take longer than if only single thread would be used. The downside of multi-threaded initialization is somehow messy log file ;-), since the messages are written to the log as they come, making the eventual troubleshooting more difficult (nevertheless, each such message is marked by corresponding thread number). Therefore this configuration is more suitable…