-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Prashant,
On 3/6/14, 12:43 AM, Prashant Kadam wrote:
>> May be I failed to explain properly my understanding, I will
>> explain the scenario once again
No, I get it. You just aren't answering the questions I'm asking.
>> I am including one jsp in another jsp, there are different
>> behaviors for 2 tomcat versions as below
>
>> 1. case in 7.0.37 - setCommitted(true) was called and thus in
>> tiles code (pasted below), it includes the jsp and works fine
>> with no exception thus no stack strace
>
>> TilesRequestProcessor class protected void doForward( String uri,
>> HttpServletRequest request, HttpServletResponse response) throws
>> IOException, ServletException { if (response.isCommitted()) {
>> this.doInclude(uri, request, response); } else {
>> super.doForward(uri, request, response); } }
>
>> 2. case in 7.0.39 - setCommitted() was not being called and thus
>> default is false, and in this case it tries to forward and thus
>> call super.doForward(uri, request, response) as per above code.
>> Now as response is already committed but due to this flag value
>> being false, it tries to flush again giving issue of flushing of
>> already flushed response. so the problem is, if response is
>> already committed why this org.apache.coyote.Response.isCommitted
>> not being set to true ?
1. In Tomcat 7.0.37, what is the full stack trace for when
setCommitted is called?
2. In Tomcat 7.0.39, what makes you think that the response has been
committed if setCommitted(true) is never called? What makes you think
that setCommitted(true) /should/ have been called?
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJTGfD9AAoJEBzwKT+lPKRYH3sQALtT4AWxANO7nC/a5RuyQanr
NWXbM2V8eCHYH09f6Y2t05/i3DVpOkVkxneXPZugvHsfEZzjl7MnAYjWodzQvRnu
7dRCc67BILo3XMr/mqo6rFgTouGsQOetiT8bVfqbKrhxuqtUnV1VULNQNFmOjRnU
PMYc9ppinGSEnedL9dvrJt3k2jYYR+vef2YXC5VskEC6S1NShJAB/l1RM0DXbKku
luscrMtTqzGLtmNtj6iuKBePvlIhtGBNEnxn2GEQEiIAiD1yxuUK679e8l+2UArp
ofuiLavlwIq8mPgChivGN3aigde6R5xxm9PcuUE48sZKKD1uRORNDeZ5uHRP+gWd
8Oh4jY4nXH2RNsWwWJjU3q6aw34Oo3XiBspolurIkwYldlsBfkyzDfk7n3ZNoaCv
G5krLjFhXN9NbH7GrqjR3tB6WedOJaGkeG4EtufBAh5k0+Fil942MUo7ym3IiWuJ
7sX2peTvRJUXEpTks09UhHFPjzBtjlvl9iSFI0FjwTaL2JVe7nthzWPzCBumwQvf
j1unT4wezrh9c6KXnjN2Tf+2HW4Y1YJB7PYYBGrOEuQ6ppSbLoqBNQNlUMytPrlN
hvGh836r32zvp7NLKkooJeI6GIGCw/VyecDhBPYjwtlVC3DSXR0qOoyVyGQScvjI
ScB+CsVsZrmIjcdR3E1C
=1q0U
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
