- 08 Jun, 2012 7 commits
-
-
Ian Barber authored
-
-
Ian Barber authored
Use the hiccup mechanism to notify the socket end of the pair of the change in state, and have it shutdown that end, and shutdown the local end normally. This seems to resolve the shutdown and race condition issues.
-
Ian Barber authored
Consolidate TCP-specific common code into their own files.
-
Hiten P authored
The TCP keepalive tuning code has been moved into the newly added files; this also allows future TCP-specific code to be added into these files, without bloating the IP level code and establishes a known file structure for other IP-based transports. Remember: this is a no-op change, hence no API or functionality was changed as part of this commit.
-
Ian Barber authored
Change connection failure test to use an invalid hostname
-
Hiten P authored
- invalid hostname set to 0mq.is.the.best (naturally!) - issue happens as other valid-like non-existent hostnames were redirected by buggy Cable/ISP DNS servers
-
- 06 Jun, 2012 7 commits
-
-
Ian Barber authored
Reverted to a simpler shutdown. This seems to disconnect and reconnect the pipe properly, but there is a problem in overall shutdown when the pipe has blocked and reconnected - the session seems to get terminated() called on it only in shutdown for the original pipe, by which point it has been replaced. I am not sure at the moment why this only happens then, but this does mean this patch is broken at the moment
-
Ian Barber authored
Remove unused variable which causes build to fail with -Werror
-
Ian Barber authored
Check if SO_NOSIGPIPE is defined
-
Alessandro Ghedini authored
-
Alessandro Ghedini authored
-
Ian Barber authored
Bumped version for next release (3.3.0)
-
Pieter Hintjens authored
-
- 05 Jun, 2012 9 commits
-
-
Ian Barber authored
The previous code to block the socket from receiving on that pipe during a disconnect was vulnerable to a race condition. This code calls with the terminate functions of both ends of the pipe - I believe this should be safer. This required storing a pointer to the socket end of the pipe
-
Ian Barber authored
When detaching a pipe, as well as checking the delay on connect sockopt is set, also ensure that the protocol is not pgm or epgm as we are not implementing the functionality for multicase types
-
Ian Barber authored
Fix build on HPUX 11iv3
-
-
Pieter Hintjens authored
Fix up build on AIX7
-
Pieter Hintjens authored
Fix build on RHEL5 and SLES10
-
AJ Lewis authored
The socket length variable for getsockname and accept must be an (int *) instead of a (socklen_t *) on HPUX. Signed-off-by: AJ Lewis <aj.lewis@quantum.com>
-
AJ Lewis authored
GCC 4.1.2 on RHEL5 and SLES10 don't like not having a newline at the end of a source file, and error out if it's missing. Signed-off-by: AJ Lewis <aj.lewis@quantum.com>
-
AJ Lewis authored
Copy logic from zmq.cpp into device.cpp for getting poll.h included. Ensure that zmq.h is included *after* poll.h in both zmq.cpp and device.cpp. Signed-off-by: AJ Lewis <aj.lewis@quantum.com>
-
- 04 Jun, 2012 5 commits
-
-
Ian Barber authored
-
Ian Barber authored
Removing unnecessary outpipe values that had been used for reconnecting existing pipes - no longer needed when using a pipe term for the delay_attach situation.
-
Ian Barber authored
-
Ian Barber authored
Remove unnecessary extra test in pipe assertion - now we are terminating pipes we don't need to allow the case in which a pipe is rebound to the same sink
-
Ian Barber authored
On the advice of Martin Hurton, removed the new command type and just terminated the pipe in a reconnect situation, and notified the socket of the same. This handles the blocking properly, but at the cost of potentially losing in flight messages. However, this is a reasonable trade off given how much simpler it makes the patch.
-
- 03 Jun, 2012 7 commits
-
-
Ian Barber authored
Rebinding on reconnection to allow for the pipe blocking will set the event sink again, which will cause an assert to be triggered. I have modified that to allow for setting the same sink to be OK. I believe this should be ok - on termination, if a pipe hasn't reconnected, it would just attempt to be erased from the pipes list again, which is reasonable
-
Ian Barber authored
-
Ian Barber authored
Fix condition so that PGM and EPGM sockets always create pipes immediately, even if delay_attach_on_connect is set. This allows passing through the icanhasall flag, and is realistic given the fact those protocols should be able to connect immediately
-
Ian Barber authored
Fix a number of whitespace issues in various parts of the code, add validation to most calls on the test and take a first stab at implementing the reconnection pipe blocking. It didn't seem straightforward to use any of the existing process calls, so I have added a new command to command_t and friends called detach. This instructs the socket_base to remove the pipe from it's pipe list. The session base stores a copy of the outpipe, and will resend the bind command on reconnection. This should allow balancing again.
-
Ian Barber authored
Remove the extra outpipe handling as the session is quite capable of delaying the creation of the pipe until the connection has happened. Simply don't build the pipe, and let it do that automatically.
-
Ian Barber authored
-
Ian Barber authored
-
- 01 Jun, 2012 5 commits
-
-
-
Ian Barber authored
Issue 320 author
-
-
Douglas Young authored
Fix Win32 build.
-
Ian Barber authored
After speaking with Ben Gray and the discussion on the mailing list, this is an attempt to create a sockopt to allow connecting pipes to not immediately be available for traffic. The problem is in a PUSH to many PULL situation, where there is a connect to a PULL which is not there. This connect will immediately create a pipe (unlike bind), and traffic will be load balanced to that pipe. This means if there is a persistently unavailable end point then the traffic will queue until HWM is hit, and older messages will be lost. This patch adds a sockopt ZMQ_DELAY_ATTACH_ON_CONNECT, which if set to 1 will attempt to preempt this behavior. It does this by extending the use of the session_base to include in the outbound as well as the inbound pipe, and only associates the pipe with the socket once it receives the connected callback via a process_attach message. This works, and a test has been added to show so, but may introduce unexpected complications. The shutdown logic in this class has become marginally more awkward because of this, requiring the session to serve as the sink for both pipes if shutdown occurs with a still-connecting pipe in place. It is also possible there could be issues around flushing the messages, but as I could not directly think how to create such an issue I have not written any code with regards to that. The documentation has been updated to reflect the change, but please do check over the code and test and review.
-