https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
--- Comment #12 from Scott Nicklous ---
I would not see a problem in handling the SC=500 as long as onComplete() is
called. It would seem to me to be the specified behavior.
In the case of Pluto, the SC=500 along with any Tomcat-generated err
https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
--- Comment #11 from Mark Thomas ---
It is worth taking a look to see if we can get consistent behaviour with and
without flush. The client won't see the same result but hopefully the app will
be able to see a consistent set of events.
--
You
https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
--- Comment #10 from Violeta Georgieva ---
(In reply to Scott Nicklous from comment #9)
> In the specific case addressed by this bug report, both onTimeout() and
> onComplete() are correctly called as long as the buffer is not flushed.
>
> Th
https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
--- Comment #9 from Scott Nicklous ---
In the specific case addressed by this bug report, both onTimeout() and
onComplete() are correctly called as long as the buffer is not flushed.
The problem occurs only when the buffer was flushed at leas
https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
--- Comment #8 from Violeta Georgieva ---
If you wait for Tomcat to invoke a complete(), then this will be an error
situation and as it is per spec Tomcat will set the response code to 500. Isn't
that a problem from application point of view?
https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
--- Comment #7 from Scott Nicklous ---
Hi Violeta,
That would be a potential workaround for the timeout case. I would have to
ensure that the Pluto listener runs after all AsyncListeners registered by the
portlet applications.
It would be a l
https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
--- Comment #6 from Violeta Georgieva ---
(In reply to Scott Nicklous from comment #5)
> I know what you mean and agree with you.
>
> From Tomcat's point of view, the Pluto portal is an application. However,
> Pluto itself hosts portlet appli
https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
--- Comment #5 from Scott Nicklous ---
I know what you mean and agree with you.
>From Tomcat's point of view, the Pluto portal is an application. However, Pluto
itself hosts portlet applications that may come from various sources. The
questio
https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
--- Comment #4 from Remy Maucherat ---
The question is really about the cases where complete should be called for the
application (which didn't call it although it should have).
--
You are receiving this mail because:
You are the assignee for
https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
--- Comment #3 from Scott Nicklous ---
Hi Violeta and Remy,
thank you very much for having a look at this so quickly (and thank you, Remy
for fixing 59213 so promptly!). The example servlets I provided were for the
purpose of reproducing the
https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
--- Comment #2 from Remy Maucherat ---
That sounds like a logical explanation and 59219 sounds a bit similar. This is
all edge cases though and I doubt everything is well defined in the
specification. So it is best to not try it :)
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=59220
Violeta Georgieva changed:
What|Removed |Added
OS||All
--- Comment #1 from Violeta Ge
13 matches
Mail list logo
