geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-1128) Derby Log Viewer performance problem
Date Fri, 09 Dec 2005 00:06:10 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1128?page=all ]

Aaron Mulder updated GERONIMO-1128:
-----------------------------------

    Fix Version: 1.0
                     (was: 1.1)
        Version: 1.0-M5
                     (was: 1.0)
      Assign To: Aaron Mulder  (was: Donald Woods)

> 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-M5
>  Environment: Win32 w/ latest 1.4.2 JDK
>     Reporter: Donald Woods
>     Assignee: Aaron Mulder
>      Fix For: 1.0

>
> 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


Mime
View raw message