[
https://issues.apache.org/jira/browse/GERONIMO-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849993#action_12849993
]
Delos Dai commented on GERONIMO-5157:
-------------------------------------
1) From tomcat 6.0.20, there are some improvement for comet mechanism. So
that's the reason why response returns faster than before.
2) For the empty response, server give a quick end which is caused by reaching
end of request input stream. You may find the statement in tomcat comet
introduction - "End will also be called when data is available and the end of
file is reached on the request input (this usually indicates the client has
pipelined a request)." To avoid this, you can't read request inputstream when
handling BEGIN event. Instead, begin handle your request inputstream in READ
event. Then, you may find no empty response.
Hope it helps!
> Tomcat 6.0.20 NIO connector cause connection always terminates in a very
> short time interval
> --------------------------------------------------------------------------------------------
>
> Key: GERONIMO-5157
> URL: https://issues.apache.org/jira/browse/GERONIMO-5157
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.1.5
> Reporter: Rex Wang
> Assignee: Ashish Jain
> Fix For: 2.1.5
>
>
> Hi,
> I have a sample application which uses the Web messaging service tosimulate
> stock quotes to a Dojo-enabled client application and i use Tomcat NIO
> connector for comet support. I tried deploying the application in
> G2.1.5-snapshot the stock quotes update doesn't happen properly but it works
> very well in G2.1.4. A look at the requests inthe firebug shows that the
> bayeux connection always terminates in a very
> short time interval. however, I don't see any exceptions or errors in the
> console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
