You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org> on 2005/11/04 20:13:19 UTC

[jira] Updated: (GERONIMO-1128) Derby Log Viewer performance problem

     [ http://issues.apache.org/jira/browse/GERONIMO-1128?page=all ]

Matt Hogstrom updated GERONIMO-1128:
------------------------------------

    Fix Version: 1.1

> Derby Log Viewer performance problem
> ------------------------------------
>
>          Key: GERONIMO-1128
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1128
>      Project: Geronimo
>         Type: Bug
>   Components: console
>     Versions: 1.0
>  Environment: Win32 w/ latest 1.4.2 JDK
>     Reporter: Donald Woods
>      Fix For: 1.1

>
> When the Derby Log Viewer is rendered on the Servers Log page, the DerbyLogHelper.java copying ALL lines from derby.log and sending it back as a request attribute.  As the Derby logfile grows, this will consume more server cycles and eventually impact other user apps and response time.
> Also, the BufferedReader/FileReader is never closed, so this will leak a file handle everytime the page is rendered.
> This portlet needs to be replaced with the logmanager/LogViewerPortet implementation, so users can choose how many lines to display....

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira