J2SE property file format.
Specify the key as follows:
key-name=value
Specify the system properties of the JavaVM that execute the J2EE servers.
If you specify the same key in the usrconf.properties file and in -D of add.jvm.arg of the usrconf.cfg file, the value specified in usrconf.properties is given priority.
If you change the contents of this file while the J2EE server is running, the changes become effective only when the J2EE server is started next.
A J2EE server internally uses the keys beginning with the following prefixes. As a result, the keys beginning with these prefixes must not be used in applications.
You can customize the operations of the J2EE servers by setting the values in the following system property keys.
The keys are classified and described as follows:
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
cosminexus.jpa.logging.level.operation.category | Specify the log level for each category of the JPA provider operation log, when you are using the JPA functionality of the J2EE server. The category name and log level are case sensitive. If this key is not specified, the log is not output to the operation log. Since this affects the security and performance, take care when you specify the output level settings.
| Off | 08-00 |
cosminexus.jpa.exception.logging.sql# | Specify whether the exception message will include the SQL statement that caused the exception, when the JPA provider executes the SQL statement and receives an exception from the database.
| Off | 08-00 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.application.InitTermProcessClasses | When using the container extension library, specify the class name of server start/stop hook. When specifying multiple classes, demarcate them with a comma (,). Do not insert a space between the comma (,) and the class name. When a J2EE server is started, the server start hook method of the server start/stop hook functionality is invoked in the specified order. When a J2EE server is shutdown, the server stop hook method of the server start/stop hook functionality is invoked in the reverse order of the specified order. | None | -- |
ejbserver.application.userlog.CJLogHandler.handler-name#1.appname | Specify a single-byte character set of 0 to 16 bytes for the default application name that is output to the AppName field. If the value of the AppName field is not specified in the program, the value of this property is output to the AppName field. If the definition of the usable character sets is fulfilled, but the length of the value exceeds the limit, a warning message is output, the data exceeding the limit is truncated, and the data up to the restricted length is used. If you specify the string "null", this string is treated as a null character string "", and nothing is displayed in the appname field. You cannot specify the display of a "null" string in appname, from this property. | user_app | -- |
ejbserver.application.userlog.CJLogHandler.handler-name#1.count | Specify an integer in the following range for the number of log files:
If an old log file or a user file with the same name exists, the existing file is overwritten. | 2 | -- |
ejbserver.application.userlog.CJLogHandler.handler-name#1.encoding | Specify a value from 0 to 1024 bytes for the encoding of the strings to be output. If you do not specify any value, the default encoding is used. If the specified value exceeds the range, or if you specify a "null" string, it is treated as if encoding is not specified (default value in encoding is used). You cannot use an encoder named "null". In JavaVM, specify the character set that changes java.nio.charset.Charset.isSupported (String charsetName) to true. For the character sets that can be specified in encoding as well as the character strings to be specified, follow the specifications, such as java.nio.charset.Charset of Java standard API. Examples of specified values are as follows:
| null | -- |
ejbserver.application.userlog.CJLogHandler.handler-name#1.filter | Specify the filter to be used with its full name, including the package name. Specify the value as a class character set from 0 to 4096 bytes. Create the filter specified here using the Reflection functionality and use it for the handler of the specified handler name. If the specified value exceeds the range, it is assumed that the filter is not specified. Furthermore, if you specify a "null" string, it is again treated as no filter is to be used. Do not create a filter with the name "null". | null | -- |
ejbserver.application.userlog.CJLogHandler.handler-name#1.formatter | Specify the formatter that you will use along with its full name, including the package name. Specify the value as a class character set from 0 to 4096 bytes. The values that can be specified are as follows:
If the specified value exceeds the range, it is assumed that the formatter is not specified. Furthermore, if you specify a "null" string, it is treated as no formatter is to be used. Do not create a formatter with the name "null". | null | -- |
ejbserver.application.userlog.CJLogHandler.handler-name#1.level | Specify single-byte alphabets for the upper-limit of log collection level. You specify a value defined in the Java constant. This option is case-sensitive. Only messages of a level lower than the value specified here are output to the log. The specifiable levels are as follows:
| SEVERE | -- |
ejbserver.application.userlog.CJLogHandler.handler-name#1.limit | Specify an integer in the following range (units: bytes) for the capacity of a log file:
In the case of HNTRLib2, since the capacity check is done before writing the messages, there are times when the actual maximum capacity exceeds the set value by a maximum of approximately 4200 bytes (this is because messages are written if even one byte does not match the specified capacity). For example, if you specify 8192 in this key and when the area currently being used by out1.log is 8000 bytes, the free space is 192 bytes and if a message of 4000 bytes is output, the message is output to out1.log. As a result, the size of out1.log will exceed the upper-limit value. | 1048576 | -- |
ejbserver.application.userlog.CJLogHandler.handler-name#1.msgid | Specify a single-byte character set from 0 to 21 bytes for the default message ID that is output to the MsgID field. If the value of MsgID is not specified in the program, the value of this property is output to the MsgID field. If the definition of the usable character sets is fulfilled, but the length of the value exceeds the limit, a warning message is output, the data exceeding the limit is truncated, and the data up to the restricted length is used. If you specify "null", it is treated as a null character string "", and nothing is displayed in the msgid field. You cannot specify the display of a "null" string in msgid, from this property. | 0001 | -- |
ejbserver.application.userlog.CJLogHandler.handler-name#1.path | Specify a value from 1 to 255 bytes for the prefix of a log file name. Specify the path as a relative path#2. Do not specify a single-byte numeric value at the end of the path name. The value obtained by adding "xx (an integer between 1 to 16).log" to the prefix specified in this key forms the name of the trace information file. The single-byte alphanumeric characters specified in the path are not case-sensitive. Specify the length of the path value, such that the total of the following A + B + C values is within the range of the value:
Apart from the above, note the following when specifying the path:
| user_log | -- |
ejbserver.application.userlog.CJLogHandler.handler-name#1.separator | Use the CJSimpleFormatter and specify a single byte character set from 0 to 1024 bytes for the separator that is used to output the message. You can use the separator as a character string. If the definition of the usable character sets is fulfilled, but the length of the value exceeds the limit, a warning message is output, the data exceeding the limit is truncated, and the data up to the restricted length is used. In the case of output in the HNTRLib2 format, do not specify the following control characters in the message:
| | (Stroke) | -- |
ejbserver.application.userlog.loggers | This is a property that declares the name of the logger to be used. Specify a value from 0 to 65535 bytes. You can specify multiple logger names by demarcating with a comma (,). If you demarcate with a semicolon (;) immediately after the logger name, you can also specify the resource bundle name for regional correspondence used in that logger. Hitachi recommends that the logger name be a name based on the package name or the class name of the subsystem that is demarcated with a dot (.), such as java.net or javax.swing.#3 Do not use a comma (,) or a semicolon (;) in the logger name. If multiple class names are defined and the length of the specified value exceeds the range, only those class names whose length is within the range and which fulfill the rules of the value are set. The logger with the name declared in this key is processed as a logger built in the CJLogManager class (the logger is built when a J2EE server is started). The loggers that are not specified in this key are not generated automatically; therefore, create the loggers as per the codes. | None | -- |
ejbserver.application.userlog.Logger.logger-name#3.filter | This property specifies the filter used in the logger with its full name, including the package name. Specify the value as a class character set from 0 to 4096 bytes. The logger with the specified logger name creates the filter specified in this key by using the Reflection functionality and uses the filter to select messages. If the specified value exceeds the range, it is assumed that the filter is not specified. Furthermore, if you specify a "null" string, it is treated as no filter is to be used. Do not create a filter with the name "null". | Null | -- |
ejbserver.application.userlog.Logger.logger-name#3.handlers | This property is used to connect the handler class (addHandler(Handler)) to the specified logger name. To create the handler class using the Reflection functionality, specify a value from 0 to 65535 bytes for the handler class with a full name containing the package name. You can specify multiple handler classes by demarcating with a comma (,). You can specify the following handler classes:
Specify a class character set of 1 to 1024 bytes beginning with a single-byte alphanumeric character for the handler name. If multiple class names are defined and the length of the specified value exceeds the range, only those class names whose length is within the range and which fulfill the rules of the value are set. If the logger name is not specified in ejbserver.application.userlog.loggers, the logger is not created. | None | -- |
ejbserver.application.userlog.Logger.logger-name#3.level | Specify single-byte alphabets for the log output level of the logger or "null". This option is case-sensitive. To output a log message, you need to clear the log output level of the logger and the output level of the handler used for the output. The values that can be specified are as follows:
| SEVERE | -- |
ejbserver.application.userlog.Logger.logger-name#3.useParentHandlers | Specify single-byte alphabets for whether the log record is to be transmitted from the logger that received the log record to the handler that is connected to the parent logger. Specify true if the log record is to be transmitted and false if it is not to be transmitted. The log output level that passes through this logger affects only the level of the handler that is connected to the parent logger (If the level of the parent logger is OFF and the level of the handler that is connected to the parent logger is ALL, all messages are displayed). | true | -- |
ejb.server.log.directory-value\user or ejb.server.log.directory-value/user
If a logger name ends with .handlers, there may be confusion when the properties of ejbserver.application.userlog.Logger.logger-name.handlers are specified, and therefore, Hitachi recommends that you do not end a logger name with ".handlers".
The following table lists the specifiable key. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.client.ctm.RequestPriority | Specify an integer from 1 to 8 as the priority for extracting the requests accumulated in the queues within CTM. Smaller the value higher is the priority. If the specified value is wrong or omitted, 4 will be set. | 4 | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.commonj.WorkManager.non_daemon_work_threads | Specify an integer from 1 to 65535 for the maximum pool size of the thread pool for executing a short-lived Work in WorkManager. | 10 | 08-50 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.compiler.jvm.maxHeapSize | Specify the maximum value of the heap size of the javac command that is invoked when a J2EE application is started. Specify the value in the format that is accepted by the -Xmx and -Xms options of the java command. If you specify the value in any other format, the operation may not produce the desired results. Specify as follows:
| 256m | -- |
ejbserver.compiler.jvm.minHeapSize | Specify the initial value of the heap size of the javac command that is invoked when a J2EE application is started. Specify the value in the format that is accepted by the -Xmx and -Xms options of the java command. If you specify the value in any other format, the operation may not produce the desired results. Specify as follows:
| 32m | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name | Contents | Default value | VR | Related information |
---|---|---|---|---|
ejbserver.connectionpool.applicationAuthentication.disabled | Specify whether to enable the functionality for optimizing container management sign-on.
| false | -- | |
ejbserver.connectionpool.association.enabled | Specify whether to enable the connection association functionality in the 1.4 mode.
| false | -- | 3.14 Functionality for performance tuning in Common Container Functionality Guide |
ejbserver.connectionpool.association.enabledDespiteUnshareableSetting | Specify whether to perform connection association when Unshareable is specified in res-sharing-scope of the standard DD for servlets and Enterprise Beans.
If the connection association functionality is expected to be running in the application even when Unshareable is specified in res-sharing-scope (particularly, when two or more connections are acquired in local transactions), true must be specified. Do not specify this key, when developing a new application. | false | -- | |
ejbserver.connectionpool.sharingOutsideTransactionScope.enabled | Specify the operations of connection sharing when a connection is acquired multiple times outside the transactions managed by Application Server, in 1.4 mode. When NoTransaction is specified in the transaction support level of a resource adapter, connection sharing is not performed.
| false | -- | |
ejbserver.connectionpool.validation.timeout | Specify the timeout value for the functionality to detect connection failure and the timeout value (unit: seconds) for deleting connections using the functionality to adjust the number of connections as an integer from 1 to 2147483647. | 5 | 08-00 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.connector.logwriter.filenum | Specify an integer from 1 to 16 for the number of log files of a resource adapter. | 4 | -- |
ejbserver.connector.logwriter.filesize | Specify an integer from 4096 to 2147483647 (units: bytes) for the size of the log files of a resource adapter. | 2097152 | -- |
ejbserver.connector.statementpool.clear.backcompat | Specify the contents for initializing the statements when the statements are reused in the statement pooling functionality.
| true | 08-70 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name | Contents | Default value | VR | Related information |
---|---|---|---|---|
ejbserver.container.audit_trail.enabled | Specify whether to enable the database audit trail linkage functionality.
| false | -- | |
ejbserver.container.bmp.backcompatible | Specify operation lock control of an Entity Bean (BMP).
| false | -- | |
ejbserver.container.ejbhome.sessionbean.reconnect.enabled | Specify whether to enable the reconnection of EJB home object functionality.
| false | -- | |
ejbserver.container.passivate.scan.interval | Specify an integer from 0 to 2147483 (units: seconds) for the interval to invoke the thread for monitoring the timeout and pool status of an Enterprise Bean. When 0 is specified, monitoring is not performed. The thread for monitoring the timeout and pool status of an Enterprise Bean executes the following processing at the interval specified here:
| 0 | -- | 2.11 Setting up timeout in the EJB container in EJB Container Functionality Guide |
ejbserver.container.rebindpolicy | Specify re-connection and re-sending of requests in the EJB client, in the case of a communication failure when invoking the EJB method.
| VB_TRANSPARENT | -- | 2.13 Invoking the EJB remote interface in EJB Container Functionality Guide |
ejbserver.container.security.disabled | Specify whether to enable the functionality for controlling the access of Enterprise Bean. For details about the functionality used for controlling the access of Enterprise Beans, see 2.10 Access control for Enterprise Bean in the manual uCosminexus Application Server EJB Container Functionality Guide. This property is not related to the security policy specified in server.policy (security policy file for J2EE servers).
| false | -- | |
ejbserver.container.remove.scan.interval | Specify an integer from 0 to 153722867280912 (units: minutes) for the interval to invoke the thread for monitoring the timeout of an activated Stateful Session Bean. When you specify either 0 or a value below 0, the timeout is not monitored. If you specify a value greater than 153722867280912, 153722867280912 is set. If you specify a non-numeric value, the default value will be set. | 5 | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.ctm.ActivateTimeOut | This property is necessary for using the CTM functionality. When you deploy a J2EE application that uses the CTM functionality, the J2EE server activates the schedule queue. At this point, specify a value from 0 to 2147483647 for the standby time (units: seconds). If you specify 0, the standby time continues infinitely and when if you do not specify a value, 180 (seconds) is set. | 180 | -- |
ejbserver.ctm.CTMDomain | This property is necessary for using the CTM functionality. Specify an alphanumeric character from 1 to 31 or an underscore (_) for the CTM domain name to which the J2EE server belongs. You cannot specify a CTM domain name beginning with 'CTM' or 'ctm'. If you do not specify a value, "CTMDOMAIN" is set. | CTMDOMAIN | -- |
ejbserver.ctm.CTMID | This property is necessary for using the CTM functionality. Specify an alphanumeric character from 1 to 31, an underscore (_), or a period (.) for the CTM identifier of the CTM daemon that controls the J2EE server. You can, however, use a period (.) only when specifying the identifier as an IP address. You cannot specify a CTM identifier beginning with 'CTM' or 'ctm'. You also cannot specify a name that is same as the CTM domain name. If you do not specify a value, the IP address is set. | IP-address | -- |
ejbserver.ctm.CTMMyHost | This property is necessary for using the CTM functionality. Specify the host name or the IP address used by CTM in a node-switching environment, wherein multi-home or IP address is inherited. Specify a string of 1 to 64 characters for the host name or IP address. If you do not specify a value, the host name that can be acquired by the hostname command is set. If you specify this property without specifying the ejbserver.ctm.CTMID property, the IP address specified in this property becomes the default CTM identifier. | host-name-acquired-by-hostname-command | -- |
ejbserver.ctm.DeactivateTimeOut | When un-deploying the J2EE applications that use the CTM functionality, the J2EE server passivates the schedule queue. Specify a value from 0 to 2147483647 (units: seconds) for the standby time (awaiting completion of the running requests) at that point. If you specify 0, the standby time continues infinitely and when if you do not specify a value, 180 (seconds) is set. If you attempt to stop an application via CTM when the application contains some running requests, it is not possible to perform forced termination, and therefore, do not specify 0. | 180 | -- |
ejbserver.ctm.enabled | Specify whether to use the CTM functionality.
|
| -- |
ejbserver.ctm.QueueLength | A J2EE server generates the CTM queue, when J2EE applications that use the CTM functionality are deployed. Specify a value from 1 to 32767 for the length of the CTM queue at this point. If you do not specify a value, the length during the generation of the CTM queue maintained in the CTM daemon (length specified by the -CTMMaxRequestCount option) becomes valid. When the CTM queue is shared, since the CTM queue is already created, the already created length becomes valid instead of the specified value. | None | -- |
ejbserver.ctm.useGlobalJNDI | Switches the default lookup name used when no optional name is specified for Enterprise Bean in a configuration using the CTM functionality.
| false | 09-00 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name | Contents | Default value | VR | Related information |
---|---|---|---|---|
ejbserver.deploy.annotations.load_libjars.enabled | Specifies whether library JAR annotations will be read when a J2EE application is deployed.
| true | 09-50 | 12.3 Classes to be loaded and the class path required for loading in Common Container Functionality Guide |
ejbserver.deploy.app.stopforcibly.disabled | Specify whether to disable forced termination of a J2EE application.
| false | -- | |
ejbserver.deploy.annotations.load_check.enabled | Specify whether to ignore the exceptions occurred when loading the classes for acquiring the annotation information.
|
| 08-00 | 12.3 Classes to be loaded and the class path required for loading in Common Container Functionality Guide |
ejbserver.deploy.context.check_interval | Specify an integer (units: seconds) from 0 to 2147483647 for the interval to detect an update in the application setup file. If you specify a numeric character other than 0 and 1 to 2147483647, automatic reloading is performed. Only command reload is accepted. | 0 | -- | |
ejbserver.deploy.context.reload_scope |
| app | -- | |
ejbserver.deploy.context.update.interval | Specify an integer (units: seconds) from 0 to 2147483647 for the standby time for update of an application setup file. If you specify a numeric character other than 0 or 1 to 2147483647, it is assumed that there is no standby time. | 0 | -- | |
ejbserver.deploy.exclusive.lockAliveInterval | Specify an integer (units: seconds) from 1 to 2147483647 for the maximum standby time until the receipt of the next response sent from a command after the completion of server processing. The commands affected by this property are those classified as update, reference and privilege, from among the commands used in a J2EE server. The commands classified into update, reference and privilege can be checked in the list of commands used in J2EE servers. For details on the commands used in a J2EE server, see 2. Commands to be used in J2EE Server in the uCosminexus Application Server Command Reference Guide. If you specify an invalid value, a warning message is output and the default value will be set. If there is no communication from the command side even after the specified time, the server assumes invalid termination of the command and forcibly cancels command exclusion. The standby time is the total of the time that a command requires to go to and return from the servers and the processing time of the command. | 60 | -- | |
ejbserver.deploy.resourcefile.scramble.enabled | Specify whether to scramble the DD files related to DataSource, JavaMail, and ResourceAdapter that are expanded below the working directory. Even if the value of this property is switched and the J2EE server is started, the status of the DD files of the resource that is already imported or deployed does not change, as long as the definition information is not updated.
| false | -- | |
ejbserver.deploy.session.work.directory | Output the session information file of a Web application in the directory present below the set ejbserver.deploy.session.work.directory-property-value\web\context-root-name. |
| -- | |
ejbserver.deploy.stub.generation.scope | Specify the target range for generating the classes required for communication, such as stub. Specify ejb during new installation and app during upgradation.
| ejb | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name | Contents | Default value | VR | Related information |
---|---|---|---|---|
ejbserver.distributedtx.enableXidReuseOptimization | Specify whether to optimize the reuse of XID in the 1.4 mode.
| false | -- | |
ejbserver.distributedtx.ots.recoverFailMessageCount | Specify after how many retries in scanning unconcluded transactions would the KFCB40139-W message be displayed. Specify the value using an integer from 0 to 2147483647. Application Server scans unconcluded transactions for the resource manager participating in a transaction during transaction recovery executed when a J2EE server starts or when a communication failure occurs while a transaction is being concluded. If scanning fails, the Application Server continues to retry infinitely until the scanning process is successful; however, when the scanning of unconcluded transactions executed for resource adapters continues and fails for the number of times specified in this property, the KFCB40139-W message is displayed. Note that the unconcluded transactions are re-scanned every 5 seconds. If you specify 0, the KFCB40139-W message is not displayed even if the scanning of the unconcluded transactions fails several times. If you specify 1, the KFCB40139-W message is displayed if scanning fails once. (The KFCB40139-W message is not displayed when scanning fails on the second and subsequent attempts. However, if the scanning is successful once, or if the J2EE server is stopped, the count is reset. In this case, the KFCB40139-W message is displayed when the scanning fails once the next time). If you specify a value of 1 or more in this property, you can identify the inability to connect to a participating resource manager at an early stage. However, when you perform an operation in which a resource is started after starting the Application Server, the KFCB40139-W message might be displayed even for a normal operation. | 0 | 08-70 | |
ejbserver.distributedtx.ots.status.directory1# | Specify the directory for saving the backup of the status file of in-process transaction service and the status file used as maintenance data. You use a forward slash (/) as the path delimiter. If you specify a relative path, it indicates the path from the following directory:
| otsstatus | -- | 3.4 Managing transactions in Common Container Functionality Guide |
ejbserver.distributedtx.ots.status.directory2# | When replicating the status file of in-process transaction service, specify a directory that stores the backup of spare status files and the spare status files used as maintenance data. You use a forward slash (/) as the path delimiter. If you specify a relative path, the path will be from the execution directory of J2EE applications. You must specify a different directory to avoid overlapping with other J2EE servers or J2EE application processes running on the same machine. If you do not specify this property, a spare status file will not be created, and therefore, the status file does not get replicated. | None | -- | 3.4 Managing transactions in Common Container Functionality Guide |
ejbserver.distributedtx.recovery.completionCheckOnStopping.timeout | Specify a number from -1 to 2147483647 (units: seconds) for the timeout value to check whether the running transaction is complete, which is performed when using a global transaction and stopping the J2EE server and when using the Transacted Delivery functionality and stopping the J2EE application. However, the timeout does not occur in the following cases:
If you specify an integer from 0 to 2147483647, the transaction completion check times out when the specified time (seconds) elapses and the J2EE server or J2EE application stops even if it cannot be confirmed that there are no unconcluded transactions. To guarantee ACID of transactions when an application is running, you need to specify the settings where the timeout will not occur. You can specify the timeout settings, when convenience is given priority over ACID of transactions, during development of an application. | -1 (no timeout) | -- | |
ejbserver.distributedtx.recovery.port | Specify an integer from 1 to 65535 for the fixed port number used for transaction recovery when a global transaction is used in 1.4 mode. If you specify an invalid value or if the specified port is already being used, the invocation process is interrupted. If a light transaction is invoked considering it as valid, this property is ignored. | 20302 | -- | |
ejbserver.distributedtx.rollbackClientTxOnSystemException | Specify whether to mark an invoked client transaction for roll back, when a system exception occurs.
This property is enabled only in either of the following two cases, when the J2EE server is running in the 1.4 mode: When you start a client transaction, invoke the EJB (that implements the remote interface of J2EE server) by using the optimization for local invocation, and start a new transaction on the invoked EJB when you do not start the client transaction. | false (true, in the case of overwrite installation from 1.4 mode) | -- | |
ejbserver.distributedtx.XATransaction.enabled | Specify whether to use a global transaction in the 1.4 mode.
| false | -- |
The following table lists the specifiable key. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.DynamicStubLoading.Enabled | Specify whether to use dynamic class loading.
| false | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.ejb.cmp20.cmr.use.existing_table | This option uses the existing CMR table during deployment. Generally, a CMR table is generated during deployment so there is no need to use the existing CMR table. However, when recovering from an error, specify this option temporarily.
| false | -- |
ejbserver.ejb.timerservice.maxCallbackThreads | Specify an integer from 1 to 100 for the maximum number of threads that call back the timeout method in TimerService, in the entire J2EE server. | 1 | -- |
ejbserver.ejb.timerservice.retryCount | Specify an integer from 0 to 2147483646 for the maximum frequency for retrying to call back the timeout method in TimerService. | 1 | -- |
ejbserver.ejb.timerservice.retryInterval | Specify an integer (units: seconds) from 1 to 604800 for the interval for retrying to call back the timeout method in TimerService. | 5 | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name | Contents | Default value | VR | Related information |
---|---|---|---|---|
ejbserver.ext.method_observation.interval | If this property is set, it implies:
| 0 | -- | 5. Operating the J2EE Applications in Operation, Monitoring, and Linkage Guide |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.http.port | Specify an integer from 1 to 65535 for the port number of the simple Web server. You cannot specify a port number that is already being used in or secured for another application. Furthermore, do not specify the same value in port numbers of the ports to be used to communicate with the Web server in multiple J2EE servers. The cjstartsv command cannot start up multiple J2EE servers in which identical port numbers are specified. | 8080 | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.instrumentation.enabled | Specify whether to integrate with the Management Server.
| true | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.jca.adapter.tp1.bind_host | Specify the IP address or host name used for communication (receipt and dispatch) in the TP1 inbound integrated function. However, if you cannot resolve the address when the host name is specified, use the default value. | Valid local address selected automatically by the system | 08-50 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.jndi.cache | Specify whether to perform caching in naming. Specify ON if caching is to be performed, and OFF if caching is not to be performed. | on | -- |
ejbserver.jndi.cache.interval | Specify the interval (units: seconds) to clear a cache, when caching is done in naming. If you specify a value other than a number from 1 to 2147483647, the cache is not cleared. | 0 | -- |
ejbserver.jndi.cache.interval.clear.option | Decide the operations to be performed in the cache area of naming, after the lapse of the interval.
| refresh | -- |
ejbserver.jndi.cache.reference | Specify whether to use the caching functionality of DataSource object.
| off | -- |
ejbserver.jndi.global.enabled | Specify whether to register an object using the Portable Global JNDI name for the naming service, when starting the application.
| true | 09-00 |
ejbserver.jndi.namingservice.group.specify-group-name.providerurls | Specify the root position of naming services belonging to each group, with a provider URL. In specify-group-name, specify the group name that has been specified in ejbserver.jndi.namingservice.group.list. Code the provider URL by using the URL schema "corbaname".
| None | -- |
ejbserver.jndi.namingservice.group.list | Define the group of logical naming service that is to be searched during the round-robin search. The group name to be specified consists of alphanumeric characters (A-Z, a-z, 0-9) or underscores (_), and can be clearly identified in ejbserver.jndi.namingservice.group.list.
specify-group-name(;specify-group-name)* Note that * indicates iteration. | None | -- |
ejbserver.jndi.request.timeout | Specify an integer from 0 to 86400 for the timeout period (units: seconds) of communication with the naming service. If you specify 0, or if this property is not specified, the timeout does not occur. If a value greater than 86400 is set, a warning message is output and the timeout does not occur. | 0 | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.jpa.defaultJtaDsName | Specify the default JTA data source references. This property is used when jta-data-source is not specified in persistence.xml or when a space is specified. | None | 08-00 |
ejbserver.jpa.defaultNonJtaDsName | Specify the default non-JTA data source references. This property is used when non-jta-data-source is not specified in persistence.xml or when a space is specified. | None | 08-00 |
ejbserver.jpa.defaultProviderClassName | This property specifies the default JPA provider class name. This property is used when provider is not specified in persistence.xml or when a space is specified. | com.hitachi.software.jpa.PersistenceProvider | 08-00 |
ejbserver.jpa.disable# | Specify this property when using the JPA functionality of Application Server.
| false | 08-20 |
ejbserver.jpa.overrideJtaDsName | Specify the JTA data source references that will be used with a higher priority than the values specified in jta-data-source in persistence.xml and the values specified in ejbserver.jpa.defaultJtaDsName. | None | 08-00 |
ejbserver.jpa.overrideNonJtaDsName | Specify the non-JTA data source references that will be used with a higher priority than the values specified in non-jta-data-source in persistence.xml and the values specified in ejbserver.jpa.defaultNonJtaDsName. | None | 08-00 |
ejbserver.jpa.overrideProvider | Specify the JPA provider class name that will be used with a higher priority than the values specified in provider in persistence.xml and the values specified in ejbserver.jpa.defaultProviderClassName. | None | 08-00 |
ejbserver.jpa.emfprop.property-key | Specify the JPA provider-specific property keys. When all the persistence units are deployed, the properties with the prefix ejbserver.jpa.emfprop. removed will be passed to the JPA provider. | None | 08-00 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.jta.TransactionManager.defaultTimeOut | Specify the default value (units: seconds) for the transaction timeout of the transactions started on a J2EE server, in the following range:
| 180 | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name | Contents | Default value | VR | Related information |
---|---|---|---|---|
ejbserver.logger.channels.define.DevelopmentLogFile.filenum | Specify an integer from 1 to 6 for the number of log files to be output with the development check log functionality for J2EE servers. | 4 | 09-00 | |
ejbserver.logger.channels.define.DevelopmentLogFile.filesize | Specify an integer from 4096 to 2147483647 for the size of log files to be output with the development check log functionality for J2EE servers (unit: bytes). | 1048576 | 09-00 | |
ejbserver.logger.DevelopmentLogFile.level | Specify the log output level of the development check log functionality for J2EE servers. We recommend that you set up the INFO level during development. If you require more detailed information than the INFO level in order to investigate the errors in the application being developed, specify a level to output a more detailed log. You can specify the following values. The values are listed in order of the amount of information to be output from smallest to largest.
| OFF | 09-00 | |
ejbserver.logger.channels.define.channel-name#.filenum | Specify an integer from 1 to 16 for the number of log files of a J2EE server. |
| -- | |
ejbserver.logger.channels.define.channel-name#.filesize | Specify an integer from 4096 to 2147483647 (units: bytes) for the size of the log files of a J2EE server. |
| -- | |
ejbserver.logger.enabled.* | Specify the log level of a J2EE server. Specify either one or more from among Error, Warning, Information and Debug. If you specify only one log level, only the log of the applicable log level is output. When specifying more than one log levels, demarcate each level-name string with a comma (,). Normally, use the default value. | Error | -- | |
ejbserver.logger.systemlog.enabled | Specify whether to output the log of messages about invocation, stopping and abnormal termination of a J2EE server, to the event log (syslog in UNIX).
| true | -- | |
ejbserver.logger.rotationTime | Specify the time for switching the file to which the J2EE server log is output, in the HHMMSS format. If the time is not specified, the output destination is switched using the log file size. Note that even if this key is specified, the file size specification is valid. The output destination files are switched when the time specified in this key is reached or when the output destination file reaches the specified file size. | None | 09-00 | 3. Preparations for Troubleshooting in Maintenance and Migration Guide |
ejbserver.logger.rotationStyle | Specify the rules for naming a file when the file to which the J2EE server log will be output is switched.
| WRAP | 09-00 | 3. Preparations for Troubleshooting in Maintenance and Migration Guide |
For details about the acquisition of documents, see 2.3 Acquiring data in the manual uCosminexus Application Server Maintenance and Migration Guide.
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.management.JVM.stats_monitor.FullGCCount.enabled | Specify whether to enable the monitoring of the frequency of full garbage collection.
| true | -- |
ejbserver.management.JVM.stats_monitor.FullGCCount.threshold | Specify an integer from 1 to 2147483647 for the frequency that acts as the threshold value when monitoring the frequency of full garbage collection. | 10 | -- |
ejbserver.management.JVM.stats_monitor.FullGCCount.interval | Specify an integer from 1 to 2147483647 (units: seconds) for the threshold value-monitoring interval when monitoring the frequency of full garbage collection. | 600 | -- |
ejbserver.management.statistics.interval | Specify an integer from 1 to 86400 (units: seconds) for the statistics collection interval. | 60 | -- |
ejbserver.management.stats_file.base_time | Specify an integer from 0 to 1439 (units: minutes) as the base time for the time switching operation of the statistics file, by incrementing from the local time 1970-01-01 00: 00: 00. When the local time 1970-01-01 hh: mm is taken as the base, specify h ![]() | 0 | -- |
ejbserver.management.stats_file.dir | Specify the directory to output the statistics file. When changing the output destination directory, specify a separate directory for each J2EE server. |
| -- |
ejbserver.management.stats_file.enabled | Specify whether to enable the functionality to output the statistics file.
| true | -- |
ejbserver.management.stats_file.num | Specify an integer from 2 to 168 for the number of statistics file. | 7 | -- |
ejbserver.management.stats_file.period | Specify an integer from 1 to 744 (units: hours) for the switching period in the time switching operation of the statistics file. | 24 | -- |
ejbserver.management.webcontainer.stats_monitor.whole_waiting_request_count.enabled | Specify whether to enable the monitoring of the total pending request count for Web containers.
| true | 09-00 |
ejbserver.management.webcontainer.stats_monitor.whole_waiting_request_count.high_threshold | Specify an integer from 1 to 100 (unit: %) as the percentage when a message is output to convey that the percentage of the total pending request count for Web containers has reached the warning level. Specify a value of ejbserver.management.webcontainer.stats_monitor.whole_waiting_request_count.low_threshold or more. If the percentage of the total pending request count for Web containers is greater than the specified value, the message is displayed. If you specify 100, an alert message is displayed when the storage ratio of the total pending request count for Web containers becomes 100%. | 80 | 09-00 |
ejbserver.management.webcontainer.stats_monitor.whole_waiting_request_count.low_threshold | Specify an integer from 0 to 99 (unit: %) as the percentage when a message is output to convey that the percentage of the total pending request count for Web containers has reached the normal level. Specify a value of ejbserver.management.webcontainer.stats_monitor.whole_waiting_request_count.high_threshold or less. If the percentage of the total pending request count for Web containers is less than the specified value, the message is displayed. If you specify 0, an alert message is displayed when the storage ratio of the total pending request count for Web containers becomes 0%. | 0 | 09-00 |
ejbserver.management.webcontainer.stats_monitor.waiting_request_count.enabled | Specify whether to enable the monitoring of the pending request count for Web containers.
| true | 09-00 |
ejbserver.management.webcontainer.stats_monitor.waiting_request_count.high_threshold | Specify an integer from 1 to 100 (unit: %) as the percentage when a message is output to convey that the percentage of the pending request count for Web containers has reached the warning level. Specify a value of ejbserver.management.webcontainer.stats_monitor.waiting_request_count.low_threshold or more. If the percentage of the pending request count for Web containers is greater than the specified value, the message is displayed. If you specify 100, an alert message is displayed when the storage ratio of the pending request count for Web containers becomes 100%. | 80 | 09-00 |
ejbserver.management.webcontainer.stats_monitor.waiting_request_count.low_threshold | Specify an integer from 0 to 99 (unit: %) as the percentage when a message is output to convey that the percentage of the pending request count for Web containers has reached the normal level. Specify a value of ejbserver.management.webcontainer.stats_monitor.waiting_request_count.high_threshold or less. If the percentage of the pending request count for Web containers becomes less than the specified value, the message is displayed. If you specify 0, an alert message is displayed when the storage ratio of the pending request count for Web containers becomes 0%. | 0 | 09-00 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.manager.agent.Agent.conf | Specify the settings required for integrating with the Management Server. The Management Server automatically sets these contents in a J2EE server. For details on the contents set up automatically by the Management Server in a J2EE server, see Appendix E.5 Contents set up automatically by the Management Server in a J2EE server in the uCosminexus Application Server System Setup and Operation Guide. | None | -- |
ejbserver.manager.agent.Agent.enabled | Specify the settings required for integrating with the Management Server. The Management Server automatically sets these contents in a J2EE server. For details on the contents set up automatically by the Management Server in a J2EE server, see Appendix E.5 Contents set up automatically by the Management Server in a J2EE server in the manual uCosminexus Application Server System Setup and Operation Guide. | false | -- |
ejbserver.manager.agent.JP1EventAgent.conf | Specify the path of the setup file for JP1 integration. | None | -- |
ejbserver.manager.agent.JP1EventAgent.enabled | Specify whether to integrate with JP1. | false | -- |
ejbserver.manager.jp1event.event_server_name | Specify a value similar to the address of the ports parameter that is specified in the event server setup file (conf) of the event service of JP1/Base in use. If multiple addresses are specified in the ports parameter, specify any one of the specified addresses. If you use an event service, wherein "0.0.0.0" (default value) is specified in the address of the ports parameter, either omit this key or specify the host name of the local machine or localhost. | localhost | -- |
ejbserver.manager.agent.MEventAgent.conf | Specify an absolute path for the property file for issuing the Management event. If you do not specify the property file, or if the specified file does not exist, the Management event is not issued. For details on property file for issuing the Management event, see 10.12 Property file for issuing Management events. | None | -- |
ejbserver.manager.agent.MEventAgent.enabled | Specify whether to enable the functionality for issuing the Management event.
| false | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.naming.exec.args | Specify the runtime option added in the CORBA Naming Service that is invoked when the CORBA Naming Service is used in the automatic invocation mode (ejbserver.naming.startupMode=automatic or inprocess). Generally, there is no need to set a value in this property. This property is used to determine, take action and avoid any failures in the CORBA Naming Service, when the CORBA Naming Service is used in the automatic invocation mode. For the runtime option, specify the string in the format that is specified in the command line argument of nameserv (specify by adding -J at the beginning of each property and demarcating with a space. It is actually specified in one line). (Example of specification) ejbserver.naming.exec.args=-J-Dvbroker.se.iiop_tp.scm.iiop_tp.listener.port=900
For details about the properties that you can specify when executing the CORBA Naming Service, see the manual Borland(R) Enterprise Server VisiBroker(R) Developers Guide and the manual Borland(R) Enterprise Server VisiBroker(R) Programmers Reference. | None | -- |
ejbserver.naming.host | Specify the host name or the IP address that invoke the CORBA Naming Service that the J2EE server uses. When using the name switching functionality, do not use "localhost" as the host name. Specify the host name or the IP address that the CORBA Naming Service invokes. If the CORBA Naming Service is used in the automatic invocation mode (ejbserver.naming.startupMode=automatic or in-process), specify either the default value ("localhost"), or the host name or IP address that starts the J2EE server. | localhost | -- |
ejbserver.naming.nameroot | Specify a name when the name is added to the CORBA Naming Service that is invoked, when the CORBA Naming Service is used in the automatic invocation mode (ejbserver.naming.startupMode=automatic or in-process). Specify the name with a string consisting of alphanumeric characters (A-Z, a-z, 0-9) or underscores (_). This name is used in the parameters of the nsutil command of VisiBroker. If a name is not specified, the name "NameService" is automatically set in VisiBroker. For details about how to use the nsutil command, and also about its usage conditions, see the manual Borland(R) Enterprise Server VisiBroker(R) Developers Guide. | None | -- |
ejbserver.naming.port | Specify an integer from 1 to 65535 for the port numbers of the CORBA Naming Service that the J2EE server uses. You cannot specify a port number that is already being used by another application. If the J2EE server is started by specifying a port number that is already being used by another application, the invocation process might not be finished. | 900 | -- |
ejbserver.naming.protocol | Specify the access protocol to the CORBA Naming Service that is used in the J2EE servers. Currently, this key supports only corbaname. You can, however, perform the operations even with the protocols (iioploc or iiopname) that were in use in the older versions. | corbaname | -- |
ejbserver.naming.startupMode# | Specify the invocation mode of the CORBA Naming Service.
|
| -- |
ejbserver.naming.startupRetryCount | If the CORBA Naming Service still does not start after the lapse of invocation wait time of the CORBA Naming Service that is specified in ejbserver.naming.startupWaitTime, specify an integer from 0 to 2147483647 for the iteration frequency to await invocation only for the number of seconds specified in ejbserver.naming.startupWaitTime. If you specify 0, the process for checking invocation status of the CORBA Naming Service is not retried If you specify 0 in ejbserver.naming.startupWaitTime, this property value is invalid. |
| -- |
ejbserver.naming.startupWaitTime | Specify an integer from 0 to 2147483647 for the standby time (units: seconds) until the CORBA Naming Service becomes available when a J2EE server is started. When you specify 0, invocation of the CORBA Naming Service is not awaited. If inprocess is set in ejbserver.naming.startupMode, do not specify 0. |
| -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name | Contents | Default value | VR | Related information |
---|---|---|---|---|
ejbserver.rmi.localinvocation.scope | Specify the scope of the functionality for optimizing local invocation.
| app | -- | |
ejbserver.rmi.logger.filenum | Specify an integer from 2 to 16 for the number of RMI communication log files of a J2EE server. If you specify a non-numeric value, or a numeric value outside the range, or if you do not specify a string, a message is output and the default value will be set. | 4 | -- | |
ejbserver.rmi.logger.filesize | Specify an integer from 8192 to 2147483647 (units: bytes) for the size of the RMI communication log files of a J2EE server. | 1048576 | -- | |
ejbserver.rmi.naming.host | Specify the host name or the IP address of the RMI registry and MBean server that the J2EE server uses in a multi-homed host environment. The specified single-byte alphabets are not case-sensitive. | None | -- | |
ejbserver.rmi.naming.port | Specify an integer from 1 to 65535 for the port number of RMI registry used by the J2EE server. You cannot specify a port number that is already being used by another application. If the J2EE server is started by specifying a port number that is already being used by another application, the invocation process may not finish. | 23152 | -- | |
ejbserver.rmi.passbyreference# | If you specify true, the arguments and the return value are not passed by value but are passed by reference, by invoking the EJB method that contains the remote interface. If, however, the range specified in ejbserver.rmi.localinvocation.scope is exceeded when invoking the EJB method, the pass-by-reference functionality becomes disabled. With the help of pass-by-reference, you can reduce the cost generated by copying the value, but, you need to be careful as the original value can be changed by using the reference that has been passed. | false | -- | |
ejbserver.rmi.remote.listener.port | You can specify optional values to fix the request reception port for the statistics information acquisition by the JMX client (such as Administration Agent and JP1/Performance Management - Agent Option for uCosminexus Application Server). Specify an integer from 0 to 65535. You cannot specify a port number that is already being used by another application. If the J2EE server is started by specifying a port number that is already being used by another application, the invocation process may not finish. When this property is not specified, or when 0 is specified as the value, random values will be set up. | 0 | -- | |
ejbserver.rmi.request.timeout | Specify an integer from 0 to 86400 for the communication timeout period (unit: seconds) between the client and server. If you specify 0, or if this property is not specified, the timeout does not occur. Note that if a value exceeding 86400 is set, a warning message is output, and there is no timeout. | 0 (seconds) | -- | |
ejbserver.rmi.stateless.unique_id.enabled | Specify whether the invocation of the remove method of Stateless Session Bean is required.
| false | -- | 4.3.1 Notes on implementing the Stateless Session Beans in EJB Container Functionality Guide |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Key name | Contents | Default value | VR | Related information |
---|---|---|---|---|
ejbserver.server.eheap.ajp13.enabled | Specify whether to deploy the objects for communication with the redirector on the Explicit heap.
| true | 08-00 | |
ejbserver.server.eheap.httpsession.enabled | Specify whether to deploy the objects, stored in the HTTP session, on the Explicit heap.
| true | 08-00 | |
ejbserver.server.j2ee.feature | Specify the operation mode of Component Container.
| 1.4 | -- | |
ejbserver.server.mutex.invocation.timeout | Specify an integer from 45 to 92233720368547758 for the exclusive timeout period (units: seconds) required to concurrently access the Entity Beans of the same primary key. Specify the timeout period above the default value (45 seconds) and below the java.lang.Long.MAX_VALUE/1000 (seconds). If you specify a value lesser than the default value, the timeout period is considered as 45 (seconds). If you specify a value greater than java.lang.Long.MAX_VALUE/1000 (seconds), the timeout period is considered as java.lang.Long.MAX_VALUE (milliseconds). Similarly, if you specify a value greater than java.lang.Long.MAX_VALUE, the default value is considered. | 45 | -- | |
ejbserver.server.prf.PRFID | Specify the PRF identifier. If you specify a PRF identifier when the PRF daemon is invoked, specify the same PRF identifier. If the PRF identifier is omitted when invoking the PRF daemon, do not specify the PRF identifier. If the PRF identifiers do not match, the performance analysis trace is not collected. | PRF_ID | -- | |
ejbserver.server.threaddump.filenum | Specify an integer from 1 to 2147483647 for the upper limit of the thread dump file count, when the J2EE server detects an error and voluntarily outputs the thread dump. If you specify a value outside the range, the default value will be set. If the environment variable JAVACOREDIR is specified, the current value is a total of the number of thread dump files in both the directory specified in the environment variable JAVACOREDIR and the default output destination directory (Windows: Cosminexus-working-directory\ejb\server-name, Unix: Cosminexus-working-directory/ejb/server-name). If there is an external request to output the thread dump, the files of thread dump are output, regardless of the setting of this option. The following are examples of external requests to output the thread dump.
| 256 | -- | 4. Monitoring Resource Depletion in the Operation, Monitoring, and Linkage Guide |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.stateful.passivate.switch | Specify whether to use the functionality for passivating and activating the Stateful Session Bean.
| false | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.stdoutlog.autoflush | Specify whether to enable the automatic flush functionality of the user output log and user error log. The automatic flush functionality is the automatic flush option of java.io.PrintStream used for the output of user output log (user_out[n]log) and user error log (user_err[n].log).
| false | 08-00 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.watch.defaultRequestQueue.enabled | Specify whether to enable the alert output to monitor pending queues of HTTP requests, in the case of the default pending queue.
| true | -- |
ejbserver.watch.defaultRequestQueue.interval | Specify an integer from 1 to 2147483647 (units: seconds) for the interval to monitor the pending queues of HTTP requests, in the case of the default pending queue. | 30 | -- |
ejbserver.watch.defaultRequestQueue.threshold | Specify an integer from 1 to 100 (units: %) for the threshold value to output alert messages. If the storage ratio of the default pending queue for the requests to be monitored exceeds the value specified in this key, an alert message will be output. | 80 | -- |
ejbserver.watch.defaultRequestQueue.writefile.enabled | Specify whether to output the results to monitor pending queues of HTTP requests to a file, in the case of the default pending queue.
| true | -- |
ejbserver.watch.enabled | Specify whether to enable the depletion monitoring of all the resources.
| true (false, when version is upgraded from 06-00 or earlier version) | -- |
ejbserver.watch.fileDescriptor.enabled | Specify whether to enable the alert output for file descriptor monitoring. Note that file descriptor monitoring cannot be used in Windows and AIX.
| true | -- |
ejbserver.watch.fileDescriptor.interval | Specify an integer from 1 to 2147483647 (units: seconds) for the interval for monitoring file descriptor. Note that file descriptor monitoring cannot be used in Windows and AIX. | 60 | -- |
ejbserver.watch.fileDescriptor.threshold | Specify an integer from 1 to 2147483647 for the threshold value to monitor the usage of a file descriptor. When the number of in-use file descriptors exceeds the threshold value, an alert will be output. Set the threshold value in the following manner: The number of file descriptors that can be allocated in the OS processes# > Value acquired from the file descriptor estimation formula > File descriptor threshold value # On some platforms, the system may not have any upper limit. Note that file descriptor monitoring cannot be used in Windows and AIX. | 2147483647 | -- |
ejbserver.watch.fileDescriptor.writefile.enabled | Specify whether to output the results of file descriptor monitoring in a file. Note that file descriptor monitoring cannot be used in Windows and AIX.
| true | -- |
ejbserver.watch.memory.enabled | Specify whether to enable alert output of memory monitoring.
| true | -- |
ejbserver.watch.memory.interval | Specify an integer from 1 to 2147483647 (units: seconds) for the memory-monitoring interval. | 60 | -- |
ejbserver.watch.memory.threshold | Specify an integer from 1 to 100 (units: %) for the threshold value to monitor the memory usage status. If signs of a full garbage collection are detected, an alert is output in any of the following conditions:
| 80 | -- |
ejbserver.watch.memory.writefile.enabled | Specify whether to output the results of memory monitoring in a file.
| true | -- |
ejbserver.watch.thread.enabled | Specify whether to enable alert output of thread monitoring. Note that you cannot monitor the number of threads in Linux.
| true | -- |
ejbserver.watch.thread.interval | Specify an integer from 1 to 2147483647 (units: seconds) for the thread monitoring interval. Note that you cannot monitor the number of threads in Linux. | 60 | -- |
ejbserver.watch.thread.threshold | Specify an integer from 1 to 2147483647 for the threshold value for monitoring the usage of threads. When the number of generated threads is greater than the threshold value, alert will be output. Set the threshold value in the following manner: The number of threads that can be allocated in the OS processes#>Value acquired from the thread estimation formula>Thread threshold value # On some platforms, the system may not have any upper limit. Note that you cannot monitor the number of threads in Linux. | 2147483647 | -- |
ejbserver.watch.thread.writefile.enabled | Specify whether to output the results of thread monitoring to a file. Note that you cannot monitor the number of threads in Linux.
| true | -- |
ejbserver.watch.threaddump.enabled | Specify whether to enable alert output of thread dump monitoring.
| true | -- |
ejbserver.watch.threaddump.interval | Specify an integer from 1 to 2147483647 (units: seconds) for the intervals in the thread dump monitoring period. | 30 | -- |
ejbserver.watch.threaddump.threshold | Specify an integer from 1 to 100 (units: %) for the ratio of the threshold value for thread dump monitoring with respect to the maximum value. When the ratio of the current value with respect to the maximum value of number of files of thread dump is greater than the threshold value, alert will be output. If the environment variable JAVACOREDIR is specified, the current value is a total of the number of thread dump files in both the directory specified in the environment variable JAVACOREDIR and the default output destination directory. | 80 | -- |
ejbserver.watch.threaddump.writefile.enabled | Specify whether to output the results of thread dump monitoring to a file.
| true | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
ejbserver.webj2ee.connectionAutoClose.enabled | Specify whether to use the automatic close functionality, when the J2EE server operates in 1.4 mode. When the operating mode is basic mode (compatible functionality), this property is ignored and the automatic close functionality is disabled.
| true | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
https.cipherSuites | Specify the recommended coding suite to be used in HttpsURLConnection.# | # | 09-00 |
https.protocols | Specify the protocol to be used in HttpsURLConnection.# | # | 09-00 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
java.naming.factory.initial | Specify the factory class for the implementation class of the context delegated by InitialContext of JNDI. The operation for each set value is as follows:
| com.hitachi.software.ejb.jndi.InsContextFactory | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
vbj.java2iiop.jvm.maxHeapSize | Specify the maximum heap size of the java2iiop command that is invoked when a J2EE application is started. Specify the value in the format that is accepted by the -Xmx and -Xms options of the java command. If you specify the value in any other format, the operation may not produce the desired results. Specify as follows:
| 128m | -- |
vbj.java2iiop.jvm.minHeapSize | Specify the initial heap size of the java2iiop command that is invoked when a J2EE application is started. Specify the value in the format that is accepted by the -Xmx and -Xms options of the java command. If you specify the value in any other format, the operation may not produce the desired results. Specify as follows:
| 16m | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
vbroker.agent.enableLocator | Specify whether to use the Smart Agent. Normally, this property need not be set. You use the default settings for this key. When the CTM linkage functionality is valid (true is specified to the ejbserver.ctm.enabled key) true is automatically set up when you start the J2EE server. If the Smart Agent is required for any other purpose than above, set true. Note that if true is set in this property, the Smart Agent needs to be invoked first. For details about the Smart Agent, see the manual Borland(R) Enterprise Server VisiBroker(R) Programmers Reference. | false | -- |
vbroker.agent.port | Specify the port number of Smart Agent. For details, see the manual Borland(R) Enterprise Server VisiBroker(R) Programmers Reference. | 14000 | -- |
vbroker.ce.iiop.ccm.htc.readerPerConnection | Specify whether the closing of the connection will be controlled when a timeout occurs during the invocation of the EJB method defined as the remote interface.
| false | 09-50 |
vbroker.ce.iiop.ccm.htc.threadStarter | Specify whether to invoke the thread for managing the reply receiving threads. To set up vbroker.ce.iiop.ccm.htc.readerPerConnection=true, specify true. | false | 09-50 |
vbroker.orb.htc.comt.entryCount | Specify a value from 100 to 30000000 for the upper-limit of the entry count in one communication trace file of Cosminexus TPBroker. | 120000 | -- |
vbroker.orb.htc.comt.fileCount | Specify a value from 1 to 256 for the upper-limit of the communication trace file count for Cosminexus TPBroker. | 3 | -- |
vbroker.orb.htc.tracePath | Specify a range of 1 to 210 bytes for the path of the output destination of Cosminexus TPBroker trace files. You need to create comtrc and mdltrc as the subdirectories of the specified path beforehand. In the case of default output destination, the subdirectories comtrc and mdltrc are automatically created when the server is started for the first time. Use a forward slash (/) as the delimiter in the directory path. For example, in Windows, if C\temp\work is to be set as the work directory, specify as follows: (Example of specification) vbroker.orb.htc.tracePath=c:/temp/work |
| -- |
vbroker.se.iiop_tp.host | Set the IP address of the EJB container for each J2EE server by specifying any optional value. | None | -- |
vbroker.se.iiop_tp.proxyHost# | Specify the name of the host where the J2EE server and CORBA Naming Service are allocated. Set up the host name such that the name is resolved as a NAT IP address with the EJB client. Also, if the EJB client does not use NAT, specify settings such that the name is resolved as a J2EE server IP address with the host. | None | 09-50 |
vbroker.se.iiop_tp.scm.iiop_tp.listener.port | You can set a communication port for each J2EE server, by specifying any optional value. Make sure that the port number is not the same as that of any other program. If this property is not set, Cosminexus TPBroker sets a random value. Moreover, if you specify true in ejbserver.container.ejbhome.sessionbean.reconnect.enabled, make sure to specify the value and then fix the port number. | 0 | -- |
vbroker.se.iiop_ts.proxyHost# | Specify the name of the host where the J2EE server and CORBA Naming Service are allocated. Set up the host name such that the name is resolved as a NAT IP address with the EJB client. Also, if the EJB client does not use NAT, specify settings such that the name is resolved as a J2EE server IP address with the host. | None | 09-50 |
# CORBA Naming Service invocation mode settings |
If the CORBA Naming Service is invoked automatically as an out-process, specify these keys in both; the user property file for J2EE servers and the user property for J2EE servers ejbserver.naming.exec.args. The following is an example of settings where the host name of the computer on which the J2EE server is allocated is MyJ2EEHost. Specify the settings for ejbserver.naming.exec.args on one line, delimited with spaces for each -J. Also, if a value is set up for ejbserver.naming.exec.args in the existing system, specify that value for the command additionally.
# CORBA Naming Service invocation mode settings |
If the CORBA Naming Service is invoked manually as an out-process, specify these keys in both, the user property file for J2EE servers and the invocation option of the nameserv command. The following is an example of settings where the host name of the computer on which the J2EE server is allocated is MyJ2EEHost:
# CORBA Naming Service invocation mode settings |
An example of executing the nameserv command is as follows. Note that to execute the nameserv command, specify the settings on one line, delimited with spaces for each -J. Also, if the nameserv command is being executed in the existing system, add a postscript to that command.
nameserv -J-Dvbroker.agent.enableLocator=false |
The following table lists the specifiable key. Note that Default value is the value that is assumed when the key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.application.lower_version | Specify the version of the Web application that you want to set with the version setup functionality of the Web application. When you specify 2.4, Web applications of version 2.4 or earlier as defined in web.xml are executed as Web applications of version 2.4. When you specify 2.5, Web applications of version 2.5 or earlier as defined in web.xml are executed as Web applications of version 2.5. | None | 08-20 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.connector.ajp12.backlog | This key is used to maintain compatibility with the older versions. This key is used as webserver.connector.ajp13.backlog. For details about specifiable values, see the explanation of the webserver.connector.ajp13.backlog key. When both, this key and the webserver.connector.ajp13.backlog key are specified, the value of the webserver.connector.ajp12.backlog key is used. | None | -- |
webserver.connector.ajp12.max_threads | This key is used to maintain compatibility with the older versions. This key is used as webserver.connector.ajp13.max_threads. For details about specifiable values, see the explanation of the webserver.connector.ajp13.max_threads key. When both, this key and webserver.connector.ajp13.max_threads are specified, the value of the webserver.connector.ajp12.max_threads key is used. When you set 1025 or more than this value, the default value 100 is used for webserver.connector.ajp13.max_threads. | None | -- |
webserver.connector.ajp12.port | This key is used to maintain compatibility with the older versions. This key is used as webserver.connector.ajp13.port. For details about specifiable values, see the explanation of the webserver.connector.ajp13.port key. When both, this key and webserver.connector.ajp13.port are specified, the value of the webserver.connector.ajp12.port key is used. | None | -- |
webserver.connector.ajp13.backlog | Specify the maximum number of rows and columns awaiting connection requests from the redirector. Specify the value using an integer from 1 to 2147483647. The valid maximum value becomes the maximum value of the Listen queue in the Socket specifiable on the platform to be used. The actual maximum value of the Listen queue depends on the OS. For details, see the manuals for the listen functionality in each OS. The value specified in this key is set in the backlog argument of java.net.ServerSocket class constructor. If, however, this specified value exceeds the limit value set for the OS, it is interpreted as the limit value of the OS, and it therefore does not result in an error. The limit value is different for every OS. For details on how to extend the limit value, see the OS manual. | 100 | -- |
webserver.connector.ajp13.bind_host | Specify the IP address or the host name used for Web server integration. The single-byte space before and after the IP address or the host name is ignored. If you do not specify a value, the wild card address is used. When specifying this property, you need to specify the local host name or the IP address even in the worker host name. In a configuration wherein a Web server is integrated with another Web server running on the same host, the Web Container cannot receive requests from the Web server if either of the following settings is specified:
| None | -- |
webserver.connector.ajp13.max_threads | Specify the concurrently executing number of requests being processed by the Web container.#1 Specify the value using an integer from 1 to 1024. Number of threads equal to the concurrently executing number of specified requests is generated when the server is started. | 10 | -- |
webserver.connector.ajp13.port | Specify the port number used for communication with the Web server. Specify the value using an integer from 1 to 65535. You cannot specify a port number that is already being used or secured for another application. Furthermore, do not specify the same value in port numbers of the ports to be used to communicate with the Web server in multiple J2EE servers. The cjstartsv command cannot start up multiple J2EE servers in which identical port numbers are specified. | 8007 | -- |
webserver.connector.ajp13.receive_timeout | Specify an integer from 0 to 3600 (units: seconds) for the period to await a response (communication timeout value) from the redirector, while the data request is being processed in the redirector (that processes requests). If you specify 0, the waiting period continues until a response is received from the redirector and the timeout will not occur. | 600 (seconds) | -- |
webserver.connector.ajp13.send_timeout | Specify an integer from 0 to 3600 (units: seconds) for the timeout value for sending response. If you specify a non-numeric value, or a numeric value outside the range, a message will be output and the default value will be used. If 0 or a time period longer than the resend timer of data transmission present in the TCP is set, the timeout value will be the timeout value of the TCP. In such a case, a message indicating that an invalid timeout value has been specified will not be output. | 600 | -- |
webserver.connector.http.bind_host | Specify the local IP address or a resolvable local host name used in the simple Web server. The single-byte space before and after the IP address or the host name will be ignored. If you do not specify a value, the wild card address is used. | None | -- |
webserver.connector.http.permitted.hosts | Specify the IP address (decimals) or the name of the host that has permission to access the simple Web server. Note that the local host can always be accessed even if it is not specified. As a result, if this key is not specified, you can access only the local host. When specifying multiple hosts, demarcate the IP addresses or the host names with a comma (,). If there are no access restrictions, specify only an asterisk (*). The single-byte space before and after the IP address or the host name is ignored. | None | -- |
webserver.connector.inprocess_http.backlog | Specify an integer from 1 to 2147483647 for the length of the TCP listen queue that saves the connection requests from the Web client. The maximum valid specified value or the length of the TCP listen queue that is actually set, is different for every OS. If you specify a non-numeric value, a numeric value outside the range, a null character string, or a whitespace#2, a message is output and the default value will be set. | 511 | -- |
webserver.connector.inprocess_http.bind_host | Specify the IP address or the host name used in an in-process HTTP server. The single-byte space before and after the IP address or the host name is ignored. If you do not specify a value, the wild card address is used. If the specified host name or the IP address cannot be resolved and if you specify the name or IP address of a host that is not local, a message is output and the wild card address is used. | None | -- |
webserver.connector.inprocess_http.enabled | Specify whether to enable the in-process HTTP server functionality.
Note that, if the in-process HTTP server functionality is enabled, Web server integration cannot be used. | false | -- |
webserver.connector.inprocess_http.enabled_methods | Specify the HTTP methods that have access permission. When specifying multiple methods, demarcate them with a comma (,). In the method name, specify the method that has been defined in HTTP/1.1. If you specify an asterisk (*), all methods are permitted. HTTP methods are case-sensitive so the value specified in this property is also case-sensitive. In the method name, you need to use the value provided in RFC2616. You cannot, however, specify the string "*" as a method name. The whitespace#2 before and after each method name is ignored. If you specify an invalid value, a null character string, or a whitespace#2, a message is output and the default value will be set. | GET, HEAD, POST, PUT, DELETE, OPTIONS | -- |
webserver.connector.inprocess_http.error_custom.list | Specify the definition name for error page customization used in the error page customization functionality. The maximum length of the value that can be specified is 1024 characters. Specify a string consisting of alphanumeric characters (A-Z, a-z, 0-9) or underscores (_). The string length of one definition name is from 1 to 32 characters. When specifying multiple definition names, demarcate them with a comma (,). The whitespace#2 before and after the comma is ignored. The same definition name for error page customization cannot be specified multiple times. If you specify an invalid value, a message is output and all the definitions for error page customization are disabled. | None | -- |
webserver.connector.inprocess_http.error_custom.error-page-customization-definition-name.file | Specify an absolute path for the file used as the response body during error page customization with the error page customization functionality. Use a forward slash (/) as the demarcation sign in the path. If this property is set by using the definition name for error page customization that has not been specified in webserver.connector.inprocess_http.error_custom.list, the property is disabled. In the definition name for error page customization specified in webserver.connector.inprocess_http.error_custom.list, make sure that you specify either this property, or webserver.connector.inprocess_http.error_custom.error-page-customization-definition-name.redirect_url. If you specify both the properties or if you do not specify any of the properties, or if you do not specify as an absolute path, or if you specify a file that does not exist, or a file for which there is no read permission, a message is output and this definition for error page customization is disabled. If you specify a null character string, or a whitespace#2, the property is disabled. | None | -- |
webserver.connector.inprocess_http.error_custom.error-page-customization-definition-name.file.content_type | Specify the value of Content-Type header of the response during error page customization using the error page customization functionality. If this property is set by using the definition name for error page customization that is not specified in webserver.connector.inprocess_http.error_custom.list, the property is disabled. If webserver.connector.inprocess_http.error_custom.error-page-customization-definition-name.file is not set, the property is disabled. | text/html | -- |
webserver.connector.inprocess_http.error_custom.error-page-customization-definition-name.redirect_url | Specify the redirect URL as an absolute path using the error page customization functionality. If this property is set by using the definition name for error page customization that is not specified in webserver.connector.inprocess_http.error_custom.list, the property is disabled. In the definition name for error page customization specified in webserver.connector.inprocess_http.error_custom.list, make sure that you specify either this property or webserver.connector.inprocess_http.error_custom.error-page-customization-definition-name.file. Whether the value is correct is not verified, so you need to check through actual operations. | None | -- |
webserver.connector.inprocess_http.error_custom.error-page-customization-definition-name.request_url | Specify an absolute path beginning with a forward slash (/) for the request URL that applies the error page customization with the error page customization functionality. You can specify the wild card (*) only once, immediately after the forward slash. An asterisk (*) is always interpreted as the wild card, so it cannot be used as a normal character. The value specified in this property and the value specified in webserver.connector.inprocess_http.error_custom.error-page-customization-definition-name.status, must not match with any other definition for error page customization. If this property is set by using the definition name for error page customization that is not specified in webserver.connector.inprocess_http.error_custom.list, the property is disabled. If you specify an invalid value, a message is output and this definition for error page customization is disabled. | /* | -- |
webserver.connector.inprocess_http.error_custom.error-page-customization-definition-name.status | Use the error page customization functionality and specify an integer from 400 to 599 for the response status code that performs error page customization. The value specified in this property and the value specified in webserver.connector.inprocess_http.error_custom.error-page-customization-definition-name.request_url, must not match with any other definition for error page customization. If this property is set by using the definition name for error page customization that is not specified in webserver.connector.inprocess_http.error_custom.list, the property is disabled. Make sure that you specify this property for setting the definition name for error page customization that has been specified in webserver.connector.inprocess_http.error_custom.list. If you do not specify this property, or if you specify an invalid value, a message is output and this definition for error page customization is disabled. | None | -- |
webserver.connector.inprocess_http.gateway.host | Specify the host name or the IP address of the gateway. When requests without a Host header are redirected to files, such as the welcome file, the host name of the URL specified in the Location header becomes the specified value. | None | -- |
webserver.connector.inprocess_http.gateway.port | Specify the port number of the gateway by using an integer from 1 to 65535. If a request has no Host header and the request is to be redirected to a location such as a welcome file, the port number portion of the URL that is specified in the Location header becomes the specified value. This property specification is ignored when webserver.connector.inprocess_http.gateway.host is not specified. If webserver.connector.inprocess_http.gateway.host is specified and this property is omitted, the following value is set:
| None | -- |
webserver.connector.inprocess_http.gateway.https_scheme | When a client request uses https as a scheme, and the scheme for a Web server will become http by using an SSL accelerator, specify true.
| false | -- |
webserver.connector.inprocess_http.hostname_lookups | Specify whether the Web container should perform reverse lookup of the host name and convert the IP address of the client to the host name, for a request received by the in-process HTTP server. The throughput, however, will decline In the case of reverse lookup of the host name. If the host name is not resolved, the result of the getRemoteHost() method of javax.servlet.ServletRequest interface and the client IP address output to the log file will be in the format wherein a dot (.) is used for demarcation.
| false | -- |
webserver.connector.inprocess_http.init_threads | Specify an integer from 1 to 1024 for the number of request processing threads of in-process HTTP server, generated when the server is started. The specified value must be lower than the maximum number of connections with the Web client (value specified in webserver.connector.inprocess_http.max_connections). If you specify a value greater than the maximum number of connections with the Web client, a message is output and the maximum number of connections with the Web client is set as the value. Furthermore, the maximum valid value differs based on the OS. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 10 | -- |
webserver.connector.inprocess_http.keep_start_threads | Specify whether to maintain the number of threads that are created when the server is started.
If you specify false in this property, adjustment is done so that the threads created when the server is started become lesser than the maximum number of spare threads. If the request-processing threads created when a server is started are greater than the maximum number of spare threads, the threads exceeding the maximum number of spare threads get destroyed one by one at an interval of one second after the server is started. If you specify a string other than true or false or if you specify a null character string or a whitespace#2, a message is output and the default value will be set. | false | -- |
webserver.connector.inprocess_http.limit.max_headers | Specify an integer from 0 to 32767 for the upper limit of the number of HTTP headers included in the HTTP requests. If you do not want to set the upper-limit value, specify 0. Even if the number of HTTP headers specified in this property is not met, an error occurs if the size specified in webserver.connector.inprocess_http.limit.max_request_header is exceeded. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 100 | -- |
webserver.connector.inprocess_http.limit.max_request_body | Specify an integer from -1 to 2147483647 (units: bytes) for the maximum size of the request body of an HTTP request. If you do not want to set the upper-limit value, specify -1. If the request body is sent in chunk format, the size of the chunk header also needs to be included in the specified size. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | -1 | -- |
webserver.connector.inprocess_http.limit.max_request_header | Specify an integer from 7 to 65536 (units: bytes) for the maximum size of the request header of an HTTP request. Even if the maximum size of the request header that has been set in this property is not met, an error occurs if the HTTP header specified in webserver.connector.inprocess_http.limit.max_headers is exceeded. The linefeed characters (double bytes of CR (0x0d) + LF (0x0a)) indicating the end of the HTTP header also need to be included in the specified size. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 16384 | -- |
webserver.connector.inprocess_http.limit.max_request_line | Specify either -1 or an integer from 7 to 8190 for the maximum length (units: bytes) of the request line. If you do not specify the upper-limit, specify -1. The request line includes URI and HTTP version that include the HTTP methods and the query strings. The value to be specified needs to be lower than the maximum size of the request header (value specified in webserver.connector.inprocess_http.limit.max_request_header). If you specify a value greater than the maximum size of the request header, a message is output, and the maximum size of the request header is set as the maximum length of the request line. The linefeed characters (double bytes of CR (0x0d) + LF (0x0a)) indicating the end of the HTTP header also need to be included in the size to be specified. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 8190 | -- |
webserver.connector.inprocess_http.max_connections | Specify an integer from 1 to 1024 for the maximum number of connections with the Web client. The valid maximum value is different for every operating OS. The value specified in this parameter becomes the maximum value for the request-processing threads. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 100 | -- |
webserver.connector.inprocess_http.max_execute_threads | Specify an integer from 1 to 1024 for the number of concurrently executing requests processed by the Web container. The specified value must be lower than the maximum number of connections with the Web client (value specified in webserver.connector.inprocess_http.max_connections). If you specify a value greater than the maximum number of connections with the Web client, a message is output and the maximum number of connections with the Web client is set in the value. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 10 | -- |
webserver.connector.inprocess_http.max_spare_threads | Specify an integer from 1 to 1024 for the maximum number of spare threads stored in a pool. The specified value must be lower than the maximum number of connections with the Web client (value specified in webserver.connector.inprocess_http.max_connections). If you specify a value greater than the maximum number of connections with the Web client, a message is output and the maximum number of connections with the Web client is set in the value. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 20 | -- |
webserver.connector.inprocess_http.min_spare_threads | Specify an integer from 1 to 1024 for the minimum number of spare threads stored in a pool. The specified value needs to be lower than the maximum number of spare threads stored in the pool (value specified in webserver.connector.inprocess_http.max_spare_threads). If a value greater than the maximum number of spare threads stored in the pool is set, a message is output, and the maximum number of spare threads stored in the pool is set as the minimum number of spare threads stored in the pool. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 5 | -- |
webserver.connector.inprocess_http.permitted.hosts | Specify the IP address (decimals) or the name of the host that has access permission for the in-process HTTP server. If you specify multiple hosts, demarcate the IP addresses or the host names with a comma (,). If there are no access restrictions, specify only an asterisk (*). Note that the local host can always be accessed even if it is not specified. If you specify a null character string or a whitespace#2, a message is output and the default value will be set. If the specified host cannot be resolved, a message is output, and access is permitted only from the local host. Note that the single-byte space before and after the IP address or the host name is ignored. | * | -- |
webserver.connector.inprocess_http.persistent_connection.max_connections | Specify an integer from 0 to 1024 for the maximum number of TCP connections maintained in a Persistent Connection. The value to be set must be lower than the maximum number of connections with the Web client (value specified in webserver.connector.inprocess_http.max_connections). If you set a value greater than the maximum number of connections with the Web client, a message is output and the maximum number of connections with the Web client is set as the maximum number of TCP connections stored in the Persistent Connection. If you specify a non-numeric value or a numeric value outside the range, a message is output and the value specified in webserver.connector.inprocess_http.max_connections is set as the default value. If you specify a null character string or a whitespace#2, the value specified in webserver.connector.inprocess_http.max_connections is set as the default value. | Value specified in webserver.connector.inprocess_http.max_connections | -- |
webserver.connector.inprocess_http.persistent_connection.max_requests | Specify an integer from 0 to 2147483647 for the upper limit of the number of serial connections when TCP connections are sustained by a Persistent Connection. If you do not want to set the upper-limit value, specify 0. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 100 | -- |
webserver.connector.inprocess_http.persistent_connection.timeout | Specify an integer from 0 to 3600 for the request wait period (units: seconds), when the TCP connections are sustained in a Persistent Connection. If you specify 0, the timeout does not occur. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 3 | -- |
webserver.connector.inprocess_http.port | Specify an integer from 1 to 65535 for the port number used by the in-process HTTP server. You cannot specify a port number that is already being used by another application. If you specify a port number that is in use or has been secured by another application, a message is output and the J2EE server does not start. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 80 | -- |
webserver.connector.inprocess_http.receive_timeout | Specify an integer from 0 to 3600 for the period until timeout (units: seconds), when requests are received from the Web client. If you specify 0, the timeout does not occur. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 300 | -- |
webserver.connector.inprocess_http.redirect.redirect-definition-name.file | Specify an absolute path for the file used as the response body during redirection with the redirect functionality. Use a forward slash (/) as the demarcation sign in the path. If you specify 200 in webserver.connector.inprocess_http.redirect.redirect-definition-name.status, always specify this property. If you specify 200 in webserver.connector.inprocess_http.redirect.redirect-definition-name.status, and this property is not specified, a message is output and this redirect definition is disabled. If you set this property by using a redirect definition name that is not specified in webserver.connector.inprocess_http.redirect.list and if you specify a null character string or a whitespace#2, the property is disabled. If you specify a value that is not an absolute path, a message is output and this redirect definition name is disabled. If you specify a file that does not exist or a file that does not have read permission, a message is output and this redirect definition is disabled. | None | -- |
webserver.connector.inprocess_http.redirect.redirect-definition-name.file.content_type | Specify the value of the response Content-Type header during redirection, using the redirect functionality. If this property is set by using a redirect definition name that is not set in webserver.connector.inprocess_http.redirect.list, the property is disabled. If the webserver.connector.inprocess_http.redirect.redirect-definition-name.file is not set, this property is disabled. | text/html | -- |
webserver.connector.inprocess_http.redirect.redirect-definition-name.redirect_url | Specify the redirect URL as an absolute URL, using the redirect functionality. If you specify 200 in webserver.connector.inprocess_http.redirect.redirect-definition-name.status, this property cannot be set. If you specify 200 in webserver.connector.inprocess_http.redirect.redirect-definition-name.status, and you specify this property, a message is output and the redirect definition name is disabled. If you specify a value other than 200 in webserver.connector.inprocess_http.redirect.redirect-definition-name.status, make sure that you specify this property. If you specify a value other than 200 in webserver.connector.inprocess_http.redirect.redirect-definition-name.status and this property is not specified, a message is output and the redirect definition is disabled. If this property is set by using a redirect definition name that is not set in webserver.connector.inprocess_http.redirect.list, the property is disabled. Whether the value is correct is not verified, so you need to check through actual operations. | None | -- |
webserver.connector.inprocess_http.redirect.redirect-definition-name.request_url | Specify an absolute path beginning with a forward slash (/) for the request URL performing redirection with the redirect functionality. You can specify the wild card (*) only once, immediately after the forward slash. The wild card indicates any string of 0 or more characters. An asterisk (*) is always interpreted as the wild card, so it cannot be used as a normal character. You also cannot specify a value same as that specified in another redirect definition. For the redirect definition name that has been specified in webserver.connector.inprocess_http.redirect.list, you always need to specify this property. If you do not specify this property, a message is output and the redirect definition is disabled. If this property is set by using a redirect definition name that is not set in webserver.connector.inprocess_http.redirect.list, the property is disabled. If you specify an invalid value, a message is output and the redirect definition is disabled. | None | -- |
webserver.connector.inprocess_http.redirect.redirect-definition-name.status | Specify the response status code (200, 300, 301, 302, 303, 305, 307) during redirection with the redirect functionality. If this property is set by using a redirect definition name that is not set in webserver.connector.inprocess_http.redirect.list, the property is disabled. If you specify an invalid value, a null character string, or a whitespace#2, a message is output and the default value will be set. | 302 | -- |
webserver.connector.inprocess_http.redirect.list | Specify the redirect definition name used in the redirect functionality. The maximum length of the value that can be specified in this property is 1024 characters. Specify the redirect definition name with a string consisting of alphanumeric characters (A-Z, a-z, 0-9) or underscores (_). The string length of one redirect definition name is from 1 to 32 characters. When specifying multiple redirect definition names, demarcate them with a comma (,). The whitespace#2 before and after the comma is ignored. You cannot specify the same redirect definition name multiple times. If you specify an invalid value, a message is output and all redirect definitions are disabled. | None | -- |
webserver.connector.inprocess_http.rejection_threads | Specify an integer from 0 to 1023 for the number of request-processing threads that are denied access. The value to be specified must be lesser than the maximum number of request-processing threads (value specified in webserver.connector.inprocess_http. max_connections). If a value greater than the maximum number of connections with the Web client is set, a message is output and a value that is 1 less than the maximum number of connections with the Web client is set as the number of request-processing threads that are denied access. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 1 | -- |
webserver.connector.inprocess_http.response.header.server | Specify the value of the Server header that is automatically added to the response. If you specify a null character string or a whitespace#2, a message is output and the default value will be set. | CosminexusComponentContainer | -- |
webserver.connector.inprocess_http.send_timeout | Specify an integer from 0 to 3600 for the period until timeout (units: seconds) when a response is sent to the Web client. When you specify 0, the timeout is not enabled. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. | 300 | -- |
webserver.connector.limit.max_parameter_count | Specify an integer from -1 to 2147483647 as the maximum number of request parameters. The valid range of maximum number of request parameters is a total of the request query strings and number of parameters of the form data with the Content-Type header value as application/x-www-form-urlencoded or multipart/form-data. If you do not want to set up the maximum number of request parameters, specify -1. If you specify a non-numeric value, a numeric value outside the range, a null character string or a whitespace#2, a message is output and the default value will be set. If the number of request parameters exceeds the specified value, the following operations are performed depending on the APIs and the KDJE39341-W or the KDJE39342-E message is displayed:
| 10000 | 09-00 |
webserver.connector.limit.max_post_form_data | Specify an integer from -1 to 2147483647 (unit: bytes) for the maximum size of form data of a POST request. If the maximum size is not set, specify -1. If the following numeric values or strings are specified, a message is output and the default value is applied:
When the request body is in the check format, if the received POST request size exceeds the maximum specified size due to an extended Servlet API invocation, a java.lang.IllegalStateException is thrown and the message KDJE39336-E is output.
| 2097152 | 08-50 |
webserver.connector.redirect_https.port | Specify the HTTPS port number used by the Web server Specify the value using an integer from 1 to 65535. If the port number is not specified, requests are not redirected to the HTTPS port. You cannot specify a port number that is already being used or secured for another application. Furthermore, do not specify the same value in port numbers of the ports to be used to communicate with the Web server in multiple J2EE servers. The cjstartsv command cannot start up multiple J2EE servers in which identical port numbers are specified. | None | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.container.ac.logEnabled | Specify whether to output the trace log for Web container maintenance.
| false | -- |
webserver.container.jaxws.webservice.no_webxml.enabled | When SOAP request messages arrive from the client of the Web Service, specify whether to receive the SOAP request messages and distribute them to the Web Service implementation class if the Web Service implementation class or Provider implementation class developed using Cosminexus JAX-WS is included even when web.xml is not included in the WAR file either completely or partially.
| none | 08-00 |
webserver.container.jaxws.webservice.wsee.no_webxml.enabled | When SOAP request messages arrive from the client of the Web Service, specify whether to receive the SOAP request messages and distribute them to the Web Service implementation class if the Web Service implementation class or Provider implementation class developed using Cosminexus JAX-WS is included even when web.xml is not included in the WAR file either completely or partially.
| lax | 08-70 |
webserver.container.jaxws.webservice.wsee.warname | Specify the path name of the WAR file for setup, for the Web service implementation class included in the EJB-JAR files#1. The WAR file for setup might be created by the user and auto-generated during deployment. When the WAR file for setup is auto-generated during deployment, this property need not be set up. | CosminexusWSEE.war | 08-70 |
webserver.container.server_id.enabled | Specify whether to add the Cookie of the server ID to the HTTP response.
| false | -- |
webserver.container.server_id.name | Specify the name of the Cookie when the Cookie of server ID is to be added to the HTTP response. Specify the value as a string from 1 to 64 characters. You can use single-byte alphanumeric characters (A-Z, a-z, 0-9) or underscores (_). The following name is used by the Web container and is case sensitive:
| ServerID | -- |
webserver.container.server_id.value | Specify the value of the Cookie when the Cookie of server ID is to be added to the HTTP response. Specify the value as a string from 1 to 64 characters. You can use single-byte alphanumeric characters (A-Z, a-z, 0-9) or underscores (_). If you specify true in webserver.container.server_id.enabled, and this property is omitted, or if you specify an invalid value, a null character string, or a whitespace#2, a message is output and the default value will be set. | String generated using the hash function from the host name and J2EE server name/Web container server name (compatibility functionality). The generated value is a 64-character hexadecimal number. | -- |
webserver.container.servlet.default_mapping.enabled | Specify whether to enable the default servlet mapping.
| false | 08-00 |
webserver.container.thread_control.enabled | Specify whether to use the functionality for controlling the concurrently executing number of threads in each Web application. This functionality is enabled only in the J2EE server mode.
| true | -- |
webserver.container.thread_control.queue_size | Specify an integer from 0 to 2147483647 for the default size of the pending queues, when the functionality for controlling the number of concurrently executing threads in each Web application is to be used. This functionality is enabled only in the J2EE server mode. However, if you specify false in webserver.container.thread_control.enabled, the property is disabled. | 8192 | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.context.check_interval | Specify an integer from 0 to 2147483647 (units: seconds) for the interval to detect the update of a Web application. If you specify 0, the update will not be automatically detected. If the reload functionality of a J2EE application is disabled, you cannot set this property. If you set this property, it is ignored. If you specify a non-numeric value, a numeric value outside the range, or a null character string, a message is output and the default value will be set. | Value set in ejbserver.deploy.context.check_interval (default value: 0) | -- |
webserver.context.reload_delay_timeout | Specify a negative integer or a value from 0 to 2147483647 (units: seconds) for the maximum delay time of the delay execution functionality for reloading the Web application. If you specify 0, the delay execution functionality for reloading is not used. If the reload functionality of a J2EE application is disabled, you cannot set this property. If you set this property, it is ignored. If you specify a negative integer, the delay execution functionality for reloading is used without specifying the maximum delay time. | 0 | -- |
webserver.context.update.interval | Specify an integer from 0 to 2147483647 (units: seconds) for the time interval required for copying the file that you will update. Specify extra time for the interval. The monitoring of a request that is being processed starts after the lapse of the specified interval from the detection of resource update. If the JSP reload functionality is disabled, you cannot set this property. If you set this property, it is ignored. If you specify a non-numeric value, a numeric value outside the range, or a null character string, a message is output and the default value will be set. | ejbserver.deploy.context.update.interval (default value: 0) | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.dbsfo.attribute_data_size.max | Specify the maximum size of the HTTP session attribute information that can be included in the global session information in bytes. | 1024 | 08-00 |
webserver.dbsfo.check_size.mode | Specify whether to enable the size estimation functionality (database session failover functionality) for the HTTP session attribute information.
| off | 08-00 |
webserver.dbsfo.connector.name | Specify the optional name of the DB Connector to be used by the database session failover functionality. | COSMINEXUS_SFO_DBCONNECTOR | 08-00 |
webserver.dbsfo.enabled | Specify whether to enable the database session failover functionality.
| false | 08-00 |
webserver.dbsfo.exception_type_backcompat | Specify the compatibility option of the exception that occurs when the HttpServletRequest#getSession method is executed in the error page of the request for which the database session failover functionality is to be controlled.
| false | 08-70 |
webserver.dbsfo.exclude.extensions | Specify the extension for controlling the database session failover functionality. If the extension matches with the extension specified in the URL path, the database session failover functionality will be disabled in the applicable request. The comparison between the specified extension and the URL is not case sensitive. Also, if the extension for controlling the database session failover functionality is not specified, specify a null string or a comma (,). | txt,htm,html,jpg,gif,js | 08-00 |
webserver.dbsfo.exclude.uris | Specify a URI for inhibiting the database session failover functionality. If the path of the request URI matches the specified URI, the database session failover functionality is disabled for that request. The comparison of the specified URI with the request URI is case sensitive. If the URI for inhibiting the database session failover functionality is not set, a null character string will be set. | None | 08-50 |
webserver.dbsfo.integrity_mode.enabled | Specify whether to enable the integrity guarantee mode of the database session failover functionality.
| false | 08-70 |
webserver.dbsfo.negotiation.high_level | Specify whether to continue or cancel the Web application start processing when the negotiation implemented during the startup of a Web application fails while the database session failover functionality is being used.
| false | 08-70 |
webserver.dbsfo.session_read_only.uris | Specify the URI to be used as the reference request of the database session failover functionality. The values that can be specified are as follows:
If the specified URI matches with the request URI, this request becomes a reference request. When the specified URI is compared with the request URI, uppercase and lowercase characters are distinguished. | None | 08-70 |
webserver.dbsfo.thread_control_queue.enabled | Specify the operations to be performed when the pending queue space is insufficient, and if the database session failover functionality is used while the functionality for controlling the number of concurrently executing threads for Web applications is enabled.
| false | 08-70 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the Application Server version in which the keys are installed or changed.
For information related to the specifiable keys, see 7. EADs Session Failover Functionality in the uCosminexus Application Server Expansion Guide.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.eadssfo.application.cache.name | Specify the cache name of the application information cache to be used with the EADs session failover functionality. | EADsSFO_APP_INFO | 09-50 |
webserver.eadssfo.check_size.mode | Specify whether to enable the functionality for estimating the size of the attribute information for the HTTP sessions (EADs session failover functionality).
| off | 09-50 |
webserver.eadssfo.client.retry.count | Specify an integer from 1 to 2147483647 as the retry count when the access to the EADs server with the EADs session failover functionality fails #1. | 2 | 09-50 |
webserver.eadssfo.client.retry.interval | Specify an integer from 1 to 2147483647 as the retry interval (unit: millisecond) when the access to the EADs server with the EADs session failover functionality fails#1. | 2000 | 09-50 |
webserver.eadssfo.eads.client.connection-destination-EADs-server-name.address | This property defines the EADs client to be used with the EADs session failover functionality#3. Specify the IP address or host name of the EADs server to be connected with the default EADs client settings used when a Web application starts. Specify the name defined in eads.client.node.list in the variable part of the parameter. | None#2 | 09-50 |
webserver.eadssfo.eads.client.connection-destination-EADs-server-name.port | This property defines the EADs client to be used with the EADs session failover functionality#3. Specify the port number of the EADs server to be connected with the default EADs client settings used when a Web application starts. Specify the name defined in eads.client.node.list in the variable part of the parameter. | 24600 | 09-50 |
webserver.eadssfo.eads.client.node.list | This property defines the EADs client to be used with the EADs session failover functionality #3. Specify the name for identifying the connection destination EADs server to be connected with the default EADs client settings used when a Web application starts. To specify multiple names, delimit the names with commas (,). If multiple names are specified, a connection is established with one of the EADs servers. If a connection fails, an attempt is made to connect to another EADs server. | None#2 | 09-50 |
webserver.eadssfo.eads.connection.buffersize | This property defines the EADs client to be used with the EADs session failover functionality #3. Specify the buffer size (unit: byte) for sending and receiving the connection reading or writing data. Note that you must set up an appropriate value according to the size of the data to be stored in the EADs server for this property. For details, see the Elastic Application Data store User Guide. | #4 | 09-50 |
webserver.eadssfo.eads.connection.retry | This property defines the EADs client to be used with the EADs session failover functionality #3. Specify the retry count for communication failure during the checking of a connection. | 1 | 09-50 |
webserver.eadssfo.eads.connection.timeout | This property defines the EADs client to be used with the EADs session failover functionality #3. Set up the monitoring time (unit: millisecond) for checking a connection and for sending and receiving the data. | #4 | 09-50 |
webserver.eadssfo.eads.connectionPool.poolsize | This property defines the EADs client to be used with the EADs session failover functionality #3. Specify the maximum number of connections to be pooled for the same connection destination. | #4 | 09-50 |
webserver.eadssfo.eads.logger.commDump.enable | This property defines the EADs client to be used with the EADs session failover functionality #3. Specify whether to enable the output of the message dump output by the EADs client. | #4 | 09-50 |
webserver.eadssfo.eads.logger.commTrace.enable | This property defines the EADs client to be used with the EADs session failover functionality #3. Specify whether to enable the output of the communication trace output by the EADs client. | true | 09-50 |
webserver.eadssfo.eads.logger.commTrace.filenum | This property defines the EADs client to be used with the EADs session failover functionality #3. Specify the number of communication trace files output by the EADs client. | #4 | 09-50 |
webserver.eadssfo.eads.logger.commTrace.filesize | This property defines the EADs client to be used with the EADs session failover functionality #3. Specify the file size (unit: byte) per communication trace file output by the EADs client. | #4 | 09-50 |
webserver.eadssfo.eads.logger.dir | This property defines the EADs client to be used with the EADs session failover functionality #3. Specify the output destination directory of the message log output by the EADs client. | ${ejbserver.log.directory} | 09-50 |
webserver.eadssfo.eads.logger.message.console.enable | This property defines the EADs client to be used with the EADs session failover functionality #3. Specify whether to enable the output of the message log, output by the EADs client, to the standard output. | #4 | 09-50 |
webserver.eadssfo.eads.logger.message.filenum | This property defines the EADs client to be used with the EADs session failover functionality #3. Specify the number of message log files output by the EADs client. | #4 | 09-50 |
webserver.eadssfo.eads.logger.message.filesize | This property defines the EADs client to be used with the EADs session failover functionality #3. Specify the file size (unit: byte) per message log file output by the EADs client. | #4 | 09-50 |
webserver.eadssfo.enabled | Specify whether to enable the EADs session failover functionality.
| false | 09-50 |
webserver.eadssfo.exclude.url_patterns | Specify the URL pattern (exact match specification, prefix match specification, and extension match specification) for controlling the EADs session failover functionality. If the specified URL pattern and request URI match, the EADs session failover functionality is disabled for that request. For the exact match specification and prefix match specification comparisons, the values are case sensitive. For the extension match specification, the values are not case sensitive. If you do not want to control the EADs session failover functionality, specify a null string. To specify multiple URL patterns, delimit the values with semi-colons (;). | *.txt;*.htm;*.html;*.jpg;*.gif;*.js | 09-50 |
webserver.eadssfo.session.cache.name | Specify the cache name of the session information cache to be used with the EADs session failover functionality. | EADsSFO_SESSIONS | 09-50 |
webserver.eadssfo.session_read_only.url_patterns | Specify the URL patterns (exact match specification, prefix match specification, and extension match specification) to be considered as read-only requests in the EADs session failover functionality. If the specified URL pattern and request URI match, that request becomes a read-only request. For the exact match specification and prefix match specification comparisons, the values are case sensitive. For the extension match specification, the values are not case sensitive. If you do not want to set up a read-only request, specify a null string. To specify multiple URL patterns, delimit the values with semi-colons (;). | None | 09-50 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.errorpage.stack_trace.enabled | Specify whether to output stack trace in the default error page, when an exception occurs.
| false | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.http.request.encoding | Specify the character encoding to be used in the request body and query decoding. The characters that can be specified as the default character encoding are the character encoding supported in the JavaVM. For details about the character encoding supported in JavaVM, see the explanation related to the supported encoding in JDK documentation. The strings that can be specified are the character encoding described in the canonical name for the java.nio API and canonical name for the java.lang API and their optional names. | None | -- |
webserver.http.request.uri_decode.enabled | Specify whether to decode the servlet path and additional path information.
| false | 08-00 |
webserver.http.response.encoding | Specify the character encoding to be used in the encoding of the response body. The characters that can be specified as the default character encoding are the character encoding supported in the JavaVM. For details about the character encoding supported in JavaVM, see the explanation related to the supported encoding in JDK documentation. The strings that can be specified are the character encoding described in the canonical name for the java.nio API and canonical name for the java.lang API and their optional names. | None | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.jsp.additional.import.list | Specify the class name (class name of a fully qualified name or package-name.*) to be imported implicitly during JSP compilation. To specify multiple class names, demarcate the class names with a comma (,). If you specify an invalid value, such as a non-existent class name or a class name not existing in a class path, a message is displayed and a compilation error occurs. | None | 08-70 |
webserver.jsp.check_interval | Specify an integer from 0 to 2147483647 (units: seconds) for the interval to detect an update in JSP. If you specify 0, the update will not be automatically detected. If the JSP reload functionality is disabled, you cannot set this property. If you set this property, it is ignored. If you specify a non-numeric value, a numeric value outside the range, or a null character string, a message is output and the default value will be set. | Value set in ejbserver.deploy.context.check_interval (default value: 0) | -- |
webserver.jsp.compile.backcompat | Specify the version of java source code during compilation of java source of the servlets generated from JSP. Specify this property when compilation cannot be done in the JavaVM version provided by Cosminexus, since the Java code is coded in JSP by the scripting of a JSP generated in an older version. If there is no dependence on the Java VM version, either omit this property or specify false. The values that can be specified are as follows:
| false | -- |
webserver.jsp.el2_2.enabled | Switches the processing nodes of EL 2.1 and EL 2.2.
| true | 09-00 |
webserver.jsp.precompile.jsp_work_dir | Specify the directory name for storing the compilation results of the JSP file generated by the JSP pre-compile functionality. You specify the directory name with a string consisting of single-byte alphanumeric characters (A-Z, a-z, 0-9) or underscores (_). If you specify an invalid value, a message is output and the default value will be set. If the following reserved words are specified, a message is output and the default value will be used.
| cosminexus_jsp_work | -- |
webserver.jsp.keepgenerated | Specify whether to store the java file generated by compiling the JSP files or the tag files. You specify the following values:
| false | -- |
webserver.jsp.pageEncoding | Specify the character encoding for JSP. The characters that can be specified as the default character encoding are the character encoding supported in the JavaVM. For details about the character encoding supported in JavaVM, see the explanation related to the supported encoding in JDK documentation. The strings that can be specified are the character encoding described in the canonical name for the java.nio API and canonical name for the java.lang API and their optional names. | None | -- |
webserver.jsp.translation.backcompat.customAction.declareVariable | Specify whether to output the variable declaration of the script variable corresponding to the second custom tag in the Java code created from JSP files, when the script variable name and the script variable scope overlap in multiple custom tags.
| false | -- |
webserver.jsp.translation.backcompat.tag.noCheckRtexprvalue | Specify whether to verify the specification of Expression in an attribute value of a tag in which Expression cannot be specified.
| false | -- |
webserver.jsp.translation.backcompat.tag.rtexprvalueTerminate | The attribute value of the tag begins with '<%= or '<%=. Specify whether to treat the value enclosed with (or ') of the attribute value that does not end with %> (specify %>' when it starts with '<%).
| false | -- |
webserver.jsp.translation.backcompat.taglib.noCheckPrefix | Specify whether to check the availability of the description of custom tags where the prefix specified in the taglib directive is used before the tablib directive.
| false | -- |
webserver.jsp.translation.backcompat.useBean.noCheckClass | Specify whether to execute the check processing of a class attribute value of the <jsp:useBean> tag in JSP translation.
| false | -- |
webserver.jsp.update.interval | Specify an integer from 0 to 2147483647 (units: seconds) for the interval required to copy the files that are to be monitored for JSP reload. Specify extra time for the interval. JSP is reloaded after the lapse of the interval specified after detecting JSP file update. If the JSP reload functionality is disabled, you cannot set this property. If you set this property, it is ignored. If you specify a non-numeric value, a numeric value outside the range, or a null character string, a message is output and the default value will be set. | Value set in ejbserver.deploy.context.update.interval (default value: 0) | -- |
webserver.jsp.translation.customAction.ignoreCaseAttributeName | Specify whether to differentiate upper and lower cases when checking whether the attributes specified in the custom tags are defined in the TLD files or tag files.
| false | 08-00 |
webserver.jsp.translation.useBean.noCheckDuplicateId | Check whether the id attribute value of the <jsp:useBean> tag is duplicated. If true, a translation error will not occur even if the id attribute value is duplicated. If false, a translation error will occur if the id attribute value is duplicated. | false | 08-00 |
webserver.jsp.tld.mapping.java_ee_tag_library.enabled | Specify whether TLD of the tag libraries (JSTL, JSF) included in the Java EE specifications and URL will be mapped automatically in Web applications of Servlet 2.5 and later specifications.
| true | 08-00 |
webserver.jsp.jsp_page.bom.enabled | Specify whether to enable the specifications of BOM-based character encoding in the JSP pages of the Web applications of Servlet 2.5 and later specifications.
| true | 08-00 |
webserver.jsp.debugging.enabled | Specify whether to enable the JSP debugging functionality. Note that this property is enabled only in the J2EE server mode.
| false | 08-00 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.logger.access_log.inprocess_http.enabled | Specify enable or disable for the access log functionality of the in-process HTTP server.
| true | -- |
webserver.logger.access_log.format_list | Specify the format name to be used in the access log functionality of the in-process HTTP server. The maximum length of the string that can be specified is 1024 characters. Specify the format name with a string consisting of alphanumeric characters (A-Z, a-z, 0-9) or underscores (_). The maximum string length of one format name is 32 characters. This key treats format_list and mode_list as invalid format names; therefore, you cannot specify them as format names. When specifying multiple format names, demarcate them with comma (,). The format name set first is treated as the default format name. You cannot specify the same format name multiple times. The formats common and combined are reserved formats of the access log functionality; therefore, you cannot specify them.
| common,combined | -- |
webserver.logger.access_log.format-name | Specify the format#2 of the access log format that is defined in format-name, with format arguments. The maximum length of the value that can be specified is 1024 characters. The usable characters include the Ascii code from 32 (decimal) to 127 (decimal). For setting all format names defined in webserver.logger.access_log.format_list, you need to set webserver.logger.access_log.format-name. If this property is set by a format name that has not been defined in webserver.logger.access_log.format_list, this property is disabled. You need not, however, specify the format names common and combined. If you specify the format names common and combined, this property is disabled. If you do not specify a string, or the format exceeds 1024 characters, or if you specify characters outside the range, a message is output and the default value will be set. | %h %l %u %t "%r" %>s %b | -- |
webserver.logger.access_log.inprocess_http.filename | Specify an absolute path for the file name#3 that outputs the log used in the access log functionality of the in-process HTTP server. The maximum length of the value that can be specified is 210 characters. If you specify a string exceeding 210 characters, or if you specify a numeric value or characters outside the range, or if you do not specify a string, a message is output and the default value will be set. If the specified directory does not exist, a directory is created. If a directory is not created, invocation of J2EE server fails. |
| -- |
webserver.logger.access_log.inprocess_http.filenum | Specify an integer from 1 to 256 for the number of Web container log files of the in-process HTTP server. If you specify a non-numeric value, or a numeric value outside the range, or if you do not specify a string, a message is output and the default value will be set. | 16 | -- |
webserver.logger.access_log.inprocess_http.filesize | Specify an integer from 4096 to 2147483647 (units: bytes) for the size of the access log file of the in-process HTTP server. If you specify a non-numeric value, or a numeric value outside the range, or if you do not specify a string, a message is output and the default value will be set. The decision of wraparound of the access log file is taken before writing the log, therefore, the specified file size may exceed in some cases. | 4194304 | -- |
webserver.logger.access_log.inprocess_http.usage_format | Choose the format to be used in the access log functionality of the in-process HTTP server. If you do not specify a string or if you specify a format name that has not been defined, a message is output and the default value will be set. | common | -- |
webserver.logger.communication_trace.inprocess_http.filenum | Specify an integer from 1 to 256 for the number of communication trace functionality log files of the in-process HTTP server. If you specify a non-numeric value, or a numeric value outside the range, or if you do not specify a string, a message is output and the default value will be set. | 16 | -- |
webserver.logger.thread_trace.inprocess_http.filenum | Specify an integer from 1 to 256 for the number of thread trace functionality log files of the in-process HTTP server. If you specify a non-numeric value, or a numeric value outside the range, or if you do not specify a string, a message is output and the default value will be set. | 16 | -- |
Format argument | Output contents | Examples of output |
---|---|---|
%% | % sign | % |
%a | IP address of Web client. | 10.20.30.40 |
%A | IP address of J2EE server. | 10.20.30.100 |
%b | Number of sent bytes excluding the HTTP header. Use "--" In the case of 0 bytes. | 2048 |
%B | Number of sent bytes excluding the HTTP header. Use "--" In the case of 0 bytes. | 1024 |
%h | Host name or IP address of the Web client. The IP address is used, if the host name is not acquired. | 10.20.30.40 |
%H | Request protocol. | HTTP/1.1 |
%l | Remote log name (User name of Web client that is acquired by the Identification protocol stipulated in RFC 1413). | - |
%m | Request method. | GET |
%p | Port number that receives requests from the Web client. | 80 |
%q | Query string. Starts with "?". If there is no query string, it is assumed as a blank character. | ?id=100&page=15 |
%r | Request line. | GET /index.html HTTP/1.1 |
%>s | Final status code (an internally redirected value is not output). | 200 |
%S | Session ID of the user. Use "--" if there is no session ID. A memory session ID displayed as %S is the value of the cookie name JSESSIONID and is different from the global session ID of the session failover functionality. If the global session ID is to be output, specify %GSESSIONIDc. If GIDCookieName is changed, specify the value of the changed GIDCookieName. | 00455AFE4DA4E7B7789F247B8FE5D605 |
%t | Time when the processing of the requests from the Web client started (dd/MMM/YYYY:HH:mm:ss Z) | [18/Jan/2005:13:06:10 +0900] |
%T | The time (units: seconds) required for processing a request from the Web client. | 2 |
%d | Time when the processing of the requests from the Web client started. Display in the following format: (dd/MMM/YYYY: HH: mm: ss.nnn Z) (nnn indicates milliseconds) | [18/Jan/2005:13:06:10.152 +0900] |
%D | The time (units: milliseconds) required for processing a request from the Web client. | 2000 |
%u | Basic authentication user name or form authentication user name. Use "--" if there is no authentication user name. | user |
%U | Request file path. | /index.html |
%v | Local host name of J2EE server. | server |
%{foo}i | Contents of the request header foo. Use "--" if foo header does not exist. If the same header name is sent multiple times in one HTTP request or HTTP response, the contents of the header that is read first will be output. | In the case of %{Host}i www.example.com:8888 |
%{foo}c | In the Cookie information sent by the Web client, the name of the Cookie is the foo content. If the name of the Cookie does not contain foo, it becomes "--". | n the case of %{JSESSIONID}c 00455AFE4DA4E7B7789F247B8FE5D605 |
%{foo}o | Contents of the response header foo. Use "--" if foo header does not exist. If the same header name is sent multiple times in one HTTP request or HTTP response, the contents of the header that is read first will be output. | In the case of %{Server}o CosminexusComponentContainer |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.servlet_api.exception.getCause.backcompat | Specify settings in such a way so that the root cause exception specified in the constructors ServletException(String, Throwable) and ServletException(Throwable) of javax.servlet.ServletException cannot be acquired using getCause(). Specify settings in such a way so that the root cause exception specified in the constructors JspException(String, Throwable) and JspException(Throwable) of javax.servlet.jsp.JspException cannot be acquired using getCause().
| false | 08-00 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.ServletContainerInitializer_jar.include.path | Specify the path of the JAR file that includes the ServletContainerInitializer implementation class as an absolute path. When specifying multiple methods, demarcate them with a comma (,). Use a forward slash (/) as the directory delimiter. | None | 09-00 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.session.cookie_config.http_only | Specify whether to add the HttpOnly attribute to the HTTP Cookie indicating the session ID of an HTTP session created with a Web application.
| false | 09-50 |
webserver.session.cookie_config.name | Specify the name of the HTTP Cookie indicating the session ID of an HTTP session created with a Web application, or the path parameter name of the URL.
|
| 09-50 |
webserver.session.delete_cookie.backcompat | Specify whether to delete the HTTP Cookie indicating the session ID maintained by the Web client when the HTTP session is disabled.
| false | 08-00 |
webserver.session.max.log_interval | Specify an integer from 0 to 2147483647 (units: seconds) for the interval to output the following messages:
If you specify a non-numeric value or a numeric value outside the range, a warning message is output and the default value will be set. | 60 | -- |
webserver.session.max.throwHttpSessionLimitExceededException | Specify whether to throw the com.hitachi.software.web.session.HttpSessionLimitExceededException exception when the number of HTTP session objects exceeds the upper limit.
| false | 08-00 |
webserver.session.server_id.enabled | Specify whether to append server ID to the session ID.
| true | -- |
webserver.session.server_id.value | Specify a string from 1 to 64 characters for the server ID that is to be appended to the session ID. You can use single-byte alphanumeric characters (A-Z, a-z, 0-9) or underscores (_). If you specify true in webserver.session.server_id.enabled, and this property is omitted, or else if you specify an invalid value, a null character string or a whitespace# in this property, a message is output and the default value will be set. | String generated using the hash function from the host name and J2EE server name/Web container server name (compatibility functionality). The generated value is a 64-character hexadecimal number. | -- |
webserver.session.tracking_mode | Specify the method of managing the HTTP sessions created with a Web application. You can either specify COOKIE or URL, or both. When you specify both the session management methods, use a comma (,) to delimit between COOKIE and URL. Note that the single-byte spaces before and after COOKIE or URL are ignored.
| COOKIE, URL | 09-50 |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.static_content.cache.enabled | Specify enable/disable/forcibly disable the functionality for caching static contents.
In a Web application, wherein the functionality for caching the static contents is not specified as either enable or disable in the DD file (web.xml) or the HITACHI Application Property file, the value specified in this property becomes valid. In a Web application, wherein the functionality for caching the static contents is set as either enable or disable, the value specified in this property becomes invalid. If, however, you specify forceoff, the value specified in this property becomes valid, irrespective of the settings of the DD file (web.xml) or the HITACHI Application Property file. If a string other than true, false, forceoff, or a null character string or whitespace# are specified, a message is output and the default value will be set. | false | -- |
webserver.static_content.cache.size | Specify an integer from 0 to 2147483647 for the upper limit of the size (units: bytes) that can be cached in the memory when the functionality for caching static contents is enabled. If the value specifying the total cache size in each Web application is exceeded, deletion will begin from the cache with the longest no access time and the deletion of cache repeats until the total size of the cache becomes lesser than the set value. If you specify 0, no upper limit is set for the cacheable size. In a Web application, wherein the cacheable memory size is not set in DD (web.xml) or the HITACHI Application Property file, the value specified in this property becomes valid. In a Web application, wherein the cacheable memory size is set, the value specified in this property becomes invalid. If you specify an invalid value, a value lesser than that specified in webserver.static_content.cache.filesize.threshold, a null character string, or a whitespace#, a message is output and the default value will be set. | 10485760 | -- |
webserver.static_content.cache.filesize.threshold | Specify an integer from 0 to 2147483647 for the file size (units: bytes) that can be cached, when the functionality for caching static contents is enabled. A file of a size exceeding the specified value does not get cached. If you specify 0, no upper limit is set for the file size that can be cached. In a Web application, wherein the file size that can be cached is not set in DD (web.xml) or the HITACHI Application Property file, the value specified in this property becomes valid. In a Web application, wherein the file size that can be cached is set, the value specified in this property becomes invalid. If you specify an invalid value, a value greater than that specified in webserver.static_content.cache.size, a null character, or a whitespace#, a message is output and the default value will be set. | 524288 | -- |
webserver.static_content.encoding.extension | Specify an extension to be applied to the character encoding used for static contents. This key is enabled when the webserver.http.response.encoding key is specified. If the value is not specified for the key, this key is disabled. | None | -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.work.clean | Specify whether to delete the directory created below the temporary directory for JSP, when starting and shutting down the server.
| false | -- |
webserver.work.directory | Specify an absolute path for the temporary directory for JSP. Specify the directory name.# Use a forward slash (/) as the delimiter in the directory path. For example, in Windows, if C\temp\work is to be set as the work directory, specify as follows: (Example of specification) webserver.work.directory=c:/temp/work |
| -- |
The following table lists the specifiable keys. Note that Default value is the value that is assumed when a key is not specified.
VR is the version of Application Server on which the keys are introduced or changed.
Key name | Contents | Default value | VR |
---|---|---|---|
webserver.xml.validate | Specify whether to check if the tag library descriptor (TLD file) in the Web application of Servlet 2.3 has been written as per the schema coded in DTD. The specification of this property is disabled in web.xml invoked in the J2EE server mode and in the TLD files of the Web applications of Servlet 2.4 and later versions. All the TLD files included in the Web applications of Servlet 2.4 and later versions are checked, irrespective of the version of TLD. You specify the following values:
| true | -- |
ejbserver.server.j2ee.feature=1.4
ejbserver.deploy.stub.generation.scope=ejb
ejbserver.compiler.jvm.maxHeapSize=256m
ejbserver.compiler.jvm.minHeapSize=32m
ejbserver.naming.host=localhost
ejbserver.naming.port=900
ejbserver.naming.protocol=corbaname
ejbserver.naming.startupMode=inprocess
ejbserver.naming.startupWaitTime=1
ejbserver.naming.startupRetryCount=9
ejbserver.logger.enabled.*=Error,Warning,Information,Debug
ejbserver.logger.channels.define.MessageLogFile.filenum=2
ejbserver.logger.channels.define.MessageLogFile.filesize=1048576
ejbserver.application.InitTermProcessClasses=InitTermClass1,InitTermClass2
webserver.connector.http.permitted.hosts=host1,host2
webserver.work.directory=c:/work