G.2.1 Server Log

Output destination

The server log is output to the following file:

domainRoot\nodes\localhost-domain1\serverInstance(JavaVM)Name\logs\server.log

Output details

Number of generations
1
Maximum log size
1,048,576 bytes
Length of Record
Variable
Rotation conditions
If the maximum log size If the maximum log size is exceeded, old information will be saved to a file with the original name followed by rotation datetime.
[Example]
```
server.log_2012-01-07T15-23-30
```

Output example

 [#|2014-03-18T18:20:16.653+0900|INFO|||_ThreadID=1;_ThreadName=main;|SEC1010: Entering Security Startup Service|#]

[#|2014-03-18T18:20:16.653+0900|INFO|||_ThreadID=1;_ThreadName=main;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]

[#|2014-03-18T18:20:17.230+0900|INFO|||_ThreadID=1;_ThreadName=main;|SEC1115: Realm [admin-realm] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.|#]

[#|2014-03-18T18:20:17.261+0900|INFO|||_ThreadID=1;_ThreadName=main;|SEC1115: Realm [file] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.|#]

[#|2014-03-18T18:20:17.277+0900|INFO|||_ThreadID=1;_ThreadName=main;|SEC1115: Realm [certificate] of classtype [com.sun.enterprise.security.auth.realm.certificate.CertificateRealm] successfully created.|#]

Message details

The following explains the messages output in PL/extJava environments.

Output format
Messages are output in the following format:
```
[#|yyyy-MM-ddTHH:mm:ss.msTZD|logLevel|||_ThreadID=IDthreadId;_ThreadName=threadName;| messageBody|#]
```
- logLevel
  Fixed to "INFO".
- messageBody
  Text output by the PL/extJava environment.
Note
Note the following about the log content:
- If a user Java application detects an exception, only the class name of the exception is output.
- For security reasons, the exception stack trace and exception message are not output.

Output format (message body)

The message body is output in the following format:

logLevel: symfo-plextjava: [resultCode] message [backend_process=pid]

logLevel
Fixed to " ERROR".
Log level
Output content
ERROR
Error information when an error occurs

Log level	Output content
ERROR	Error information when an error occurs

resultCode

The following return values are returned:

Return value	Explanation
0	Returned successfully.
1001	An internal error was detected. (protocol rule violation) Contact Fujitsu technical support.
2001	An internal error was detected. (protocol rule violation) Contact Fujitsu technical support.
2002	The Java application to be run cannot be found. Check if the jar file of the Java application has been registered, the FUNCTION specification contains an error, or the created Java application contains an error. [Considerations] Was the "packageName.className.methodName" specified during registration of FUNCTION correct? Does the "(Java function) arguments" specified during registration of FUNCTION match the type and number of arguments of the created Java application? Does the return value type specified during registration of FUNCTION match the type of the return values for methods of the created Java application? Have the methods of the created Java application been created as static methods (static) with the access modifier "public"?
3001	The user does not have privileges to run the Java application. Check the privileges for running Java applications. [Considerations] Has the access modifier of the class of the created Java application been created as "public"?
3002	An exception occurred while the Java application was running. Check the database status or the processing content of the Java application.
9001	An internal error was detected. (environment error) Contact Fujitsu technical support.

backend_process
PID of the Symfoware Server (backend) process.