Mrunal Patel <mpatel@redhat.com> made a comment on bug 1005373

Hi, Daniel,
You can disregard the previous comment. I was comparing different requests.

The main difference I see for this request between the success and failing
case is

SUCCESS:

1380673106880:DEBUG:[01/Oct/2013:20:18:26 -0400] -

{"host":"timeout-testbz.dev.rhcloud.com:8443","conne$ tion":"keep-alive","access-control-request-method":"POST","origin":"http://localhost:8001","user-agent"$ "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.76 Safari/537.$ 6","access-control-request-headers":"origin, content-type","accept":"*/*","referer":"http://localhost:8$ 01/","accept-encoding":"gzip,deflate,sdch","accept-language":"en-US,en;q=0.8"}

1380673106885:DEBUG:[01/Oct/2013:20:18:26 -0400] - Sent headers[object Object]
1380673106885:DEBUG:[01/Oct/2013:20:18:26 -0400] - end

In cartridge logs:
2013/10/01 20:18:26,232 INFO [org.jboss.aerogear.simplepush.server.netty.NotificationHandler] (nioEventLoopGroup-4-2) /simplepush/info
2013/10/01 20:18:26,561 INFO [org.jboss.aerogear.simplepush.server.netty.NotificationHandler] (nioEventLoopGroup-4-3) /simplepush/025/39rawn3l/xhr_streaming
2013/10/01 20:18:26,564 INFO [org.jboss.aerogear.simplepush.server.netty.SimplePushSockJSService] (nioEventLoopGroup-4-3) SimplePushSockJSServer onOpen
2013/10/01 20:18:26,883 INFO [org.jboss.aerogear.simplepush.server.netty.NotificationHandler] (nioEventLoopGroup-4-4) /simplepush/025/39rawn3l/xhr_send
2013/10/01 20:18:27,698 INFO [org.jboss.aerogear.simplepush.server.netty.NotificationHandler] (nioEventLoopGroup-4-1) /simplepush/025/39rawn3l/xhr_send
2013/10/01 20:18:27,700 INFO [org.jboss.aerogear.simplepush.server.netty.SimplePushSockJSService] (nioEventLoopGroup-4-1) messageType: HELLO
2013/10/01 20:18:27,709 INFO [org.jboss.aerogear.simplepush.server.netty.SimplePushSockJSService] (nioEventLoopGroup-4-1) UserAgent [44b53156-ca55-4387-be01-207ac75ea2fa] handshake done

FAILURE:
1380673113877:DEBUG:[01/Oct/2013:20:18:33 -0400] -

{"host":"timeout-testbz.dev.rhcloud.com:8443","connec tion":"keep-alive","access-control-request-method":"POST","origin":"http://localhost:8001","user-agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.76 Safari/537.3 6","access-control-request-headers":"origin, content-type","accept":"*/*","referer":"http://localhost:80 01/","accept-encoding":"gzip,deflate,sdch","accept-language":"en-US,en;q=0.8"}

1380673115955:DEBUG:[01/Oct/2013:20:18:35 -0400] - data
1380673115955:DEBUG:[01/Oct/2013:20:18:35 -0400] - h

1380673119407:DEBUG:[01/Oct/2013:20:18:39 -0400] - data
1380673119407:DEBUG:[01/Oct/2013:20:18:39 -0400] - h

1380673131566:DEBUG:[01/Oct/2013:20:18:51 -0400] - data

In cartridge logs:
2013/10/01 20:18:33,365 INFO [org.jboss.aerogear.simplepush.server.netty.NotificationHandler] (nioEventLoopGroup-4-2) /simplepush/info
2013/10/01 20:18:33,622 INFO [org.jboss.aerogear.simplepush.server.netty.NotificationHandler] (nioEventLoopGroup-4-3) /simplepush/627/7q42rnqd/xhr_streaming
2013/10/01 20:18:33,629 INFO [org.jboss.aerogear.simplepush.server.netty.SimplePushSockJSService] (nioEventLoopGroup-4-3) SimplePushSockJSServer onOpen

In the second case, the data keeps on trickling and doesn't seem to stop.
Is that expected behavior given that the sequence of requests on load for both the cases are the same and on the 5th load, there is this change in behavior.

Thanks,
Mrunal

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira