Symfoware Server V12.1.0 Messages

A.2.22 Messages without a Message ID

A.2.22.1 Messages that are Output when the pgx_jadmin Command is Executed

Authentication failed for user: {0}
(Usually, this means invalid user name and/or password)

Variable Information

{0}: User name

Explanation

The admin user ID and/or password is invalid.

System Action

Processing is interrupted.

User Action

Specify the correct user name and password, and then reexecute the command.

com.sun.enterprise.universal.xml.MiniXmlParserException: {0}

Variable Information

{0}: Detail message

Explanation

Failed to parse domain.xml.

System Action

Processing is interrupted.

User Action

The product environment has been corrupted, therefore reinstall the product.

Command {0} failed.

Variable Information

{0}: Subcommand name

Explanation

Failed to execute the command that was output to the Variable Information subcommand name.

System Action

Processing is interrupted.

User Action

Based on the message that was output at the same time, remove the cause of the error, and then reexecute the command.

Command failed on node {0} ({1}): {2}

Variable Information

{0}: Node name
{1}: Host name
{2}: Detail information

Explanation

The command has failed to execute.

System Action

Processing is interrupted.

User Action

Take the action indicated by the message output at the same time, remove the cause of command execution failure, and then reexecute the command.

Could not contact the DAS running at {0}:{1}. This could be because a firewall is blocking the connection back to the DAS or because the DAS host is known by a different name on the instance host {2}. To change the hostname that the DAS uses to identify itself please update the DAS admin HTTP listener address.

Variable Information

{0}: Host name
{1}: Port number

Explanation

Failed to connect to the Java EE DAS service.

System Action

Processing is interrupted.

User Action

The instance may have stopped. Check if it is running.

If the instance is running, it is possible that the ephemeral ports are depleted

Check the network status using the "netstat -a" command, and ensure that a large number of "TIME_WAIT" status connections do not exist. If it is confirmed that the ephemeral ports are depleted, release unnecessary ports. Alternatively, increase the number of ports that can be used as ephemeral ports.

Error starting domain {0}.

Variable Information

{0}: Domain name

Explanation

An error occurred during the Java EE DAS service start processing.

System Action

Processing is interrupted.

User Action

Based on the message that was output at the same time, remove the cause of the error, and then reexecute the command.

Failed to rendezvous with DAS on {0}:{1}. Please check if this server is running, that the host and port are correct, and that this server is configured to allow remote access.

Variable Information

{0}: Host name
{1}: Port number

Explanation

Failed to connect to the Java EE DAS service.

System Action

Processing is interrupted.

User Action

The instance may have stopped. Check if it is running.
If the instance is running, it is possible that the ephemeral ports have run out.

Refer to "java.net.SocketException: No buffer space available (maximum connections reached?)" in "A.2.22.5 Exception Information that Starts with "java.net.SocketException"", and then take the required action.

Failed to start process named {0}. Detail={1}

Variable Information

{0}: Server instance (Java VM) name

{1}: Detail information

Explanation

Failed to start the server instance (Java VM).

System Action

Processing is interrupted.

User Action

Take the following actions:

• Take the action indicated by the message output before and after this message.

• Take the action indicated by the message output to the event log (Windows(R)) or the system log (Linux), and investigate the cause of the failure.

If the problem is still not resolved despite taking the above action, contact Fujitsu technical support.

Failed to start process named {0}. PCMI Error Code={1}.

Variable Information

{0}: Server instance (Java VM) name

{1}: Error information

Explanation

Failed to start the server instance (Java VM).

System Action

Processing is interrupted.

User Action

Take the following actions:

• Take the action indicated by the message output before and after this message.

• Check Error information {1} that was output, and then follow the action advised in the table below.

  Error information {1}	Explanation and Action
  100	Failed to read the PCMI profile, or the value specified for the PCMI profile definition item is incorrect. Recover PL/extJava. If this message continues to be output despite taking the above action, contact Fujitsu technical support.
  700	An error occurred during the instance start processing. Take the action indicated by the message output to the event log (Windows(R)) or the system log (Linux), and investigate the cause of the failure. If a message is not output, investigate the cause of the failure based on the information output to the PL/extJava server log and the Java VM log. If a message that shows a Java VM error is output, refer to "Operation Guide" - " Java Function Errors". In all other cases, take the following actions: There may be insufficient memory. Check if there is sufficient memory. Ensure that the port numbers used by the domain or container are not being used by another application. Recover PL/extJava. If this message continues to be output despite taking the above action, contact Fujitsu technical support.
  Other error information	Contact Fujitsu technical support.

Incorrect current master password. You will not be able to change it.

Explanation

The specified current master password is invalid.

System Action

Processing is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

Instance {0} seems to be offline; command {1} was not replicated to that instance

Variable Information

{0}: Server instance (JavaVM) name

{1}: Subcommand name

Explanation

The server instance (JavaVM) is not running, therefore the synchronization processing could not be performed.

System Action

Processing is continued.

User Action

Not required.

The synchronization processing will be performed automatically when the instance starts the next time.

Invalid boolean value for option: {0}, Value: {1}

Variable Information

{0}: Option name
{1}: Specified value

Explanation

The value that was specified as the "Bool" value option was neither "true" nor "false", therefore execution of the command failed.

System Action

Processing is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

Invalid file for option: --{0}: {1}

Variable Information

{0}: Option name

{1}: Cause of the error

Explanation

Cannot reference the file, therefore execution of the command failed.

System Action

Processing is interrupted.

User Action

Check if the file displayed in Variable Information exists and whether there are sufficient access privileges, and then reexecute the command.

remote failure: {0}: Could not start instance {0} on node {1} ({2}).

Variable Information

{0}: Server instance (JavaVM) name
{1}: Node name
{2}: Host name

Explanation

Failed to start the server instance (JavaVM).

System Action

Processing is interrupted.

User Action

An error occurred during start processing of the instance.

Take the action indicated by the message output at the same time and the message output to the event log (Windows(R)) or the system log (Linux), and investigate the cause of the instance start failure.

If a message has not been output, investigate the cause of the failure based on the information output to the PL/extJava server log and the JavaVM log.

remote failure: Adding User to file realm {0} failed. User name cannot be empty.
User name cannot be empty.

Variable Information

{0}: file realm name

Explanation

The user name that is specified when the file realm user is created cannot be empty.

System Action

Processing is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

remote failure: Authrealm named {0} not found.

Variable Information

{0}: Realm name

Explanation

The realm name does not exist.

System Action

Processing is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

remote failure: File realm {0} does not exist.

Variable Information

{0}: file realm name

Explanation

The file realm name does not exist.

System Action

Processing is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

remote failure: Specified file user {0} not found  No such user [{0}].
No such user [{0}].

Variable Information

{0}: file realm user

Explanation

The file realm user does not exist.

System Action

Processing is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

remote failure: There is no cluster named {0} in this domain.

Variable Information

{0}: Database name

Explanation

The specified database does not exist.

System Action

Processing is interrupted.

User Action

Check if the database exists.

remote failure: Unknown plain text format.  A properly formatted response from a PlainTextActionReporter \n\
always starts with one of these 2 strings: PlainTextActionReporterSUCCESS or PlainTextActionReporterFAILURE.  The response we received from the server was not understood: {0}

Variable Information

{0}: Response message

Explanation

The response that was received is invalid.

System Action

Processing is interrupted.

User Action

Based on the message that was output at the same time, remove the cause of the error, and then reexecute the command.

remote failure: Updating user {0} in file realm {1} failed.  {2}

Variable Information

{0}: User name
{1}: file realm name
{2}: Detail information

Explanation

Failed to update the file realm user.

System Action

Processing is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

remote failure: Updating user in file realm {0} failed. User name cannot be empty.
User name cannot be empty.

Variable Information

{0}: file realm name

Explanation

The user name that is specified when the file realm user is updated cannot be empty.

System Action

Processing is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

remote failure: User {0} does not exist in file realm {1}.  No such user [{0}].
No such user [{0}].

Variable Information

{0}: User name
{1}: file realm name

Explanation

The file realm user does not exist.

System Action

Processing is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

Remote server does not listen for requests on [localhost:{0}]. Is the server up?
No such local command, {1}. To run remote commands, start the application server (e.g. 'asadmin start-domain').

Variable Information

{0}: Port number

{1}: Subcommand name

Explanation

The database is not running using the specified port number.

System Action

Processing is interrupted.

User Action

Start theinstance, or specify the correct port number, and then reexecute the command.

Server {0} is running. You need to stop the instance before the master-password can be changed.

Variable Information

{0}: Server instance (JavaVM) name

Explanation

The server instance has not stopped.

System Action

Processing is interrupted.

User Action

Stop the instance.

Server instance directory {0} does not exist or is not a directory

Variable Information

{0}: Server instance (JavaVM) path

Explanation

The specified server instance (JavaVM) does not exist.

System Action

Processing is interrupted.

User Action

Check if the server instance (Java VM) exists.

Something went wrong in creating the local filesystem for instance {1}: {2}

Variable Information

{0}: Server instance (JavaVM) name
{1}: Error information

Explanation

Failed to create the server instance (JavaVM).

System Action

Processing is interrupted.

User Action

Refer to the error information message output at the same time, and then take the action indicated.

The server exited prematurely with exit code {0}.
Before it died, it produced the following output:
{1}

