- Top Category > General Questions > DataSpider Servista > [DataSpider Servista] Problems such as error （ScriptNotFoundException) upon script execution and not being able to connect to DataSpider Studio are happening irregularly.
Search via FAQ No.
[DataSpider Servista] Problems such as error （ScriptNotFoundException) upon script execution and not being able to connect to DataSpider Studio are happening irregularly.
Problems such as error （ScriptNotFoundException) upon script execution and not being able to connect to DataSpider Studio are happening irregularly.
The following error was output on the checking server log, server default error output.
Please tell us the cause and its resolution.
java.lang.OutOfMemoryError: PermGen space
- Category :
Answer
■Error Condition
The error you are inquiring about occurs when there is not enough permanent space, one of the memory spaces of Java. Modules, such as DataSpider script information, class, etc., required for various type of process are stored in the permanent space.
■Possible Cause
In the past we have seen this issue rise when excessive amount of projects, scripts and/or triggers are used.
■Countermeasure
Permanent space can be designated with -XX:MaxPermSize at DataSpiderServer.lax.
Please modify this and see if the problem will resolve.
For more details regarding the setting, please refer to the help section of Reference Information.
For details regarding the setting change, please refer to the following.
■Setting Change Methods
- Please stop DataSpiderServer
- Please change the following settings file and settings key
- Settings File
$DATASPIDER_HOME/server/bin/DataSpiderServer.lax
- Settings Key
lax.nl.java.option.additional
Please desginate a larger number (larger than [128M]) than what is currently specified on "-XX:MaxPermSize=128M."
- Start DataSpiderServer
■Caution
*Please be aware that -XX:MaxPermSize does not exist on Version 2.x of Windows OS x64 DataSpider Servista.
*Version 2.x Windows x64 DataSpider never had the error mentioned in the question
■Supplementary
A required permanent space capacity can be calculated from the Mapper setting description.
*The following equation is the minimum requirement for the permanent space.
Depending on your operation, you may need to allocate more capacity so please test with the necessary amount and see if that will resolve your issue.
The following Mapper is the subject to capacity calculation.
- All the Mapper included in project registered to the server.
- All the Mapper included in project which includes scripts that are executed by designer.
The following capacity total is required per Mapper.
- Input Element, Output Element
150 bytes per 1
*Not only columns, tables and rows are also subjects.
*Whether it is mapped or not does not change the fact that capacity is required.
- Logic Icon
200 byes per 1
*Whether it is mapped or not does not change the fact that capacity is required.
- Script Variable, Component Variable
1150 bytes per 1
*Unlike "1." and "2." the capacity is required only when it is mapped.
Example:
For example the setting script capacity is calculated as following.
- Map the three columns read from the database to the three file write process column by [Simple Repetition]
- Map the component variable "error_code" to a script variable
( [table] + [row] + [column] × 3 ) #input origin
+ ( [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
+ ( [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
If there are multiple variables and counting individually is unrealistic, please use the following equation to get an estimate capacity.
（Mapper input element, average number of output element × 150 +
average number of logic icon × 200 +
Mapped script variables, average number of component variables ×
150 ） ×
（The number of Mapper included in project registered to the server +
The number of Mapper included in project which includes scripts that are executed by designer）
average number of logic icon × 200 +
Mapped script variables, average number of component variables ×
150 ） ×
（The number of Mapper included in project registered to the server +
The number of Mapper included in project which includes scripts that are 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