Symfoware Server V12.1.0 Messages

A.2.5 Messages that Contain "IJServer" in the Message ID

A.2.5.1 IJServer12000 to IJServer12099

A.2.5.1.1 IJServer12003

( warn) IJServer12003: Cannot clean old log files. You must remove the old log file manually. pid=<pid> tid=<tid>

Variable Information

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

Old log files cannot be deleted.

User Action

Because old log files may exhaust the free disk space, manually delete old log files beyond the specified number of generations. Refer to "PL/extJava Log Information" in the Operation Guide for information on the log file output destination.

A.2.5.1.2 IJServer12004

(error) IJServer12004: Cannot connect to IJServer. The following are the most common causes of this error: IJServer stops or overloaded, Wrong IP address or port. serverName=<serverName> serverPort=<serverPort> host=<host> port=<port> uri=<uri> errno=<errno> pid=<pid> tid=<tid>

Variable Information

<serverName> = Server name of Web server

<serverPort> = Port number of Web server

<host> = Host name of container

<port> = Port number of container

<uri> = Web browser request URL

<errno> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

The Web server connector cannot be connected to the container.

Cause

Possible causes are as follows:

1. The container process was forced to stop due to an application timeout.

2. A TCP/IP resource shortage occurred.
   When this message is output and the "netstat -a" command lists a large number of "TIME_WAIT" connections between ephemeral ports and server instance ports, it means that the ephemeral ports may be depleted.

3. The container is overloaded. A memory shortage may have occurred in the Java VM.

4. The number of requests that was received exceeded the maximum number of connections to the server instance.

5. The container is in diminished operation.

6. In other cases, an error may have occurred in the container.

System Action

• If the container process concurrency is 1, the Web server connector interrupts connection to the container, and posts a message containing status code 500 (Internal Server Error) to the web browser.

• If the container process concurrency is 2 or more, the Web server connector ends connection to the container and attempts to connect to another container.

  If connection to all containers fails, the Web server connector posts a message containing status code 500 (Internal Server Error) to the Web browser.

User Action

1. Tune the TCP/IP parameter. Check the network status with the "netstat -a" command, and check if there is a large number of connections in a "TIME_WAIT" state.
   If it was confirmed that the ephemeral port was depleted, release unnecessary ports. Alternatively, increase the number of ports that can be used as ephemeral ports.

2. If this error message is output frequently, increase the server instance (JavaVM) or check the system configuration (hardware and software) and reconfigure an overload-resistant system. Consider upgrading the CPU as needed.

   Refer to the event log (system log), or the logs mentioned in "Container" in the Operation Guide. If there is insufficient JavaVM memory ('OutOfMemoryError' occurs), refer to "Java Function Errors" in the Operation Guide, and then take action.

3. Check the logs mentioned in "Container" of the Operation Guide, and if an error was output, take the action advised in the message.

A.2.5.1.3 IJServer12007

(error) IJServer12007: Cannot create socket. The per-process descriptor table is full or out of streams resources. errno=<errno> pid=<pid> tid=<tid>

Variable Information

<errno> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

A socket cannot be created because of a resource shortage.

System Action

The Web server connector interrupted its attempt to connect to the container, and sent the error message status code 500 (Internal Server Error) to the web browser.

User Action

Terminate other applications or increase the number of files that can be opened in the system.

A.2.5.1.4 IJServer12011

( info) IJServer12011: Cleaning up the old log files. file="<filename>" pid=<pid> tid=<tid>

Variable Information

<filename> = Old log file name

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

Cleaning up the old log files.

A.2.5.1.5 IJServer12016

( info) IJServer12016: Loading of the Web Server Connector properties. conf="<filename>" pid=<pid> tid=<tid>

Variable Information

<filename> = Property file of Web server connector

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

The property file of the Web server connector is loaded.

A.2.5.1.6 IJServer12017

(error) IJServer12017: No space left on device. directory= "<dir>" pid=<pid> tid=<tid>

Variable Information

<dir> = Directory name

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

The disk is short of free space.

User Action

Check if there is sufficient space to collect the logs mentioned in "Internal Log" of the Operation Guide. The required size can be calculated from the log size and the number of log generations.

A.2.5.1.7 IJServer12020

( warn) IJServer12020: Rollover log file has already existed. Rollover process is performed next time with the new name. file="<filename>" pid=<pid> tid=<tid>

