Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 > Administering > Jobs > Monitoring job results

Monitoring job results

Viewing job results in the Cloud Cruiser Portal

To review the results of a job, navigate to Data > Processing > Monitoring.

You can click a row in the table to view the status of that job step in detail:

Detailed status of a job step

You can select and copy the text in the details table so you can quickly paste it into messaging and email tools without having to search through the log files.

Viewing job results in log files

You can open a job's log file by selecting an entry and clicking Show Log File at the top of the page. These files are stored in the cc-working\logs\<workbook> directory. 

Troubleshooting specific warnings and errors

This section suggests causes and resolutions for common warnings and errors when running batch jobs.

A job instance already exists

Message: job terminated in error: org.springframework.batch.core.repository.JobInstanceAlreadyCompleteException: A job instance already exists and is complete for parameters

Cause: An instance of the same job is still running. The Cloud Cruiser application server can only run one instance of a job at a time.

Resolution: Restart the Cloud Cruiser application server to terminate the running job. Check the log for that job run to determine why it hung.

Out of memory when running the Excel collector

A job that runs the Microsoft Excel collector can throw

Message: 0000005e  java.lang.OutOfMemoryError: GC overhead limit exceeded

Cause: The Excel file from which you're collecting is larger than the Cloud Cruiser application server can handle with current settings.


  1. Adjust garbage collection for your Java virtual machine (VM).
    1. Open the file <install_dir>\bin\ccservice.bat in a text editor.
      If you are not running Cloud Cruiser as a service, edit ccserver.bat instead.
    2. Find the line containing the string --JvmOptions.
      This is followed by a set of options for your Java VM, enclosed in double quotes (") and delimited by semicolons (;).
    3. Add the option -XX:+UseConcMarkSweepGC.
      For example, this portion of the line might be:

      --JvmOptions "-XX:MaxPermSize=%serverMaxPermGenMB%m;-Dcatalina.base=%CATALINA_HOME%;-Dcatalina.home=%CATALINA_HOME%;-Djava.endorsed.dirs=%CATALINA_HOME%\endorsed;-XX:+UseConcMarkSweepGC"​
    4. Save the file, then reinstall the Cloud Cruiser application server.
  2. Run your job again. If you receive a new out of memory error message, increase the heap size for the Cloud Cruiser application server.
    1. Open the file <install_dir>/conf/ in a text editor.
    2. Increase the value for the serverMaxHeapMB setting by 1024 (one gigabyte), then save the file.
    3. Reinstall the Cloud Cruiser application server.
  3. Run your job again. If you still receive the out of memory error message, repeat step 2 until it goes away.
Last modified



This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP