- 30 Apr, 2010 13 commits
-
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2055 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2054 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2053 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2052 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
If it is still identified, the node would still be referenced in node manager although having been asked for removal. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2051 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2050 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
- Don't trash a node to recreate it right after (it was the case when a node was known by address only). - Check node type consistency between: - parameters and node found - node known by type and node known by UUID - Log actions before doing them, consistently - Log found node in addition to loop variables - Don't call remove when an unknown node is notified as down, and add a log for this case git-svn-id: https://svn.erp5.org/repos/neo/trunk@2049 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2048 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2047 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2046 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2045 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2044 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2043 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
- 28 Apr, 2010 9 commits
-
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2042 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2041 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2040 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2039 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2038 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2037 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
This simplifies code (and I should have done it this way from the beginning). Keep the lock check wrapper in MT subclass as it should have been added in r2025 anyway. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2036 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
When a handler sends a request, always queue the response for handling within the same handler, possibly delaying further a pending handler switch. This is for example required to properly complete identification between master nodes, as the connecting master node might exit election phase before receiving peer's AnswerPrimary when peer happens to be the primary. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2035 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2034 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
- 27 Apr, 2010 3 commits
-
-
Vincent Pelletier authored
If a first packet is sent and its answer received in time, then a second packet is sent after more than PING_DELAY seconds, a ping will be emitted right after that second packet, because _ping_time was still set. This change resets it when there is no pending requests. Also, as required to have a consistent view of _handlers, check that lock is properly held in the MT variant of the class. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2033 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2032 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
If this check fails, hard and soft checks will produce different results. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2031 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
- 26 Apr, 2010 10 commits
-
-
Vincent Pelletier authored
conn.getUUID() will always return None on a not-identified-yet node, so the test was always false when a was given. Also, test app.primary_master_node for None instead of primary_uuid, as the case where an unknown primary UUID is received must be handled. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2030 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
There is no need to make a special case in waitStoreResponses if it becomes equivalent to just calling waitResponses. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2029 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
This prevents from having an endless wait on "get" if the last connection from which we were expecting answers got interrupted. Note that this method will not raise any error related to this. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2028 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2027 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
Also, only check if connector is opened when needed, and use new "isClosed" method on connection. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2026 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2025 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
Those events are not purged at disconnection, ignore them here. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2024 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Grégory Wisniewski authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2023 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
"was_connected" actually meant "was_not_connected". To avoid using a negation in variable name, fix its use and values it's set to. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2022 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
Such node might have died between connection establishment and answering identification message, possibly causing ECONNRESET. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2021 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
- 23 Apr, 2010 5 commits
-
-
Vincent Pelletier authored
Cleanup actions are only appropriate if such exception happens in receive/ send, so it should not be applied to other possible sources of exceptions. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2020 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
Any exception triggered by low-level code should cause a log and connection closure before being propagated. git-svn-id: https://svn.erp5.org/repos/neo/trunk@2019 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
- dump() values - include oid git-svn-id: https://svn.erp5.org/repos/neo/trunk@2018 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2017 71dcc9de-d417-0410-9af5-da40c76e7ee4
-
Vincent Pelletier authored
git-svn-id: https://svn.erp5.org/repos/neo/trunk@2016 71dcc9de-d417-0410-9af5-da40c76e7ee4
-