Java operands are specified when a Java stored procedure or Java stored function is used. For details about Java stored procedures and Java stored functions, see the HiRDB Version 9 UAP Development Guide.
Note that some platforms on which HiRDB is run do not support Java stored procedures and Java stored functions. For details, see Environments in which Java stored procedures and Java stored functions can be used in the HiRDB Version 9 System Operation Guide.
- 39) pd_java_stdout_file = "Java-virtual-machine-standard-output-and-standard-error-output-destination-file"
- ~<path name>
- Specifies as an absolute path name the file to which the standard output and standard error output are to be output in a Java virtual machine.
- Specification guideline
- Because the size of the file specified by this operand is extremely large, this operand is not normally specified. It is recommended that this operand be specified during debugging of a Java stored procedure or Java stored function. There is no limit to the size of the file that can be specified by this operand.
- Operand default
- When this operand is omitted, the specification of the same operand in the server common definition, the unit control information definitions, or the system common definition, in that order, is assumed. When the same operand is also omitted in the server common definition, the unit control information definition, and the system common definition, the Java Virtual Machine standard output and standard error output are ignored.
- Note
- If there are simultaneous writing attempts from multiple processes, their output contents cannot be guaranteed.
- Operand rules
- Up to 255 characters can be used for the path name.
- 40) pd_java_castoff = Y | N
- Specifies whether to use the following events as triggers for shutting down the process at the server (single server, front-end server, dictionary server, or back-end server) that started the Java Virtual Machine:
No. | Server type | Process name | Trigger that ends process |
---|
1 | Single server | pdsds | UAP is disconnected |
2 | Front-end server | pdfes | UAP is disconnected |
3 | Dictionary server | pddic | Transaction is completed or UAP is disconnected |
4 | Back-end server | pdbes | Transaction is completed or UAP is disconnected |
- Y: Shut down server process when trigger occurs.
- N: Do not shut down server process when trigger occurs.
- Specification guidelines
- Normally, this operand is not specified. However, if you encounter the problems described below, we recommend that you specify Y in this operand:
- Use of the Java Virtual Machine causes the amount of memory usage to increase to the point where the available system memory becomes nearly exhausted.
- SQL code that includes numerous search conditions is executed, and even though the connection does not use the Java Virtual Machine, the maximum stack size set by the Java Virtual Machine on another connection prevents the stack from expanding, causing the server process to be aborted by a segmentation error.
- For details about the Java Virtual Machine facility, see the Java Virtual Machine documentation.
- Notes
- On systems that run Java stored routines frequently, specifying Y in this operand will generate overhead for server process restarts and Java Virtual Machine startups.
- Relationship to other operands
- This operand is related to the pd_process_count operand.