RHN Taskomatic is throwing the error "JVM exited unexpectedly"

Solution Unverified - Updated -

Issue

  • RHN Taskomatic is dying throwing the error below:
INFO   | jvm 1    | 2014/05/15 00:07:42 | 2014-05-15 00:07:42,008 [DefaultQuartzScheduler_Worker-3] 
INFO  com.redhat.rhn.taskomatic.task.CompareConfigFilesTask -   saving comparison for 1000018708
INFO   | jvm 1    | 2014/05/15 00:07:45 | 2014-05-15 00:07:45,314 [DefaultQuartzScheduler_Worker-3] 
INFO  com.redhat.rhn.taskomatic.task.CompareConfigFilesTask -   saving comparison for 1000018709
INFO   | jvm 1    | 2014/05/15 00:07:48 | 2014-05-15 00:07:48,293 [DefaultQuartzScheduler_Worker-3] 
INFO  com.redhat.rhn.taskomatic.task.CompareConfigFilesTask -   saving comparison for 1000018711
INFO   | jvm 1    | 2014/05/15 00:07:51 | 2014-05-15 00:07:51,373 [DefaultQuartzScheduler_Worker-3] 
INFO  com.redhat.rhn.taskomatic.task.CompareConfigFilesTask -   saving comparison for 1000018751
INFO   | jvm 1    | 2014/05/15 00:07:54 | 2014-05-15 00:07:54,480 [DefaultQuartzScheduler_Worker-3] 
INFO  com.redhat.rhn.taskomatic.task.CompareConfigFilesTask -   saving comparison for 1000018740
INFO   | jvm 1    | 2014/05/15 00:07:57 | 2014-05-15 00:07:57,618 [DefaultQuartzScheduler_Worker-3] 
INFO  com.redhat.rhn.taskomatic.task.CompareConfigFilesTask -   saving comparison for 1000018735
INFO   | jvm 1    | 2014/05/15 00:08:00 | 2014-05-15 00:08:00,809 [DefaultQuartzScheduler_Worker-3] 
INFO  com.redhat.rhn.taskomatic.task.CompareConfigFilesTask -   saving comparison for 1000018771
INFO   | jvm 1    | 2014/05/15 00:08:03 | 2014-05-15 00:08:03,871 [DefaultQuartzScheduler_Worker-3] 
INFO  com.redhat.rhn.taskomatic.task.CompareConfigFilesTask -   saving comparison for 1000018779
INFO   | jvm 1    | 2014/05/15 00:08:07 | 2014-05-15 00:08:07,384 [DefaultQuartzScheduler_Worker-3] 
INFO  com.redhat.rhn.taskomatic.task.CompareConfigFilesTask -   saving comparison for 1000018742
INFO   | jvm 1    | 2014/05/15 00:08:10 | 2014-05-15 00:08:10,571 [DefaultQuartzScheduler_Worker-3] 
INFO  com.redhat.rhn.taskomatic.task.CompareConfigFilesTask -   saving comparison for 1000018738
ERROR  | wrapper  | 2014/05/15 00:10:04 | JVM exited unexpectedly.
STATUS | wrapper  | 2014/05/15 00:10:05 | JVM exited in response to signal SIGKILL (9).
STATUS | wrapper  | 2014/05/15 00:10:09 | Launching a JVM...
ERROR  | wrapper  | 2014/05/15 00:10:38 | Startup failed: Timed out waiting for a signal from the JV
M.
ADVICE | wrapper  | 2014/05/15 00:10:38 | 
ADVICE | wrapper  | 2014/05/15 00:10:38 | ----------------------------------------------------------
--------------
ADVICE | wrapper  | 2014/05/15 00:10:38 | Advice:
ADVICE | wrapper  | 2014/05/15 00:10:38 | The Wrapper consists of a native component as well as a se
t of classes
ADVICE | wrapper  | 2014/05/15 00:10:38 | which run within the JVM that it launches.  The Java compo
nent of the
ADVICE | wrapper  | 2014/05/15 00:10:38 | Wrapper must be initialized promptly after the JVM is launched or the
ADVICE | wrapper  | 2014/05/15 00:10:38 | Wrapper will timeout, as just happened.  Most likely the main class
ADVICE | wrapper  | 2014/05/15 00:10:38 | specified in the Wrapper configuration file is not correctly initializing
ADVICE | wrapper  | 2014/05/15 00:10:38 | the Wrapper classes:
ADVICE | wrapper  | 2014/05/15 00:10:38 |     com.redhat.rhn.taskomatic.core.TaskomaticDaemon
ADVICE | wrapper  | 2014/05/15 00:10:38 | While it is possible to do so manually, the Wrapper ships with helper
ADVICE | wrapper  | 2014/05/15 00:10:38 | classes to make this initialization processes automatic.
ADVICE | wrapper  | 2014/05/15 00:10:38 | Please review the integration section of the Wrapper's documentation
ADVICE | wrapper  | 2014/05/15 00:10:38 | for the various methods which can be employed to launch an application
ADVICE | wrapper  | 2014/05/15 00:10:38 | within the Wrapper:
ADVICE | wrapper  | 2014/05/15 00:10:38 |     http://wrapper.tanukisoftware.org/doc/english/integrate.html
ADVICE | wrapper  | 2014/05/15 00:10:38 | ------------------------------------------------------------------------
ADVICE | wrapper  | 2014/05/15 00:10:38 | 
ERROR  | wrapper  | 2014/05/15 00:10:38 | JVM did not exit on request, terminated
STATUS | wrapper  | 2014/05/15 00:10:39 | JVM exited in response to signal SIGKILL (9).
ERROR  | wrapper  | 2014/05/15 00:10:39 | Unable to start a JVM
STATUS | wrapper  | 2014/05/15 00:10:40 | <-- Wrapper Stopped
STATUS | wrapper  | 2014/05/15 08:17:18 | --> Wrapper Started as Daemon

Environment

  • Red Hat Network Satellite 5.4.1
  • Red Hat Network Satellite 5.5
  • Red Hat Satellite 5.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content