Hi guys,
I was using merb + mongrel for an api server but that had problems
with clients using persistent connections, thanks to mongrel. So, I
thought of switching to merb + thin as the combo (thin, in particular)
claims to support persistent connections using unix domain sockets.
When I run "merb -a thin", everything works fine except of course
persistent connections and the reason I think is that the command
results in merb and thin communicate through internet sockets rather
than unix domain sockets. So, I went by the suggestions I found on the
net and used following command instead -
merb -a thin -h log/thin.sock -p 4000
I see the following output on the console -
merb : worker (port 4000) ~ Starting Thin at port 4000
merb : worker (port 4000) ~ Using Thin adapter on host log/
thin.sock and port 4000.
merb : worker (port 4000) ~ Successfully bound to port 4000
However, now my client program is not even able to hit the server app;
it dies with "Connection refused" error!! Doing a "netstat -l" on the
server (I'm on Ubuntu) reveals that no process is listening on port
4000, although thin seems to be listening on a unix domain socket.
Here's the output from "netstat -l" -
Proto RefCnt Flags Type State I-
Node Path
unix 2 [ ACC ] STREAM LISTENING 14310 log/
thin.sock-4000
The client is trying to hit the server at port 4000 which is bound to
fail as that port is not being listened on. Any idea what could be
wrong? Am I missing something here?
thanks
Amit
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---