Variable Information

<filename> = Log to be rotated

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

A file with the same name as the log file to be rotated already exists.
Many logs were generated in a short period, so rotation could not be performed.
Log rotation will be performed with a new name the next time a message is output.

User Action

Refer to the other messages that were output to the log file, and remove the cause of many logs being output.

A.2.5.1.8 IJServer12027

(error) IJServer12027: The connection of IJServer was aborted. The following are the most common causes of this error: IJServer stops, Web Application timed out, Setting up SSL on IJServer. serverName=<serverName> serverPort=<serverPort> host=<host> port=<port> uri=<uri> errno=<errno> pid=<pid> tid=<tid>

Variable Information

<serverName> = Server name of Web server

<serverPort> = Port number of Web server

<host> = Host name of container

<port> = Port number of container

<uri> = Web browser request URL

<errno> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

The connection with the container has been interrupted.

Cause

Possible causes are as follows:

1. The container process is forcibly stopped because of an application timeout.

2. The container is stopped.

3. The container is temporarily stopped because an error occurred in the Java application.

4. The container is overloaded. A memory shortage may have occurred in the Java VM.

5. The number of requests that was received exceeded the maximum number of connections to the server instance (JavaVM).

6. The Web server connector Server instance IP address:Port Number settings are incorrect.

7. In other cases, an error may have occurred in the container.

System Action

The Web server connector interrupted connection to the container, and sent the error message status code 500 (Internal Server Error) to the web browser.

User Action

Do as follows:

Additionally, if a message was output to a log mentioned in "Container" of the Operation Guide, take the action advised in the message.

1. If this error message is output frequently, use the add-instance subcommand of the pgx_jadmin command to increase the number of server instances, or check the system configuration (hardware and software) and reconfigure an overload-resistant system. You may also consider upgrading the CPU.

   Refer to the event log (system log), or the logs mentioned in "Container" in the Operation Guide. If there is insufficient JavaVM memory ('OutOfMemoryError' occurs), refer to "Java Function Errors" in the Operation Guide, and then take action.

2. Check the logs mentioned in "Container" of the Operation Guide. If an error has occurred, take action according to the message.

A.2.5.1.9 IJServer12032

( info) IJServer12032: The existing log file is rolled over to a new file. file="<filename>" pid=<pid> tid=<tid>

Variable Information

<filename> =Rotating log

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

The web server connector log was rotated to a new file.

A.2.5.1.10 IJServer12033

( info) IJServer12033: The most recent Web Server Connector properties have been loaded. conf="<filename>" pid=<pid> tid=<tid>

Variable Information

<filename> = Property file of Web server connector

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

The latest Web server connector properties have been loaded.

A.2.5.1.11 IJServer12034

(error) IJServer12034: The requests cannot be sent to Web Application. serverName=<serverName> serverPort=<serverPort> host=<host> port=<port> uri=<uri> func=<func> errno=<errno> pid=<pid> tid=<tid>

Variable Information

<serverName> = Server name of Web server

<serverPort> = Port number of Web server

<host> = Host name of container

<port> = Port number of container

<uri> = Web browser request URL

<func> = Name of the function in which an error occurred

<errno> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

Data cannot be transferred to the Java application.

Cause

Possible causes are as follows:

• A system resource shortage occurred.

• A network or system error occurred.

• The connection with the container was aborted.

User Action

• Check the event log (system log) for system errors.

• Refer to the User Action in message IJServer12027 and take action.

A.2.5.1.12 IJServer12035

(error) IJServer12035: The requests sent to the Web Application did a timeout. Delay in Web Applications or IJServer overloaded. serverName=<serverName> serverPort=<serverPort> host=<host> port=<port> uri=<uri> time=<time> seconds pid=<pid> tid=<tid>

Variable Information

<serverName> = Server name of Web server

<serverPort> = Port number of Web server

<host> = Host name of container

<port> = Port number of container

<uri> = Web browser request URL

<time> = Timeout time

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

A timeout occurred during data transfer to the Web application. The form data sent from the Java browser cannot be transferred to the Java application.

Cause

Possible causes are as follows:

1. Java application processing was delayed.

2. The container is overloaded. A memory shortage may have occurred in the Java VM.

3. A network error occurred between the Web server and container.

System Action

The Web server connector interrupted connection to the container, and sent the error message status code 500 (Internal Server Error) to the web browser.

