https://issues.apache.org/bugzilla/show_bug.cgi?id=50883
Ashish <dashashishku...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ErrorMessage
URL| |https://issues.apache.org/b
| |ugzilla/show_bug.cgi?id=508
| |83
--- Comment #2 from Ashish <dashashishku...@gmail.com> 2011-03-08 22:56:33 EST
---
Mark thanks for your response.
I have used following kinda methods at many places in my app.
protected void logUserDetails(HttpServletRequest request){
request.setAttribute("APP_ID", "myappid");
}
But surprisingly this StackOverflowError is coming randomly around 3 times in a
month and these methods are serving fine to rest all request with out any
StackOverFlowError. SO here am looking for your help to understand in which
scenario this request object becoming an instance of ServletRequestWrapper and
undergoing that recursion.
Also one more doubt I have, are we not suppose to call the setAttribute() and
getAttribute() methods of ServletRequestWrapper.
(In reply to comment #1)
> Looks like something in your app is calling setRequest() on a wrapper and
> passing in the wrapper rather than the request to be wrapped. The Servlet
> specification does not provide for throwing an exception in this case. I'll
> add
> that to my list of things to raise for the next version of the spec.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
