This is the expected behavior of TCP/IP. When no data is sent over the wire, TCP can not detect the connection is broken after the IP is changed.
The only option is set SO_TIMEOUT on the connection to beanstalkd. Usually, you can set it larger than the timeout value of reserve operation, so the connection is not timed out prematurely. best regards, 韩竹(Zhu Han) 坚果云 <https://jianguoyun.com/>, 最简捷易用的云存储 无限空间, 文件同步, 备份和分享! On Sat, Jul 14, 2012 at 10:53 AM, Andre Ruiz <[email protected]> wrote: > > I have temporarily solved this problem making a vpn between the client and > the server, so that the IPs of each end of the connection never change, > even if the dynamic ip changes and the vpn reconnect. > > But I still would be interested in knowing if this is an expected > behaviour of the protocol. > > Thanks, > > Andre > > -- > You received this message because you are subscribed to the Google Groups > "beanstalk-talk" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/beanstalk-talk/-/no6kRRwdbZ8J. > > 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/beanstalk-talk?hl=en. > -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" 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/beanstalk-talk?hl=en.