Variable Information

{0}: Return value

{1}: Message output by the Java EE DAS service

Explanation

During start processing, the Java EE DAS service ended with return value {0}.

System Action

Processing is interrupted.

User Action

Refer to the message {1} output by the Java EE DAS service to remove the cause of the instance start processing failure.

WARNING: Command {0} did not complete successfully on server instance {1}: {2}

Variable Information

{0}:Command name
{1}: Server instance (JavaVM) name
{2}: Exception information

Explanation

The command has failed to execute.

System Action

Processing is interrupted.

User Action

If the exception information output at the same time contains the string "java.net.SocketException: No buffer space available (maximum connections reached?)", the ephemeral ports may be depleted.

Refer to "A.2.22.5 Exception Information that Starts with "java.net.SocketException"" - "java.net.SocketException: No buffer space available (maximum connections reached?)", and then take the required action.

A.2.22.2 Messages that are Output during PCMI Operations

error occured while initializing PcmiTraceLogFilehandler

Explanation

An error occurred during trace log file initialization.

System Action

Processing is continued.

User Action

Privileges to execute commands may not have been set for the user who executed the command. Check the user privileges, and reexecute the command as a user with privileges to execute the command.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

A.2.22.3 Messages that are Output during Web Container Operations

SEVERE: Cannot find port information from domain.xml

Explanation

A port number has not been specified for the HTTP listener.

System Action

Processing to set the port number is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

WARNING: Can not parse network-listener port number: null

Explanation

A port number has not been specified for the HTTP listener.

System Action

Processing to set the port number is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

SEVERE: Config Listener class com.sun.enterprise.v3.services.impl.DynamicConfigListener notification took too long
java.util.concurrent.TimeoutException

Explanation

Failed to initialize the HTTP listener.

System Action

Initialization of the HTTP listener is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

SEVERE: doSelect exception
java.lang.IllegalArgumentException: corePoolsize > maxPoolSize: {0} > {1}

Variable Information

{0}: Minimum pool size
{1}: Maximum pool size

Explanation

The minimum pool size has exceeded the maximum pool size.

System Action

The request is not processed.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

SEVERE: doSelect exception
java.util.concurrent.RejectedExecutionException: The thread pool's task queue is full, limit: {0}

Variable Information

{0}: Queue size

Explanation

The container thread pool queue is full, therefore the request cannot be processed.

System Action

The request is not processed.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

Exception in grizzly thread
java.lang.IllegalArgumentException: Invalid range

Explanation

The value that was specified for the HTTP listener port number is invalid.

System Action

Processing to set the port number is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

SEVERE: Exception while processing config bean changes :
java.lang.NumberFormatException: null

Explanation

A port number has not been specified for the HTTP listener.

System Action

Processing to set the port number is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

INFO: Grizzly Framework {0} started in: {1}ms - bound to [{2}:{3}]

Variable Information

{0}: Internal information
{1}: Internal information
{2}: IP address
{3}: Port number

Explanation

The port number settings have been configured.

WARNING: Invalid address for {0}: {1}

Variable Information

{0}: Listener name
{1}: Network address

Explanation

The network address is invalid.

System Action

Processing is continued.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

INFO: JACC Policy Provider:Failed Permission Check: {0}

Variable Information

{0}: Detail information

Explanation

An attempt to call a method without the required privileges was made.

System Action

Processing is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

WARNING: More than the maximum number of request parameters (GET plus POST) for a single request ([{0}]) were detected. Any parameters beyond this limit have been ignored. To change this limit, set the maxParameterCount attribute on the Connector.

Variable Information

{0}: Maximum value of the HTTP request parameter

Explanation

The number of HTTP request parameters has exceeded the maximum value {0}.

System Action

Processing is executed ignoring those parameters which have exceeded the maximum number allowed.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

SEVERE: Network listener configuration error. Type: CHANGE
java.lang.RuntimeException: Cannot find port information from domain configuration

Explanation

A port number has not been specified for the HTTP listener.

System Action

Processing to set the port number is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

INFO: Network listener {0} on port {1} disabled per domain.xml

Variable Information

{0}: HTTP listener name
{1}: Port number

Explanation

The HTTP listener has been disabled.

System Action

Processing is continued.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

WARNING: No Principals mapped to Role [{0}]

Variable Information

{0}: Security role name specified in the deployment descriptor (web.xml)

Explanation

The user or group that corresponds to the security role name specified in the deployment descriptor (web.xml) has not been defined in the Interstage deployment descriptor (glassfish-web.xml).

System Action

Processing is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

WARNING: Realm file: com.sun.enterprise.security.auth.realm.NoSuchUserException: No such user [{0}]

Variable Information

{0}: User or group specified in the Interstage deployment descriptor (glassfish-web.xml) security-role-mapping tag

Explanation

The user or group does not exist in the file realm.

System Action

Processing is interrupted.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

WARNING: Response Error during finishResponse

Explanation

An exception occurred in processing to send the response.

System Action

Processing to send the response is interrupted.

User Action

• The client may have disconnected before the instance returned the response to the client. Review the client settings.

• Follow the action advised in the exception information output at the same time to remove the cause of the error.

StandardWrapperValve[{0}]: PWC1406: Servlet.service() for servlet {1} threw exception

Variable Information

{0}: Servlet name

{1}: Servlet name

Explanation

The servlet service method returned an exception.

System Action

Processing is interrupted.

User Action

Refer to the other messages and exception information that were output at the same time, and remove the cause of the error.

Unable to call method {0} on servlet context {1}, because this servlet context has already been initialized

Variable Information

{0}: Method name
{1}: Context root

Explanation

The Java application of the context root {1} has already been initialized, therefore the method {0} cannot be executed.

User Action

Change the timing for calling the method {0} to when the context is initialized.

SEVERE: Unknown address null

Explanation

The network address is invalid.

System Action

Processing is continued.

User Action

Recover PL/extJava.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

A.2.22.4 Messages that are Output while the Process is Running

SEVERE: Aborting, Failed to start container {0}

Variable Information

{0}: Internal information

Explanation

Failed to start the container.

System Action

Processing is interrupted.

User Action

Refer to the other messages and the exception information output at the same time, and remove the cause of the error.

SEVERE: Cannot start container {0}

Variable Information

{0}: Container name

Explanation

Failed to start the container.

System Action

Processing is interrupted.

User Action

Refer to the other messages and the exception information output at the same time, and remove the cause of the error.

SEVERE: doSelect IOException
java.io.IOException: Unable to establish loopback connection

Explanation

Failed to establish a loopback connection.

System Action

Processing is interrupted.

User Action

If "java.net.SocketException: No buffer space available (maximum connections reached?)" is included in the exception information output at the same time, it is possible that the ephemeral ports have run out.

Refer to "java.net.SocketException: No buffer space available (maximum connections reached?)" in "A.2.22.5 Exception Information that Starts with "java.net.SocketException"", and then take the required action.

SEVERE: doSelect IOException
java.net.BindException: No free port within range: {0}:{1}={2}

Variable Information

{0}: Host name or IP address information
{1}: Port number
{2}: Internal information

Explanation

The specified IP address or port number cannot be used.

System Action

Start processing is interrupted.

User Action

Check if the port number {1} is already being used.

Exception while preparing the app

Explanation

An exception occurred while loading the Java application.

System Action

The Java application load processing is interrupted, and the start processing continues.

User Action

Refer to any error messages output before or after this message, and remove the cause.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

jaccfactory.notfound

Explanation

The JACC factory was not found.

System Action

Processing is interrupted.

User Action

Refer to the other messages and the exception information output at the same time, and remove the cause of the error.

Log Format field separator is not a character so using default.

Explanation

The initial value will be used as the log message separator character.

System Action

Processing is continued.

User Action

Not required.

Record begin marker is not a proper value so using default.

Explanation

The initial value will be used as the log message start string.

System Action

Processing is continued.

User Action

Not required.

Record end marker is not a proper value so using default.

Explanation

The initial value will be used as the log message end string.

System Action

Processing is continued.

User Action

Not required.

SEVERE: Shutting down v3 due to startup exception : Address family not supported by protocol family: bind: {0}:{1}={2}

Variable Information

{0}: Host name or IP address information
{1}: Port number
{2}: Internal information

Explanation

The specified IP address or port number cannot be used.

System Action

Start processing is interrupted.

User Action

Check if the port number {1} is already being used.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

SEVERE: Shutting down v3 due to startup exception : No free port within range: {0}:{1}={2}

Variable Information

{0}: Host name or IP address information
{1}: Port number
{2}: Internal information

Explanation

The specified IP address or port number cannot be used.

System Action

Start processing is interrupted.

User Action

Check if the port number {1} is already being used.

If this message continues to be output despite taking the above action, contact Fujitsu technical support.

A.2.22.5 Exception Information that Starts with "java.net.SocketException"

java.net.SocketException: No buffer space available (maximum connections reached?)

Explanation

Insufficient buffer space.

System Action

Processing is interrupted.

User Action

If this message is output, it is possible that the ephemeral ports have run out.

Check the network status using the "netstat -a" command, and ensure that a large number of "TIME_WAIT" status connections do not exist.

If it is confirmed that the ephemeral ports are depleted, release unnecessary ports. Alternatively, increase the number of ports that can be used as ephemeral ports.