Taskomatic reports out of JAVA heap space

This document (7012598) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 1.7
SUSE Manager 2.1
SUSE Manager 3
SUSE Manager 3.1
SUSE Manager 3.2
SUSE Manager 4.0

Situation

When syncing channel data using mgr-ncc-sync or mgr-ncc-sync -r the following error may be observed in /var/log/rhn/rhn_taskomatic_daemon.log:

INFO   | jvm 1    | 2013/06/13 11:36:55 | Exception in thread "DefaultQuartzScheduler_QuartzSchedulerThread" java.lang.OutOfMemoryError: Java heap space
INFO   | jvm 1    | 2013/06/13 11:36:55 |       at java.lang.Object.clone(Native Method)
INFO   | jvm 1    | 2013/06/13 11:36:55 |       at java.lang.Class.getConstructor(Class.java:377)
INFO   | jvm 1    | 2013/06/13 11:36:55 |       at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:697)
INFO   | jvm 1    | 2013/06/13 11:36:55 |       at org.quartz.impl.jdbcjobstore.JobStoreSupport.getAttributeRestoringConnection(JobStoreSupport.java:678)
INFO   | jvm 1    | 2013/06/13 11:36:55 |       at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:707)
INFO   | jvm 1    | 2013/06/13 11:36:55 |       at org.quartz.impl.jdbcjobstore.JobStoreTX.getNonManagedTXConnection(JobStoreTX.java:69)
INFO   | jvm 1    | 2013/06/13 11:36:55 |       at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3760)
INFO   | jvm 1    | 2013/06/13 11:36:55 |       at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2728)
INFO   | jvm 1    | 2013/06/13 11:36:55 |       at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:264)


Resolution

Please edit /etc/rhn/rhn.conf and add the option
taskomatic.java.maxmemory = <value>
manually to the end of the file. The value has to be entered in megabytes. An example could be:
taskomatic.java.maxmemory = 4096
When done, restart taskomatic using
rctaskomatic restart
to have it pick up the new XmX value. Since the last releases, the default value was set to 4096, so this change should not be needed any more in new releases. Higher values should not be required either, as recommended in the past (not even when using Expanded Support channels). The general RAM requirements still apply (32 GB for a production system).

Additional Information

NOTE: As of SUSE Manager 3, the option is no longer called taskomatic.maxmemory but taskomatic.java.maxmemory.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7012598
  • Creation Date: 13-Jun-2013
  • Modified Date:03-Mar-2020
    • SUSE Manager

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center