Some Wake on LAN settings and debug messages in loader-messages.log

  • 7010199
  • 22-Feb-2012
  • 25-Sep-2013


Novell ZENworks 11 Configuration Management Support Pack 1 - ZCM 11 SP1
Novell ZENworks 11 Configuration Management Support Pack 2 - ZCM 11 SP2


What does it mean to see this in loader-messages.log?
[WakeOnLANHandler : Will not process wol queue item 1877660 with taks id of wol-1435467201 immediately because the maximum concurrent job count has been reached.] [] [] [] []


This line does not indicate an error.  Later the log will show that the job is completed:
[WakeOnLANHandler : Restarting the processing of wol- 1435467201 .] [] [] [] []
[DEBUG] [1/30/12 8:01:52 AM] [] [WakeOnLanHandler : FileData: <ns1:WOLData xmlns=" " xmlns:ns1=""><Targets><Target><GUID>8c02297b73774896304e448dddd142c7</GUID><Type>Device</Type><AgentPort>0</AgentPort></Target><Target>
<DeviceRefresh>true</DeviceRefresh></ns1:WOLData>] [] [] [] []
[DEBUG] [1/30/12 8:01:52 AM] [] [WakeOnLANHandler : Marking job as done for task 'wol-1435467201'. Completed = true] [] [] [] []

Additional Information

Primary servers restrict WOL task concurrent threads to 10 in order to prevent overloading the primary with WOL tasks.  The server keeps track of the jobs ( /var/opt/novell/zenworks/discovery/woltasks ) so that delayed jobs will be reprocessed when the prior jobs complete.
If the primary server is not explicitly selected in the WOL task, the server to handle the job will be selected based on that on the same segment as the device, or randomly selected.  There is no load balance logic used to assign the WOL tasks to any particular primary unless specifically selected by the Administrator in the WOL task.
By Default, ZCM will process WOL jobs 10 devices at a time.  To increase overall performance speed, Administrators can configure the this value in  wakeOnLanHandler.xml
by setting:
By default the value is set to 10 which should can be set to a  reasonable number, depending on the system configuration.
For example in an environment with large numbers of devices to be woken up, try giving a value of 20 ~ 50.   64 bit machines may be able to go higher.  See also x64 RAM settings in Best Practice guide: 
This thread count is unrelated to and does not impact Tomcat threads.
NOTE:  Do not change the value of MaxWOLRunningThreads, because this will take the threads from Tomcat threads.  This would cause the primary Tomcat to run out of threads and will lead to slow performance issues.

For more information about Wake on LAN in general see