Problem with Lift, Jetty, python2.7/httplib.py, BadStatusLine

43 views
Skip to first unread message

Daniel Roziecki

unread,
Oct 25, 2012, 3:54:44 AM10/25/12
to lif...@googlegroups.com
Hi,

I have big problem with BadStatusLine error at python2.7/httplib.py during connections with Lift/Jetty.

current configuration:

Frontend: Django, Python 2.7
Backend: Lift 2.4 (as webservices), Akka 1.3.1, jetty 8.0.4, scala 2.9.1

Everything is at one physical server (Ubuntu 11.10 Server)

There is no big traffic between Frontend and Backend (+- 5-20 requests/s - usually 5 - 20ms for response)

+- 2% return traffic from Backend to Frontend has empty status line.

I have request at lift, request is properly handled, and finished with status 200, I have no idea what Jetty do with it, but at Frontend side, I have response with empty status (should be 200). Frontend repeat this request, and second time everything is ok. 

As I wrote before, there is +- 2% bad responses.

Any suggestions, ideas?

Best Regards

Daniel Roziecki


Diego Medina

unread,
Oct 25, 2012, 9:29:26 AM10/25/12
to lif...@googlegroups.com
I would try reproducing the error with something like curl, if you
can, then it is on the jetty/lift side. If not, then it probably is on
the python side.
If it turns out to be on the jetty side, see if jetty has some way to
log all the responses, and see if jetty is really returning the wrong
Empty status.
I hope that gives you some ideas of what to try.

Diego
> --
> --
> Lift, the simply functional web framework: http://liftweb.net
> Code: http://github.com/lift
> Discussion: http://groups.google.com/group/liftweb
> Stuck? Help us help you:
> https://www.assembla.com/wiki/show/liftweb/Posting_example_code
>
>
>



--
Diego Medina
Lift/Scala Developer
di...@fmpwizard.com
http://www.fmpwizard.com

Daniel Roziecki

unread,
Oct 25, 2012, 10:29:33 AM10/25/12
to lif...@googlegroups.com
I could try do this, thanks.

Daniel

2012/10/25 Diego Medina <di...@fmpwizard.com>

Daniel Roziecki

unread,
Oct 26, 2012, 3:58:13 AM10/26/12
to lif...@googlegroups.com
Problem was / is with connection's persistence. We have connection's pool at frontend. These connections should be permanent, but jetty has set default timeout for 5 min. What worse (don't know is it bug or feature) connection is alive after timeout, and frontend can send request to backend, this request is processed, but response is don't send back, and connection is closing.

Regards

Daniel
Reply all
Reply to author
Forward
0 new messages