[ 
https://issues.apache.org/jira/browse/OFBIZ-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14142027#comment-14142027
 ] 

Pranay Pandey edited comment on OFBIZ-254 at 9/20/14 3:05 PM:
--------------------------------------------------------------

Its quite old issue, lets try concluding it. I looked around and found there is 
fix present for ajax calls, with Debug.verboseOn() in RequestHandler line 
number 996 in current code. What do you think of having it enabled in normal 
case too when user cancels the requests, instead of full stack trace we can opt 
to log in case verboseon. 

Please find patch attached for the same. 

Thanks.



was (Author: pandeypranay):
Hi Jacopo,

Its quite old issue, lets try concluding it. I looked around and found there is 
fix present for ajax calls, with Debug.verboseOn() in RequestHandler line 
number 996 in current code. What do you think of having it enabled in normal 
case too when user cancels the requests, instead of full stack trace we can opt 
to log in case verboseon. 

Please find patch attached for the same. 

Thanks.


> Noisy, Possibly Unnecessary Logging when a browser request is cancelled by 
> the user
> -----------------------------------------------------------------------------------
>
>                 Key: OFBIZ-254
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-254
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>            Reporter: Jacopo Cappellato
>            Priority: Minor
>
> Copy of an issue created by Joe Eckard in the old server:
> If a user requests a page and cancels that request before the page is 
> rendered and returned, a ClientAbortException is thrown in 
> RequestHandler.renderView() - at resp.flushBuffer() line 551. This propagates 
> up to ControlServlet where it is logged, adding 50 lines or so to the logfile 
> for each occurence, which is pretty noisy when attempting to debug a site 
> with many users. Not sure if we would ever care that resp.flushBuffer() 
> encountered a problem, therefore not sure of the best fix.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to