Read error: #<Errno::ENOTCONN: Transport endpoint is not connected - getpeername(2)>

[David Krmpotic]

Hi,

I'm using Faye in Ruby and after various problems I got it running quite stable except for this:

Read error: #<Errno::ENOTCONN: Transport endpoint is not connected - getpeername(2)>

I don't know exactly how Faye behaves when this happens but it doesn't seem to quit .. I just got report from one test user that the site didn't work and faye.js couldn't get loaded... and I saw this in the log.

Thank you for any hints as to what could be happening here.

David

[James Coglan]

On 28 August 2014 09:16, David Krmpotic <david.k...@gmail.com> wrote:

Hi,

I'm using Faye in Ruby and after various problems I got it running quite stable except for this:

Read error: #<Errno::ENOTCONN: Transport endpoint is not connected - getpeername(2)>

I don't know exactly how Faye behaves when this happens but it doesn't seem to quit .. I just got report from one test user that the site didn't work and faye.js couldn't get loaded... and I saw this in the log.

What are you doing to trigger this error? Can you provide a short program that demonstrates it? 

[David Krmpotic]

Yes, here - same as previous time we talked but with EM issue solved:

https://gist.github.com/davidhq/eb9d4dfb45d35aaab863

I'm sorry if you expected a much smaller example but I'm quite certain that I cannot reduce it to a minimal sample that causes this..

so far it only happened once.. so even with complete code I'm not sure how to recreate for now.

Please tell me if you can suspect something from this or should I restructure my logic again to be more robust / better designed...

thank you

david

--
You received this message because you are subscribed to a topic in the Google Groups "Faye users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/faye-users/DAWbuzKcwgM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to faye-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[James Coglan]

On 28 August 2014 13:48, David Krmpotic <david.k...@gmail.com> wrote:

Yes, here - same as previous time we talked but with EM issue solved:

https://gist.github.com/davidhq/eb9d4dfb45d35aaab863

I'm sorry if you expected a much smaller example but I'm quite certain that I cannot reduce it to a minimal sample that causes this..

so far it only happened once.. so even with complete code I'm not sure how to recreate for now.

Please tell me if you can suspect something from this or should I restructure my logic again to be more robust / better designed...

I've never seen this error myself so I'm afraid I can't guess where in your app this is coming from.