• Font Size
  • S
  • M
  • L

Search via FAQ No.


  • No : 30608
  • Open Date : 2019/09/02 11:50
  • 更新日時 : 2020/09/15 10:54
  • Print

[DataSpider Servista] An error occurs upon a script execution or DataSpider Studio will not connect.

Problems in which an error (ScriptNotFoundException) occurs upon a script execution or DataSpider Studio will not connect occur irregularly.
 
When I checked the server log and the server standard error output, the following error was output. Please tell me about the cause and a way to resolve the problem.
 
java.lang.OutOfMemoryError: PermGen space
java.lang.OutOfMemoryError: Metaspace
 
 
Category : 

Answer

Error Condition
 
The error that we got on a report occurs when there is not enough space in Java's memory area that contains modules required to execute various processes, such as the DataSpider script information and classes.
 
This memory area is called the Metaspace area in Version 4.0 (JRE 1.8) or later versions, and the Permanent area (PermGen space) prior to Version 3.2 (JRE 1.7 or earlier).
 
Probable Cause
 
In the past case, there was a case in which the error occurred when a number of projects, scripts, and triggers got larger.
 
Workaround
 
Please expand the permanent area or the Metaspace area and check whether the problem is resolved.
 
Please refer to the following for how to change the settings. For details on the settings, refer to the help described in the reference information.
 
How to Change the Settings
  1. Stop DataSpiderServer
  2. Change the following setting file and setting key.
  • Setting file
$ DATASPIDER_HOME / server / bin / DataSpiderServer.lax
  • Setting key
lax.nl.java.option.additional
 
Please make the value after “=” of “-XX: MaxPermSize =” or “-XX: MaxMetaspaceSize =” specified for this key larger than the current value.
  1. Start DataSpiderServer
Notes
 
* An appropriate setting value varies depending on the operation and the setting contents so after you changed the value, please adjust the setting accordingly to whether the problem is resolved.
 
* Please note that -XX: MaxPermSize does not exist in the x64 version DataSpider Servista of the Windows OS version 2.x.
 
* The error described in Q does not occur in Version 2.x of the DataSpider for Windows x64.
 
* Due to the influence of JRE used by DataSpider Servista, the setting specified in the permanent area up to Version 3.2 (JRE 1.7 or earlier) has changed since Version 4.0 (JRE 1.8) to the Metaspace area.
 
Supplementary
 
A required permanent area capacity can be calculated from the Mapper settings.
(The calculation method of the Metaspace area for Version 4.0 or later versions is the same.)
 
* The following formula is the minimum required capacity calculation for the permanent area. Depending on the operation, more capacity may be required so please make sure to confirm whether the error is resolved after changing the actual settings,
 
The target range of the capacity calculation is the following Mapper:
  • All Mappers included in projects registered on the server
  • All Mappers in projects that contain scripts executed from Designer
For each mapper, the total capacity of the following is required:
  1. Input element, output element
150 bytes per each
* Not only columns but tables and rows are also applicable.
* It requires a capacity regardless of whether it is mapped or not.
  1. Logic icon
200 bytes per each
* It requires a capacity regardless of whether it is mapped or not.
  1. Script Variable, Component variable
150 bytes per each
* Unlike (1) and (2), a capacity is required only when mapped.
 
Example:
 
As an example, we will calculate the script capacity for the following settings:
  • Maps the data of 3 columns read from a database to 3 columns of the file writing process with [Simple Repetition]
  • Maps the "error_code" of component variables to script variables
([table] + [row] + [column] × 3) # input source
+ ([table] + [row] + [column] × 3) # output destination
+ [Simple Repetition]
+ ([Component Variable] + [Script Variable])
=
( 150 + 150 + 150 × 3 )
 + ( 150 + 150 + 150 × 3 )
 + 200
+ ( 150 + 150 )
= 2 KB
 
Also, if there are many mappers and the individual counts are not realistic, estimate the approximate capacity with the following formula:
 
(Mapper input element, the average number of output elements × 150 + average number of logic icons × 200 + Script variables being mapped, the average number of component variables × 150) × (a number of Mappers included in the project registered in the server + a number of Mappers included in projects that include scripts executed by Designer)
 
 
Reference information
  • Property reference
Prior to Version 3.2 (*Contents linked from this page might be in Japanese.)
 
Version 4.0 or later