[ 
https://issues.apache.org/jira/browse/GERONIMO-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841368#action_12841368
 ] 

Ashish Jain commented on GERONIMO-5157:
---------------------------------------

I was able to increase the performance of the stock quotes refresh and now I 
see very frequent updates. For this I have modifed some part of the  web 
messaging code. However I still see that there are requests with empty 
responses. Also I see cpu usage going up. 

Further I see that in tomcat the processing being done by 
HTTP11NioProcessor.event has been moved to HTTP11NioProcessor.process in 
6.0.20. I am still looking into this issue. Since this is multithreaded I am 
finding some difficulty in getting to the actual cause. Any suggestions on how 
to debug effectively will be really helpful.

> 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) 
>    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.

Reply via email to