jobd dies and Scan Job killed when over certain number of Scan Rule Sets in Scan Rule Set Group

Symptoms

Scan Rule Set Group with N Scan Rule Sets (N varies) used in Scan Job, job killed and jobd process stops

Message in jobd.log:

2016-07-26 09:52:56,592 19503335 [Thread-1] WARN  com.exlibris.voyager.jobd.AbstractRunnableJob  - 
        Killed ScanJob (name = Scan Job Name, id = 204) at Tue Jul 26 09:52:56 CDT 2016

Also sometimes see java errors beginning with

Exception in thread "main" java.lang.OutOfMemoryError: Java heap space 

Defect Status

Issue VYG-7042 is currently in Development.

Replication Steps

1. Create Scan Rule Set Group with 25 or 30 Scan Rules (may occur with fewer).
2. Submit Scan Job with Scan Rule Set Group
3. When jobd starts the job
   1. in View Running/Completedstatus is Killed.
   2. jobd process stops and jobd.log message:

2016-07-26 09:52:56,592 19503335 [Thread-1] WARN  com.exlibris.voyager.jobd.AbstractRunnableJob  - 

        Killed ScanJob (name = Scan Job Name, id = 204) at Tue Jul 26 09:52:56 CDT 2016

Workaround

Create smaller Scan Rule Set Groups and run multiple scan jobs.

• Article last edited: 26-Jul-2016