This article only applies to the Classic JOC interface
The information provided on this page only applies to the Classic JOC user interface, which is entering retirement:
FEATURE AVAILABILITY ENDING WITH RELEASE 1.11
The JOC Cockpit user interface replaces JOC:
FEATURE AVAILABILITY STARTING FROM RELEASE 1.11
See the JOC Cockpit article as a starting point for information about the JOC Cockpit.Why is there a delay before the log file shows in the GUI?
Question:
If I click on the menu button and select show log ...sometimes the JOC interface comes up totally blank (almost as if there is no log). After a while the log finally appears on the screen. Can you point out why there might be a delay?
Answer:
Check if the number of process classes in your scheduler.xml is sufficient(defaults to 10), e.g.
<process_classes>
<process_class max_processes="20"/>
<process_class name="many_processes" max_processes="30"/>
...
</process_classes>
A set of standard processes runs in the default process class (the one without the attribute name=). The handling of TCP requests (which is what you cause by using the built-in web interface) occupies one of these processes. What could have happened is that some more processes (=jobs) were running in the default process class and the web interface had to wait for a process to be freed.