Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Log Manager portlet options are depicted illustrated in the following figure. From this portlet you can specify the location of the log configuration file. By default this value is set to var/log/server-log4j.properties.

...

From this portlet you can also change the Log Level. By default this value is set to INFO, the possible values you can choose from are All, DEBUG, INFO, WARN, ERROR, FATAL, TRACE and OFF.

Server Log

...

Viewer

The Server Log Server Viewer portlet options are illustrated in the following figure. From this portlet you can view the Geronimo server logs as well as set filters for refining the results displayed.

Image RemovedImage Added

The Reset link on the upper left corner will reset any filtering criteria you may have specified to the Geronimo Administration Console's defaults and will display the last 11 10 lines (if any) of the current Geronimo server log.

The Filter Results: area will let you specify different filtering criteria for narrowing down your search. The File pull-down menu allows you to select the log file to view. Lines ..to.. lets you specify a range of line of log to analyze. Max Results limits the number of lines to be displayed. Level displays only those errors occurred for that Log Level. Containing text lets you enter a specific string to search through the server log. With Exceptions by clicking this checkbox will be displayed not just the error but also the exception, the stack trace display will be limited to the number lines set by the Max Results value.

Derby Log Viewer

The Derby Log viewer portlet options are illustrated in the following figure. From this portlet you can view the Derby server logs as well as set filters for refining the results displayed.

Image Added

The Reset link on the upper left corner will reset any filtering criteria you may have specified to the Geronimo Administration Console's defaults and will display the last 10 lines (if any) of the current Derby server log.

Similar to the #Server Log Viewer

Performance monitoring

Adding new listeners for the Web containers

...