Next to adjusting the log level (see chapter 5.2) in the JobRouter web application, it is possible to receive certain detailed information by activating the debug mode that can help troubleshooting.
The following additional information will be generated if the debug mode is activated:
•In forms of user steps, the time (in seconds) needed server-side to generate the entire form will be written into a hidden element with the ID "renderingTime". This information can be helpful to determine the fraction of the total form load time that is caused by the processing time of the web browser of the user (Data transfer from server to client, rendering the form, executing the onLoad scripts).
•All database queries are written additionally in the log file dbqueries_YYMMDD.log in the log directory of the JobRouter web application.
•During the internal parallel processing of steps by JobFlowExecute and JobFlowSend under use of cURL, additional detailed information are written into the log file curl_n_m_YYMMDD.log (n = processing pool, m = number of the parallel cURL request) in the log directory of the JobRouter web application. This additional information can be useful to locate the cause of steps that should automatically be processed not being processed over a long period of time. This can be detected if the number of steps to be processed in the respective processing pools is not going down although no new steps arriving in this processing pool while the JobServer service is started. Information on the number of steps waiting to be processed in a processing pool can be found in the table JRJOBFLOWSTATS.
•When calling REST resources, additional detailed information is written in a log file restclient_debug_YYMMDD.log in the log directory of the JobRouter web application.
•When using specific JobRouter add-on modules, additional detailed information will be written in respective log files in the log directory of the JobRouter web application.
•The messages in the log files will be expanded by additional information (maximum memory usage, request files, backtrace, unique ID (UID)).
•When saving the configuration of a system activity, it will additionally be written in an xmltransfer.xml file in the output directory of the JobRouter web application.
Configuration
The debug mode can be activated by defining the constant CONST_DEBUG with the value 1 in the config.php file.
If the debug mode is activated, users with configuration rights will see a respective message after logging in.
Attention: Please note, activating the debug mode can lead to a significant amount of data (under circumstances multiple hundreds of MB per hour) written into the log files over a short amount of time. Please ensure that enough free storage space is available for the output directory and after logging all necessary additional information, remove the constant CONST_DEBUG.