User Action

If this error message is output frequently, increase the server instance (JavaVM) or check the system configuration (hardware and software) and reconfigure an overload-resistant system. Consider upgrading the CPU as needed.

1. Check whether a processing delay occurred in the Java application.

2. Refer to the event log (system log), or the logs mentioned in "Container" in the Operation Guide. If there is insufficient JavaVM memory ('OutOfMemoryError' occurs), refer to "Java Function Errors" in the Operation Guide, and then take action.

A.2.5.1.13 IJServer12036

(error) IJServer12036: The response of the Web Application cannot be received. serverName=<serverName> serverPort=<serverPort> host=<host> port=<port> uri=<uri> func=<func> errno=<errno> pid=<pid> tid=<tid>

Variable Information

<serverName> = Server name of Web server

<serverPort> = Port number of Web server

<host> = Host name of container

<port> = Port number of container

<uri> = Web browser request URL

<func> = Name of the function in which an error occurred

<errno> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

A response from the Java application cannot be received.

Cause

Possible causes are as follows:

• A system resource shortage occurred.

• A network or system error occurred.

• The connection with the container was aborted.

System Action

The Web server connector interrupted connection to the container, and sent the error message status code 500 (Internal Server Error) to the web browser.

User Action

• Check the event log (system log) for system errors.

• Refer to the User Action in message IJServer12027 and take action.

A.2.5.1.14 IJServer12037

(error) IJServer12037: Unable to create log file. Missing write permission for log file or file is already open with write access. Add write permission on the file or directory. file="<filename>" errno=<errno> pid=<pid> tid=<tid>

Variable Information

<filename> = File name

<error> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

Web server connector message cannot be logged.

Cause

Possible causes are as follows:

1. Write permission is not granted to the log file or the directory to which a log is to be output.

2. The log file has been opened by another application.

3. A directory having the same name as the log file exists.

4. When on a Windows(R) system, the network drive is specified to the log output directory of a Web server connector.

User Action

1. Close the log file.

2. If <filename> is a directory, change or delete the directory.

3. Specify the path name for a log output directory to be on a local disk

4. Move of delete <filename>.

5. Restart the instance.

   .

A.2.5.1.15 IJServer12038

(error) IJServer12038: Unable to create log file. Too many open files. Close some of the opened files or close any unnecessary applications. file="<filename>" errno=<errno> pid=<pid> tid=<tid>

Variable Information

<filename> = File name

<error> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

A Web server connector log file could not be created

Cause

Because too many files were open.

User Action

Terminate other applications, or increase the number of files that can be opened in the system.

A.2.5.1.16 IJServer12039

(error) IJServer12039: Unable to open file. No such file or permission denied. Add read permission on the file. file="<filename>" errno=<errno> pid=<pid> tid=<tid>

Variable Information

<filename> = File name

<error> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

The indicated file cannot be opened.

Cause

Possible causes are as follows:

1. The file does not exist.

2. Read permission is not granted to the file.

3. Too many files are open.

User Action

1. Check whether the file exists.

2. Grant the file read permission.

3. Terminate other applications, or increase the number of files that can be opened in the system.

A.2.5.1.17 IJServer12040

( warn) IJServer12040: Unable to remove old log file. Missing write permission for old log file or file is already open with write access. You must remove the old log file manually. file="<filename>" errno=<errno> pid=<pid> tid=<tid>

Variable Information

<filename> = Name of old log file

<error> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

The indicated old log file cannot be deleted.

Cause

Possible causes are as follows:

• Permission to write to the old log file is not granted.

• The old log file is opened by another application.

User Action

Because the old log file may exhaust the free disk space, manually delete the old log file.

A.2.5.1.18 IJServer12041

( warn) IJServer12041: Unable to rollover log file. pid=<pid> tid=<tid>

Variable Information

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

Log file rollover failed.

Cause

A log file could not be rolled over.

User Action

Take action according to the message that was output to the Web server connector log or event log (system log).

A.2.5.1.19 IJServer12042

( warn) IJServer12042: Unable to run Web Server Connector. conf="<filename>" webtype=<webtype> pid=<pid> tid=<tid>

Variable Information

<filename> = Property file of Web server connector

"none" is output if an error occurs immediately after the Web server connector is activated.

<webtype> = Web server I/F which the Web server connector is using.

