Uncaught exception in service Dictionary Consumer Service for OES linux Support Pack 2

  • 3048914
  • 12-Dec-2007
  • 30-Apr-2012


Novell ZENworks 7 Desktop Management Support Pack 1 - ZDM7 SP1 Inventory
Novell ZENworks 7 Desktop Management on Linux Support Pack 1 - ZDML7 SP1 Inventory


Dictionary consumer service generates unhandled memory exception and inventory services are unloaded.
[7/10/07 22:19:50.528] Service Manager: Uncaught exception in thread
Thread[Dictionary Consumer::UpdateScheduler::Schedule Refresh Thread,9,Dictionary Consumer Service13]com.novell.utility.servicemanager.LoaderThreadGroup[name=Dictionary Consumer Service13,maxpri=9]

[7/10/07 22:19:50.529] Service Manager: Uncaught exception in service Dictionary Consumer Service

[7/10/07 22:19:50.529] Service Manager: Service manager name to stop is ZENWorksInvService
[7/10/07 22:19:50.529] Service Manager Thread Watcher: ERROR: An internal error has occured.
If the error occurs when you manually stop the Inventory services, ignore it.
All inventory services are stopped at this point, and must be restarted with:
/etc/init.d/novell-zfd-inv start


To obtain access to a hot patch with the fix for this problem, follow the instructions in TID 3484245"Updates to Novell ZENworks 7 Desktop Management" which can be found athttps://www.novell.com/support
Workaround: The"/etc/init.d/novell-zdm-inv" script checks whether the inventory service is running and starts it only if it is not running. Set a cron job that runs the command"/etc/init.d/novell-zdm-inv start" once every few weeks (or whatever is the frequency with which the inventory service stops working) to automatically restart the service when it has gone down.

Additional Information

The frequency of the problem seems to correlate with the SchedulePollInterval setting in dictconsumer.properties. This is described as follows:
# The time interval, in minutes, between two polls for a change for the dictionary update schedule. The default is
# 1 day (1440 minutes)
In typical usage, the dictionary update schedule shouldn't change frequently, so this setting might be extended.