You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Alexander Klimetschek (Created) (JIRA)" <ji...@apache.org> on 2011/10/18 17:43:10 UTC
[jira] [Created] (SLING-2249) BufferedPrintWriter logging misses
argument # of chars
BufferedPrintWriter logging misses argument # of chars
------------------------------------------------------
Key: SLING-2249
URL: https://issues.apache.org/jira/browse/SLING-2249
Project: Sling
Issue Type: Bug
Components: Engine
Affects Versions: Engine 2.2.0
Reporter: Alexander Klimetschek
Priority: Minor
In debug logging, the BufferedPrintWriter always logs the placeholder "{0}" instead of the actual number of chars:
org.apache.sling.engine.impl.output.BufferedPrintWriter write: Writing {0} characters to the buffer
org.apache.sling.engine.impl.output.BufferedPrintWriter flush: Flushing {0} characters
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (SLING-2249) BufferedPrintWriter logging misses
argument # of chars
Posted by "Alexander Klimetschek (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Klimetschek closed SLING-2249.
----------------------------------------
Oh, good to know :-)
> BufferedPrintWriter logging misses argument # of chars
> ------------------------------------------------------
>
> Key: SLING-2249
> URL: https://issues.apache.org/jira/browse/SLING-2249
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: Engine 2.2.0
> Reporter: Alexander Klimetschek
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: Engine 2.2.4
>
>
> In debug logging, the BufferedPrintWriter always logs the placeholder "{0}" instead of the actual number of chars:
> org.apache.sling.engine.impl.output.BufferedPrintWriter write: Writing {0} characters to the buffer
> org.apache.sling.engine.impl.output.BufferedPrintWriter flush: Flushing {0} characters
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-2249) BufferedPrintWriter logging misses
argument # of chars
Posted by "Carsten Ziegeler (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-2249.
-------------------------------------
Resolution: Fixed
Fix Version/s: Engine 2.2.4
Assignee: Carsten Ziegeler
This has been fixed by SLING-2039 - the whole buffering has been removed with
the 2.2.4 release
> BufferedPrintWriter logging misses argument # of chars
> ------------------------------------------------------
>
> Key: SLING-2249
> URL: https://issues.apache.org/jira/browse/SLING-2249
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: Engine 2.2.0
> Reporter: Alexander Klimetschek
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: Engine 2.2.4
>
>
> In debug logging, the BufferedPrintWriter always logs the placeholder "{0}" instead of the actual number of chars:
> org.apache.sling.engine.impl.output.BufferedPrintWriter write: Writing {0} characters to the buffer
> org.apache.sling.engine.impl.output.BufferedPrintWriter flush: Flushing {0} characters
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira