Problems with ORBJSON and rails 1.0 under lighttpd


#1

Folks,

I’ve been using ORBJson as a high-level services link between my
javascript and my rails backend,
and now that I have upgraded to rails 1.0 I am finding that ORBJSON no
longer works for me under lighttpd,
though it still works fine under Webrick.

The symptom I am seeing is that when I start up lighttpd and then hit
the web address for it, my disk fills up
with messages being written to the lighttpd error log like this:

2006-01-16 13:46:12: (mod_fastcgi.c.1561) connect failed: 8 Connection
refused 111 0 /tmp/lighttpd/dev.socket-0
2006-01-16 13:46:12: (mod_fastcgi.c.1561) connect failed: 8 Connection
refused 111 0 /tmp/lighttpd/dev.socket-0

and it just keeps repeating/

I can’t find any other error messages, and the code works fine under
Webrick.
If I remove the services stuff, my app runs fine under the lighttpd
setup.

So it looks like those two just don’t play together.

Can anyone suggest how to analyze the problem?

Also, is ORBJSON the wrong technology to use? It seems like a great idea
to me, but there is no traffic at all on its
rubyforge site.

Thanks,

Larry Young