The Solar Eclipse application server uses the log4j logging engine to record its activity and communications to the SolarServer.log file that is located on your application server at
/u2/eclipse/modules /jboss/server/eclipse/log. The SolarServer.log file is an encrypted file that the system sends to Eclipse every two minutes. You cannot view this log file on your system.
Note: If you need to review the log file, the application server also records its activity and communications to the server.log file that is located on your application server at /u2/eclipse/modules /jboss/server/eclipse/log. This is a plain text file that you can view.
The application server is set up to record messages at the Error logging level and is also set up to roll to a new file every hour. When the system rolls to a new file, the file name reflects the day and time the roll over occurred using the following format: SolarServer.log-YYYY-MM-DD-HH. The rolling interval, logging level, and other parameters are configurable within the logging engine, however, we recommend that you not make significant changes to the logging parameters for the server file without speaking to Eclipse support for assistance.
The application server error log contains the following information, any or all of which is helpful when troubleshooting issues with your Solar Eclipse application server:
|
Error Log Parameter |
Description |
|
Date/Time |
The calendar date and the time when the error took place. |
|
Severity |
The error's severity level, such as Fatal. |
|
Application |
The application that caused the error. This parameter is always Solar Eclipse. |
|
Release |
The version of Solar Eclipse you are running, such as 8.6.0.04. |
|
Message |
Details about what the system recorded. For example, the message may contain information regarding how a subroutine was called. |
|
Stack Trace |
The Java exception stack trace. A stack trace indicates portions of the code that are calling other portions of code. The code is referenced by methods and line numbers. |
|
Thread |
The thread within the Solar Eclipse code that triggered |
|
Logger |
The class within the Solar Eclipse code that triggered |
|
Account Name |
The name of the account, such as Training or Production. |
|
Eterm Account Host |
The system that hosts the Universe database. |
|
Eterm Account Port |
The Universe connection port, for example, 20353. |
|
Build Date |
The date the software was compiled and built for deployment to customer sites. |
See Also: