Netty seems to get stuck on routes with browsers

[aspyker]

Using curl you can switch between /ping and /healthcheck and you get expected data. Curl commands don't use http persistent connections.

Using Chrome or Safari, if you go to /ping and then /healthcheck you get pong for healthcheck. Similary if you go to /healthcheck and then /ping you get healthcheck status.

I validated via netstat that Chrome keeps a http persistent connection to Prana. It turns out that as long as this stays open you get stuck in the routes. I closed Chrome to the point of killing the process and was able to see the other url (but then got stuck again).

[diptanu]

Word on the street is that @NiteshKant has fixed it in RxNetty, and is going to come out in the next few days. I am going to pick the new release up and release 0.0.2 of Prana.

[diptanu]

@NiteshKant Can we close this now? We could move to a new version of RxNetty

[phorst]

I hit this issue today. First time trying out Prana and thought it was something I was doing.

[NiteshKant]

I think this was related to the karyon issue: Netflix/karyon#126
which was fixed in 2.2.00-ALPHA1

[rob-mccann]

does anyone have an update for this? I'm regularly hitting this issue.

[NiteshKant]

The issue is fixed in karyon, I guess prana has to pick up the latest version of karyon.

[aspyker]

Thank you all for the contribution. More will be coming, but please see http://ispyker.blogspot.com/2015/10/towards-being-better-about-open-source.html for a bit of context on the status of this project.