"nsapi" is output when Microsoft (R) Internet Information Services is used, and "isapi" is output when Sun Java System Web Server is used.

This variable information is not outputted at the time of use of Interstage HTTP Server.

Property file of Web server connector

"none" is output if an error occurs immediately after the Web server connector is activated.

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

The Web server connector cannot be activated.

System Action

The Web server connector sent the error message status code 404 (Not Found) to the web browser.

The status code 404 (Not Found) may be notified. Moreover, after this message is output, the status code 404 (Not Found) may be notified also to other requests.

User Action

Take action according to the message that was output to the Web server connector log or event log (system log). If the Web server is active, stop it and restart it.

Note

In Microsoft(R) Internet Information Services 6.0, this message is output after the Web Server is started and the first access is made from the client. In Web Servers other than Microsoft(R) Internet Information Services 6.0, this message is output when the Web Server is started.

A.2.5.1.20 IJServer12043

(error) IJServer12043: Unable to write log file. Device was removed or an I/O error occurred. file="<filename>" errno=<errno> pid=<pid> tid=<tid>

Variable Information

<filename> = File name

<errno> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

Web server connector messages cannot be logged.

Cause

An I/O error occurred. The disk was removed or the availabilities of a disk are insufficient.

User Action

Check the event viewer (system log) to check for system errors.

A.2.5.1.21 IJServer12044

(error) IJServer12044: Web Application does not respond. Web Application has timed out. Delay in Web Applications or IJServer overloaded. serverName=<serverName> serverPort=<serverPort> host=<host> port=<port> uri=<uri> time=<time> seconds pid=<pid> tid=<tid>

Variable Information

<serverName> = Server name of Web server

<serverPort> = Port number of Web server

<host> = Host name of container

<port> = Port number of container

<uri> = Web browser request URI

<time> = Timeout time

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

The Web application does not respond. A timeout occurred during waiting for a response from the Java application.

Cause

Possible causes are as follows:

1. The Java application failed to respond within the specified timeout time.

2. Java application processing was delayed.

3. The container is overloaded. A memory shortage may have occurred in the Java VM.

4. A network error occurred between the Web server and container.

System Action

The Web server connector interrupted connection to the container, and sent the error message status code 500 (Internal Server Error) to the web browser.

User Action

1. Check whether a processing delay or a hang-up occurred in the Java application.

2. If this error message is produced frequently, increase the server instances (Java VM) by referring to "Adding or Deleting Server Instances (Java VM)" under "Setting up and Operating PL/extJava" in the Operation Guide, or check the system configuration (hardware and software) and reconfigure an overload-resistant system. Consider upgrading the CPU as needed.

   Refer to the event log (system log), or the logs mentioned in "Container" in the Operation Guide. If there is insufficient JavaVM memory ('OutOfMemoryError' occurs), refer to "Java Function Errors" in the Operation Guide, and then take action.

A.2.5.1.22 IJServer12045

( warn) IJServer12045: Web Server Connector properties could not be loaded. conf="<filename>" pid=<pid> tid=<tid>

Variable Information

<filename> = Property file of Web server connector

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

The property file of the Web server connector cannot be loaded. The Web server connector operates with the properties most recently loaded, or those properties used at start of the Web server.

The Web server connector operates with the properties most recently loaded, or those properties used at start of the Web server.

The Web connector posts status code 500 (Internal Server Error) to the Web browser.

The Web connector posts status code 500 (Internal Server Error) to the Web browser also to the request after this message was output.

User Action

Refer to the Operation Guide, and take the action advised in the message output to the internal log or event log (system log).

A.2.5.1.23 IJServer12047

( info) IJServer12047: Web Server Connector running. conf="<filename>" pid=<pid> tid=<tid>

Variable Information

<filename>= Web server connector property file
<pid>= Web server process ID
<tid>= Web server thread ID

Explanation

The Web server connector has been activated.

A.2.5.1.24 IJServer12048

( info) IJServer12048: Web Server Connector stops running. conf="<filename>" pid=<pid> tid=<tid>

Variable Information

<filename>= Web server connector property file
<pid>= Web server process ID
<tid>= Web server thread ID

Explanation

The Web server connector has been stopped.

A.2.5.1.25 IJServer12049

(error) IJServer12049: Unable to open file. Too many open files. Close some of the opened files or close any unnecessary applications. file="<filename>" errno=<errno> pid=<pid> tid=<tid>

Variable Information

<filename> = File name

<errno> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

A file cannot be opened.

Cause

There are too many opened files.

User Action

End other applications or increase the number of files that can be opened by the system.

A.2.5.1.26 IJServer12050

(error) IJServer12050: Unable to open file. Missing write permission for file or file is already open with write access. Add write permission on the file or directory. file="<filename>" errno=<errno> pid=<pid> tid=<tid>

Variable Information

<filename> = File name

<errno> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

Unable to open file.

Cause

Possible causes are as follows:

• There is no authority written in the directory to which the file exists.

• The file is already opened by another application.

• A directory exists with the same name as the file.

User Action

Close the file.

When <filename> is a directory, move the directory or delete the directory.

A.2.5.1.27 IJServer12051

(error) IJServer12051: Unable to read file. Device was removed or an I/O error occurred. file="<filename>" errno=<errno> pid=<pid> tid=<tid>

Variable Information

<filename> = File name

<errno> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

Unable to read file.

Cause

The I/O error occurred. The disk may have been removed.

User Action

Check whether with reference to an event log (system log), there are any abnormalities in a system.

A.2.5.1.28 IJServer12052

(error) IJServer12052: Unable to write file. Device was removed or an I/O error occurred. file="<filename>" errno=<errno> pid=<pid> tid=<tid>

Variable Information

<filename> = File name

<errno> = Error number

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

Unable to write file.

Cause

The I/O error occurred. The disk may have been removed, or be insufficiently available.

User Action

Check whether with reference to an event log (system log), there are any abnormalities in a system.

A.2.5.1.29 IJServer12054

(error) IJServer12054: HTTP request which contains wrong header was received. header=<http_header> pid=<pid> tid=<tid>

Variable Information

<http_header> = HTTP header

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

An HTTP request containing an illegal HTTP header was received.

Cause

The server may have been attacked externally.

System Action

The Web server connector aborts the connection to the container and notifies a status code 400 (Bad Request) message to the Web browser.

User Action

Based on the IP address or host name of the request source that is output to the access log described in "Web Server" in the Operation Guide, investigate the possibility that an attack has occurred.

A.2.5.1.30 IJServer12055

(error) IJServer12055: Web Server does not exist. pid=<pid> tid=<tid>

Variable Information

<pid> = Web server process ID

<tid> = Web server thread ID

Explanation

The Web server does not exist.

Cause

A system error occurred.

User Action

Contact a service engineer.

A.2.5.1.31 IJServer12056

(error) IJServer12056: A system error was returned by the operating system. func=<func> error=<error> pid=<pid> tid=<tid>

Variable Information

<func>= Function in which the error occurred

<error>= Error ID

<pid>= Web server process ID

<tid>= Web server thread ID

Explanation

A system error was returned by the operating system.

Cause

An operating system error occurred in the processing of the web server connector.

Another program may have locked an internal file of the web server connector.

User Action

Check if another program has locked a file under "Server Server installDir/java". If it has, stop the processing.

If the problem cannot be resolved, contact Fujitsu technical support.

A.2.5.1.32 IJServer12057

(error) IJServer12057: Unable to initialize Web Server Connector. pid=<pid> tid=<tid>

Variable Information

<pid>= Web server process ID

<tid>= Web server thread ID

Explanation

Web server connector initialization failed.

User Action

Contact Fujitsu technical support.

A.2.5.1.33 IJServer12058

( warn) IJServer12058: Web Server Connector property file contains an illegal value. conf=<filename> section=<section> key=<key> value=<value> pid=<pid> tid=<tid>

Variable Information

<filename>= Web server connector property file

<section>= Section in the web server connector property file

<key>= Key in the web server connector property file

<value>= Value specified in the web server connector property file

<pid>= Web server process ID

<tid>= Web server thread ID

Explanation

An invalid value was set in the web server connector property file.

User Action

Contact Fujitsu technical support.

A.2.5.1.34 IJSErver12060

(error) IJServer12060: Internal error. detail={0} pid=<pid> tid=<tid>

Variable Information

{0}: Detailed message
<pid>= Web server process ID
<tid>= Web server thread ID

Explanation

An internal error occurred.

User Action

Contact Fujitsu technical support.

A.2.5.2 When there is no Message Number

If not explained in the Messages, identify the cause of the problem from the message body and take appropriate action. If the problem still exists, contact Fujitsu technical support.