RepoMirrors
/
haproxy
mirror of http://git.haproxy.org/git/haproxy.git/
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
haproxy/doc/internals/stream-sock-states.fig

536 lines
21 KiB
Plaintext
Raw Normal View History

[RELEASE] Released version 2.0-dev6 Released version 2.0-dev6 with the following main changes : - BUG/MEDIUM: connection: fix multiple handshake polling issues - MINOR: connection: also stop receiving after a SOCKS4 response - MINOR: mux-h1: don't try to recv() before the connection is ready - BUG/MEDIUM: mux-h1: only check input data for the current stream, not next one - MEDIUM: mux-h1: don't use CS_FL_REOS anymore - CLEANUP: connection: remove the now unused CS_FL_REOS flag - CONTRIB: debug: add 4 missing connection/conn_stream flags - MEDIUM: stream: make a full process_stream() loop when completing I/O on exit - MINOR: server: increase the default pool-purge-delay to 5 seconds - BUILD: tools: do not use the weak attribute for trace() on obsolete linkers - BUG/MEDIUM: vars: make sure the scope is always valid when accessing vars - BUG/MEDIUM: vars: make the tcp/http unset-var() action support conditions - BUILD: task: fix a build warning when threads are disabled - CLEANUP: peers: Remove tabs characters. - CLEANUP: peers: Replace hard-coded values by macros. - BUG/MINOR: peers: Wrong stick-table update message building. - MINOR: dict: Add dictionary new data structure. - MINOR: peers: Add a LRU cache implementation for dictionaries. - MINOR: stick-table: Add "server_name" new data type. - MINOR: cfgparse: Space allocation for "server_name" stick-table data type. - MINOR: proxy: Add a "server by name" tree to proxy. - MINOR: server: Add a dictionary for server names. - MINOR: stream: Stickiness server lookup by name. - MINOR: peers: Make peers protocol support new "server_name" data type. - MINOR: stick-table: Make the CLI stick-table handler support dictionary entry data type. - REGTEST: Add a basic server by name stickiness reg test. - MINOR: peers: Add dictionary cache information to "show peers" CLI command. - MINOR: peers: Replace hard-coded for peer protocol 64-bits value encoding by macros. - MINOR: peers: Replace hard-coded values for peer protocol messaging by macros. - CLEANUP: ssl: remove unneeded defined(OPENSSL_IS_BORINGSSL) - BUILD: travis-ci improvements - MINOR: SSL: add client/server random sample fetches - BUG/MINOR: channel/htx: Don't alter channel during forward for empty HTX message - BUG/MINOR: contrib/prometheus-exporter: Add HTX data block in one time - BUG/MINOR: mux-h1: errflag must be set on H1S and not H1M during output processing - MEDIUM: mux-h1: refactor output processing - MINOR: mux-h1: Add the flag HAVE_O_CONN on h1s - MINOR: mux-h1: Add h1_eval_htx_hdrs_size() to estimate size of the HTX headers - MINOR: mux-h1: Don't count the EOM in the estimated size of headers - MEDIUM: cache/htx: Always store info about HTX blocks in the cache - MEDIUM: htx: Add the parsing of trailers of chunked messages - MINOR: htx: Don't use end-of-data blocks anymore - BUG/MINOR: mux-h1: Don't send more data than expected - BUG/MINOR: flt_trace/htx: Only apply the random forwarding on the message body. - BUG/MINOR: peers: Wrong "server_name" decoding. - BUG/MEDIUM: servers: Don't attempt to destroy idle connections if disabled. - MEDIUM: checks: Make sure we unsubscribe before calling cs_destroy(). - MEDIUM: connections: Wake the upper layer even if sending/receiving is disabled. - MEDIUM: ssl: Handle subscribe by itself. - MINOR: ssl: Make ssl_sock_handshake() static. - MINOR: connections: Add a new xprt method, remove_xprt. - MINOR: connections: Add a new xprt method, add_xprt(). - MEDIUM: connections: Introduce a handshake pseudo-XPRT. - MEDIUM: connections: Remove CONN_FL_SOCK* - BUG/MEDIUM: ssl: Don't forget to initialize ctx->send_recv and ctx->recv_wait. - BUG/MINOR: peers: Wrong server name parsing. - MINOR: server: really increase the pool-purge-delay default to 5 seconds - BUG/MINOR: stream: don't emit a send-name-header in conn error or disconnect states - MINOR: stream-int: use bit fields to match multiple stream-int states at once - MEDIUM: stream-int: remove dangerous interval checks for stream-int states - MEDIUM: stream-int: introduce a new state SI_ST_RDY - MAJOR: stream-int: switch from SI_ST_CON to SI_ST_RDY on I/O - MEDIUM: stream-int: make idle-conns switch to ST_RDY - MEDIUM: stream: re-arrange the connection setup status reporting - MINOR: stream-int: split si_update() into si_update_rx() and si_update_tx() - MINOR: stream-int: make si_sync_send() from the send code of si_update_both() - MEDIUM: stream: rearrange the events to remove the loop - MEDIUM: stream: only loop on flags relevant to the analysers - MEDIUM: stream: don't abusively loop back on changes on CF_SHUT*_NOW - BUILD: stream-int: avoid a build warning in dev mode in si_state_bit() - BUILD: peers: fix a build warning about an incorrect intiialization - BUG/MINOR: time: make sure only one thread sets global_now at boot - BUG/MEDIUM: tcp: Make sure we keep the polling consistent in tcp_probe_connect.
2019-06-07 04:12:59 +00:00
#FIG 3.2 Produced by xfig version 2.0
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
Portrait
Center
Metric
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
A4
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
100.00
Single
-2
1200 2
0 32 #8e8e8e
6 2295 1260 2430 1395
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 2363 1328 68 68 2430 1328 2295 1328
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 2363 1361 1\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 1845 2295 1980 2430
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 1913 2363 68 68 1980 2363 1845 2363
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 1913 2396 2\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 2475 2340 2610 2475
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 2543 2408 68 68 2610 2408 2475 2408
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 2543 2441 9\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 2835 2610 2970 2745
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 2903 2678 68 68 2970 2678 2835 2678
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 2903 2711 7\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 3195 2025 3330 2160
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 3263 2093 68 68 3330 2093 3195 2093
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 3263 2126 8\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 2745 2160 2880 2295
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 2813 2228 68 68 2880 2228 2745 2228
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 2813 2261 6\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 990 2700 1125 2835
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 1058 2768 68 68 1125 2768 990 2768
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 1058 2801 13\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 1305 2970 1440 3105
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 1373 3038 68 68 1440 3038 1305 3038
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 1373 3071 12\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 3105 1710 3240 1845
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 3173 1778 68 68 3240 1778 3105 1778
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 3173 1811 15\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 1260 4410 1395
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 1328 68 68 4410 1328 4275 1328
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 4343 1361 1\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 1440 4410 1575
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 1508 68 68 4410 1508 4275 1508
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 4343 1541 2\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 1620 4410 1755
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 1688 68 68 4410 1688 4275 1688
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 4343 1721 3\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 1800 4410 1935
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 1868 68 68 4410 1868 4275 1868
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 4343 1901 4\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 3240 2835 3375 2970
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 3308 2903 68 68 3375 2903 3240 2903
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 3308 2936 16\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 2835 3015 2970 3150
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 2903 3083 68 68 2970 3083 2835 3083
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 2903 3116 17\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 2295 3195 2430 3330
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 2363 3263 68 68 2430 3263 2295 3263
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 2363 3296 3\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 1440 4815 1620 4995
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 1508 4883 68 68 1575 4883 1440 4883
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 1508 4916 19\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 1800 3960 1980 4140
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 1868 4028 68 68 1935 4028 1800 4028
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 1868 4061 18\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 1980 4410 2115
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 2048 68 68 4410 2048 4275 2048
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 4343 2081 5\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 2340 4410 2475
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 2408 68 68 4410 2408 4275 2408
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 4343 2441 6\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 2520 4410 2655
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 2588 68 68 4410 2588 4275 2588
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 4343 2621 7\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 2700 4410 2835
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 2768 68 68 4410 2768 4275 2768
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 4343 2801 8\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 2880 4410 3015
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 2948 68 68 4410 2948 4275 2948
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 4343 2981 9\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 3060 4410 3195
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 3128 68 68 4410 3128 4275 3128
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 3161 10\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 3240 4410 3375
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 3308 68 68 4410 3308 4275 3308
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 3341 11\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 3420 4410 3555
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 3488 68 68 4410 3488 4275 3488
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 3521 12\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 3600 4410 3735
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 3668 68 68 4410 3668 4275 3668
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 3701 13\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 3960 4410 4095
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 4028 68 68 4410 4028 4275 4028
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 4061 15\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 4140 4410 4275
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 4208 68 68 4410 4208 4275 4208
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 4241 16\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 4320 4410 4455
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 4388 68 68 4410 4388 4275 4388
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 4421 17\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 3780 4455 3960
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 3848 68 68 4410 3848 4275 3848
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 3881 14\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 4590 4455 4770
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 4658 68 68 4410 4658 4275 4658
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 4691 18\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 4770 4455 4950
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 4838 68 68 4410 4838 4275 4838
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 4871 19\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 4950 4455 5130
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 5018 68 68 4410 5018 4275 5018
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 5051 20\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 1170 3690 1350 3870
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 1238 3758 68 68 1305 3758 1170 3758
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 1238 3791 11\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 1530 3555 1710 3735
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 1598 3623 68 68 1665 3623 1530 3623
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 1598 3656 10\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 720 4095 900 4275
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 788 4163 68 68 855 4163 720 4163
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 788 4196 14\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 855 3645 1035 3825
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 923 3713 68 68 990 3713 855 3713
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 923 3746 21\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 5130 4455 5310
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 5198 68 68 4410 5198 4275 5198
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 5231 21\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 2295 4140 2430 4275
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 2363 4208 68 68 2430 4208 2295 4208
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 60 2363 4241 4\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 2475 3870 2655 4050
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 2543 3938 68 68 2610 3938 2475 3938
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 2543 3971 22\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
6 4275 5310 4455 5490
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 4343 5378 68 68 4410 5378 4275 5378
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 18 5 0.0000 4 60 120 4343 5411 22\001
-6
6 2295 5625 2430 5760
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 2363 5693 68 68 2430 5693 2295 5693
4 1 0 50 -1 18 5 0.0000 4 60 60 2363 5726 5\001
-6
6 2295 6480 2475 6660
1 4 0 1 0 7 50 -1 -1 0.000 1 0.0000 2363 6548 68 68 2430 6548 2295 6548
4 1 0 50 -1 18 5 0.0000 4 60 120 2363 6581 20\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
-6
1 2 0 1 0 6 50 -1 20 0.000 1 0.0000 1350 4612 225 112 1125 4612 1575 4612
1 2 0 1 0 6 50 -1 20 0.000 1 0.0000 2250 1912 225 112 2025 1912 2475 1912
1 2 0 1 0 7 50 -1 20 0.000 1 0.0000 1125 3487 225 112 900 3487 1350 3487
1 2 0 1 0 7 50 -1 20 0.000 1 0.0000 2250 3712 225 112 2025 3712 2475 3712
[DOC] internal: reflect the fact that SI_ST_ASS is transient This state might appear before process_session() (eg: when the session is first initialized), but does not remain after process_session() returns.
2011-02-24 16:24:48 +00:00
1 2 0 1 0 6 50 -1 20 0.000 1 0.0000 2250 2812 225 112 2025 2812 2475 2812
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
1 2 0 1 0 7 50 -1 20 0.000 1 0.0000 3375 2362 225 112 3150 2362 3600 2362
1 2 0 1 0 7 50 -1 20 0.000 1 0.0000 2250 1012 225 112 2025 1012 2475 1012
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
1 2 0 1 0 6 50 -1 20 0.000 1 0.0000 2250 6232 225 112 2025 6232 2475 6232
1 2 0 1 0 7 50 -1 20 0.000 1 0.0000 2250 5422 225 112 2025 5422 2475 5422
1 2 0 1 0 7 50 -1 20 0.000 1 0.0000 2250 6997 225 112 2025 6997 2475 6997
1 2 0 1 0 6 50 -1 20 0.000 1 0.0000 2250 4587 225 112 2025 4587 2475 4587
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 1 0 2
1 1 1.00 60.00 120.00
2250 1125 2250 1800
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8910 5805 4500 5805
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 3
6885 5900 6930 5990 6975 5810
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 3
6885 6570 6930 6660 6975 6480
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
5310 5589 5310 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
5670 5589 5670 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
6030 5589 6030 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
6390 5589 6390 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
6750 5589 6750 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
7110 5589 7110 6921
2 1 0 2 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
4950 5589 4950 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8910 6705 4500 6705
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 1 0 2
1 1 1.00 60.00 120.00
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
2250 5535 2250 6120
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 1 0 2
1 1 1.00 60.00 120.00
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
2250 6345 2250 6885
2 2 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 5
4500 5580 8910 5580 8910 6930 4500 6930 4500 5580
2 2 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 5
4500 5580 8910 5580 8910 6930 4500 6930 4500 5580
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
8910 6030 4500 6030
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
8910 6255 4500 6255
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
8910 6480 4500 6480
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
5310 5589 5310 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
5670 5589 5670 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
6030 5589 6030 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
6390 5589 6390 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
6750 5589 6750 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
7110 5589 7110 6921
2 1 0 2 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
4950 5589 4950 6921
2 2 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 5
4500 5580 8910 5580 8910 6930 4500 6930 4500 5580
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8865 5805 4500 5805
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8865 6030 4500 6030
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8865 6255 4500 6255
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8865 6480 4500 6480
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
[BUG] stream_interface: SI_ST_CLO must have buffers SHUT An abort during a connect would go to the SI_ST_CLO state without the buffers shut. This was causing some sessions to never end if they would abort before the connect request was initiated. This bug has been introduced after 1.4-dev2. The doc has been extended to reflect that too.
2009-09-20 06:19:25 +00:00
5310 5589 5310 6921
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
[BUG] stream_interface: SI_ST_CLO must have buffers SHUT An abort during a connect would go to the SI_ST_CLO state without the buffers shut. This was causing some sessions to never end if they would abort before the connect request was initiated. This bug has been introduced after 1.4-dev2. The doc has been extended to reflect that too.
2009-09-20 06:19:25 +00:00
5670 5589 5670 6921
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
[BUG] stream_interface: SI_ST_CLO must have buffers SHUT An abort during a connect would go to the SI_ST_CLO state without the buffers shut. This was causing some sessions to never end if they would abort before the connect request was initiated. This bug has been introduced after 1.4-dev2. The doc has been extended to reflect that too.
2009-09-20 06:19:25 +00:00
6030 5589 6030 6921
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
[BUG] stream_interface: SI_ST_CLO must have buffers SHUT An abort during a connect would go to the SI_ST_CLO state without the buffers shut. This was causing some sessions to never end if they would abort before the connect request was initiated. This bug has been introduced after 1.4-dev2. The doc has been extended to reflect that too.
2009-09-20 06:19:25 +00:00
6390 5589 6390 6921
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
[BUG] stream_interface: SI_ST_CLO must have buffers SHUT An abort during a connect would go to the SI_ST_CLO state without the buffers shut. This was causing some sessions to never end if they would abort before the connect request was initiated. This bug has been introduced after 1.4-dev2. The doc has been extended to reflect that too.
2009-09-20 06:19:25 +00:00
6750 5589 6750 6921
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
[BUG] stream_interface: SI_ST_CLO must have buffers SHUT An abort during a connect would go to the SI_ST_CLO state without the buffers shut. This was causing some sessions to never end if they would abort before the connect request was initiated. This bug has been introduced after 1.4-dev2. The doc has been extended to reflect that too.
2009-09-20 06:19:25 +00:00
7110 5589 7110 6921
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
2 1 0 2 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
4950 5589 4950 6921
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
8865 6705 4500 6705
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
8865 5805 4500 5805
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8865 6030 4500 6030
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8865 6255 4500 6255
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8865 6480 4500 6480
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
5310 5589 5310 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
5670 5589 5670 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
6030 5589 6030 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
6390 5589 6390 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
6750 5589 6750 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
7110 5589 7110 6921
[BUG] stream_interface: SI_ST_CLO must have buffers SHUT An abort during a connect would go to the SI_ST_CLO state without the buffers shut. This was causing some sessions to never end if they would abort before the connect request was initiated. This bug has been introduced after 1.4-dev2. The doc has been extended to reflect that too.
2009-09-20 06:19:25 +00:00
2 1 0 2 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
4950 5589 4950 6921
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8865 6705 4500 6705
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 3
7605 5890 7650 5980 7695 5800
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 3
7605 6570 7650 6660 7695 6480
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
7470 5589 7470 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 3
7965 5890 8010 5980 8055 5800
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 3
7965 6570 8010 6660 8055 6480
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
7830 5589 7830 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 3
8325 6570 8370 6660 8415 6480
[BUG] stream_interface: SI_ST_CLO must have buffers SHUT An abort during a connect would go to the SI_ST_CLO state without the buffers shut. This was causing some sessions to never end if they would abort before the connect request was initiated. This bug has been introduced after 1.4-dev2. The doc has been extended to reflect that too.
2009-09-20 06:19:25 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8190 5589 8190 6921
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
8550 5589 8550 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8190 5589 8190 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8550 5589 8550 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8190 5589 8190 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8550 5589 8550 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8190 5589 8190 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
8550 5589 8550 6921
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 1
4500 5805
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 1
4500 6030
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 1
4500 6255
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 1
4500 6480
2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 1
4500 6705
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 4
1 1 1.00 60.00 120.00
2250 2700 2475 2475 2475 2250 2250 2025
0.000 1.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 3
1 1 1.00 60.00 120.00
3375 2250 2925 2025 2475 1935
0.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 3
1 1 1.00 60.00 120.00
3375 2475 3375 2700 2475 2835
0.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 4
1 1 1.00 60.00 120.00
3420 2475 3420 4320 3150 5850 2475 6165
0.000 1.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 3
1 1 1.00 60.00 120.00
1125 3375 1125 2925 2025 2790
0.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 3
1 1 1.00 60.00 120.00
1125 3375 1125 2250 2025 1935
0.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 6
1 1 1.00 60.00 120.00
2475 1890 3825 1800 3825 2520 3825 4500 3150 6075 2475 6210
0.000 1.000 1.000 1.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 4
1 1 1.00 60.00 120.00
2250 2025 2025 2250 2025 2475 2250 2700
0.000 1.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 2
1 1 1.00 60.00 120.00
2250 3825 2250 4500
0.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 3
1 1 1.00 60.00 120.00
2475 1980 2880 2115 3150 2340
0.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 2
1 1 1.00 60.00 120.00
2250 2925 2250 3600
0.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 4
1 1 1.00 60.00 120.00
2205 3825 2070 4140 1622 4221 1440 4500
0.000 1.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 4
1 1 1.00 60.00 120.00
1350 4725 1350 4950 1485 5760 2025 6165
0.000 1.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 7
1 1 1.00 60.00 120.00
1125 4590 720 4455 675 4050 675 3600 675 2250 1350 1800
2025 1935
0.000 1.000 1.000 1.000 1.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 3
1 1 1.00 60.00 120.00
1260 4500 1125 4320 1125 3600
0.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 4
1 1 1.00 60.00 120.00
1350 4500 1440 3645 1575 3330 2070 2880
0.000 1.000 1.000 0.000
3 0 0 1 32 7 51 -1 -1 0.000 0 1 0 5
1 1 1.00 60.00 120.00
1035 3600 990 4365 990 5040 1395 5895 2025 6210
0.000 1.000 1.000 1.000 0.000
3 0 0 1 32 7 51 -1 -1 0.000 0 1 0 5
1 1 1.00 60.00 120.00
2340 3825 2385 4005 2925 4275 2655 4815 2295 5310
0.000 1.000 1.000 1.000 0.000
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 4
1 1 1.00 60.00 120.00
2475 2835 3150 3375 3150 5625 2475 6120
0.000 1.000 1.000 0.000
3 0 0 1 0 7 50 -1 -1 0.000 0 1 0 2
1 1 1.00 60.00 120.00
2250 4725 2250 5310
0.000 0.000
4 0 0 50 -1 14 6 0.0000 4 105 2880 4500 1710 ASS-CON: ssui(): connect_server() == SN_ERR_NONE\001
4 0 0 50 -1 14 6 0.0000 4 90 540 4500 1350 INI-REQ: \001
4 0 0 50 -1 14 6 0.0000 4 120 3720 4500 1530 REQ-ASS: prepare_conn_request(): srv_redispatch_connect() == 0\001
4 0 4 50 -1 14 10 0.0000 4 105 105 2475 2700 4\001
4 0 4 50 -1 14 10 0.0000 4 105 105 1620 4500 6\001
4 0 0 50 -1 14 6 0.0000 4 120 3360 4500 1890 CON-EST: sess_update_st_con_tcp(): !timeout && !conn_err\001
4 0 0 50 -1 14 6 0.0000 4 105 2460 4500 3510 TAR-ASS: ssui(): SI_FL_EXP && SN_ASSIGNED\001
4 0 0 50 -1 14 6 0.0000 4 105 3420 4500 2970 ASS-REQ: connect_server: conn_retries == 0 && PR_O_REDISP\001
4 0 0 50 -1 14 6 0.0000 4 120 2460 4500 2610 QUE-REQ: ssui(): !pend_pos && SN_ASSIGNED\001
4 0 0 50 -1 14 6 0.0000 4 120 2520 4500 2790 QUE-REQ: ssui(): !pend_pos && !SN_ASSIGNED\001
4 0 0 50 -1 14 6 0.0000 4 120 3300 4500 4230 QUE-CLO: ssui(): pend_pos && (SI_FL_EXP || req_aborted)\001
4 0 0 50 -1 14 6 0.0000 4 105 2520 4500 3690 TAR-REQ: ssui(): SI_FL_EXP && !SN_ASSIGNED\001
4 0 0 50 -1 14 6 0.0000 4 120 3960 4500 4545 ASS-CLO: PR_O_REDISP && SN_REDIRECTABLE && perform_http_redirect()\001
4 0 0 50 -1 14 6 0.0000 4 120 4440 4500 2430 REQ-QUE: prepare_conn_request(): srv_redispatch_connect() != 0 (SI_ST_QUE)\001
4 0 0 50 -1 14 6 0.0000 4 120 4200 4500 4050 REQ-CLO: prepare_conn_request(): srv_redispatch_connect() != 0 (error)\001
4 0 0 50 -1 14 6 0.0000 4 105 4320 4500 4410 ASS-CLO: ssui(): connect_server() == SN_ERR_INTERNAL || conn_retries < 0\001
4 0 0 50 -1 14 6 0.0000 4 120 3120 4500 4680 CON-CER: sess_update_st_con_tcp(): timeout/SI_FL_ERR\001
4 0 0 50 -1 14 6 0.0000 4 120 3600 4500 4860 CER-CLO: sess_update_st_cer(): (ERR/EXP) && conn_retries < 0\001
4 0 0 50 -1 14 6 0.0000 4 120 4200 4500 3870 CER-REQ: sess_update_st_cer(): timeout && !conn_retries && PR_O_REDISP\001
4 0 0 50 -1 14 6 0.0000 4 120 3600 4500 3330 CER-TAR: sess_update_st_cer(): conn_err && conn_retries >= 0\001
4 0 0 50 -1 14 6 0.0000 4 120 4620 4500 3150 CER-ASS: sess_update_st_cer(): timeout && (conn_retries >= 0 || !PR_O_REDISP)\001
4 0 4 50 -1 14 10 0.0000 4 105 105 1305 3375 3\001
4 0 4 50 -1 14 10 0.0000 4 105 105 2430 3600 5\001
4 0 4 50 -1 14 10 0.0000 4 105 105 3555 2250 2\001
4 0 4 50 -1 14 10 0.0000 4 105 105 2430 1800 1\001
4 0 4 50 -1 14 10 0.0000 4 105 105 2430 900 0\001
4 0 0 50 -1 14 6 0.0000 4 105 3000 4500 2070 EST-DIS: stream_sock_read/write/shutr/shutw: close\001
4 0 0 50 -1 14 6 0.0000 4 120 1980 4500 2250 EST-DIS: process_session(): error\001
4 0 0 50 -1 14 6 0.0000 4 120 2100 4500 5040 DIS-CLO: process_session(): cleanup\001
4 1 0 50 -1 14 10 0.0000 4 105 315 1350 4680 CER\001
4 1 0 50 -1 14 10 0.0000 4 135 315 2250 1980 REQ\001
4 1 0 50 -1 14 10 0.0000 4 105 315 1125 3555 TAR\001
4 1 0 50 -1 14 10 0.0000 4 105 315 2250 2880 ASS\001
4 1 0 50 -1 14 10 0.0000 4 135 315 3375 2430 QUE\001
4 1 0 50 -1 14 10 0.0000 4 105 315 2250 3780 CON\001
4 1 0 50 -1 14 10 0.0000 4 105 315 2250 1080 INI\001
4 0 0 50 -1 14 6 0.0000 4 120 2820 4500 5220 TAR-CLO: sess_update_stream_int(): client abort\001
4 0 0 50 -1 14 6 0.0000 4 120 2820 4500 5400 CON-DIS: sess_update_st_con_tcp(): client abort\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
4 1 0 50 -1 14 8 0.0000 4 15 75 5130 5985 -\001
4 1 0 50 -1 14 8 0.0000 4 15 75 5490 5985 -\001
4 1 0 50 -1 14 8 0.0000 4 15 75 5850 5985 -\001
4 1 0 50 -1 14 8 0.0000 4 15 75 6210 5985 -\001
4 1 0 50 -1 14 8 0.0000 4 15 75 6570 5985 -\001
4 1 0 50 -1 14 8 0.0000 4 15 75 7290 5985 -\001
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 16 7 0.0000 4 105 120 4725 5985 fd\001
4 1 0 50 -1 14 8 0.0000 4 90 225 5130 5760 INI\001
4 1 0 50 -1 16 7 0.0000 4 105 270 4725 5760 state\001
4 1 0 50 -1 14 8 0.0000 4 120 225 5490 5760 REQ\001
4 1 0 50 -1 14 8 0.0000 4 120 225 5850 5760 QUE\001
4 1 0 50 -1 14 8 0.0000 4 90 225 6210 5760 TAR\001
4 1 0 50 -1 14 8 0.0000 4 90 225 6570 5760 ASS\001
4 1 0 50 -1 14 8 0.0000 4 90 225 6930 5760 CON\001
4 1 0 50 -1 14 8 0.0000 4 90 225 7290 5760 CER\001
4 1 0 50 -1 14 8 0.0000 4 90 75 5850 6210 0\001
4 1 0 50 -1 14 8 0.0000 4 90 75 5130 6210 0\001
4 1 0 50 -1 16 7 0.0000 4 90 270 4725 6210 ERR\001
4 1 0 50 -1 16 7 0.0000 4 90 270 4725 6435 EXP\001
4 1 0 50 -1 14 8 0.0000 4 90 75 5490 6210 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 6210 6210 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 6570 6210 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 6570 6435 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 5490 6435 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 5130 6435 0\001
4 1 0 50 -1 14 8 0.0000 4 90 75 5850 6435 0\001
4 1 0 50 -1 14 8 0.0000 4 90 75 6210 6435 0\001
4 1 0 50 -1 14 8 0.0000 4 90 75 7290 6435 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 6930 6435 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 7290 6210 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 6930 6210 X\001
4 1 0 50 -1 16 7 0.0000 4 75 240 4725 6660 sess\001
[MEDIUM] stream_interface: added a DISconnected state between CON/EST and CLO There were rare situations where it was not easy to detect that a failed session attempt had occurred and needed some server cleanup. In particular, client aborts sometimes lead to session leaks on the server side. A new state "SI_ST_DIS" (disconnected) has been introduced for this. When a session has been closed at a stream interface but the server cleanup has not occurred, this state is entered instead of CLO. The cleanup is then performed there and the state goes to CLO. A new diagram has been added to show possible stream_interface state transitions that can occur in a stream-sock. It makes debugging easier.
2008-11-23 16:23:07 +00:00
4 1 0 50 -1 14 8 0.0000 4 15 75 5130 6660 -\001
4 1 0 50 -1 14 8 0.0000 4 15 75 5490 6660 -\001
4 1 0 50 -1 14 8 0.0000 4 15 75 5850 6660 -\001
4 1 0 50 -1 14 8 0.0000 4 15 75 6210 6660 -\001
4 1 0 50 -1 14 8 0.0000 4 15 75 6570 6660 -\001
4 1 0 50 -1 14 8 0.0000 4 15 75 7290 6660 -\001
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 0 0 50 -1 16 6 0.0000 4 120 5970 675 7335 Note: states painted yellow above are transient ; process_session() will never leave a stream interface in any of those upon return.\001
4 1 0 50 -1 16 7 0.0000 4 90 330 4725 6840 SHUT\001
[BUG] stream_interface: SI_ST_CLO must have buffers SHUT An abort during a connect would go to the SI_ST_CLO state without the buffers shut. This was causing some sessions to never end if they would abort before the connect request was initiated. This bug has been introduced after 1.4-dev2. The doc has been extended to reflect that too.
2009-09-20 06:19:25 +00:00
4 1 0 50 -1 14 8 0.0000 4 15 75 7290 6840 -\001
MEDIUM: stream-int: introduce a new state SI_ST_RDY The main reason for all the trouble we're facing with stream interface error or timeout reports during the connection phase is that we currently can't make the difference between a connection attempt and a validated connection attempt. It is problematic because we tend to switch early to SI_ST_EST but can't always do what we want in this state since it's supposed to be set when we don't need to visit sess_establish() again. This patch introduces a new state betwen SI_ST_CON and SI_ST_EST, which is SI_ST_RDY. It indicates that we've verified that the connection is ready. It's a transient state, like SI_ST_DIS, that cannot persist when leaving process_stream(). For now it is not set, only verified in various tests where SI_ST_CON was used or SI_ST_EST depending on the cases. The stream-int state diagram was minimally updated to reflect the new state, though it is largely obsolete and would need to be seriously updated.
2019-06-05 12:34:03 +00:00
4 1 0 50 -1 14 8 0.0000 4 90 75 6930 6840 0\001
4 1 0 50 -1 14 8 0.0000 4 90 75 6570 6840 0\001
4 1 0 50 -1 14 8 0.0000 4 90 75 6210 6840 0\001
4 1 0 50 -1 14 8 0.0000 4 90 75 5850 6840 0\001
4 1 0 50 -1 14 8 0.0000 4 90 75 5490 6840 0\001
4 1 0 50 -1 14 8 0.0000 4 90 75 5130 6840 0\001
4 1 0 50 -1 14 10 0.0000 4 105 315 2250 6300 DIS\001
4 1 0 50 -1 14 10 0.0000 4 105 315 2250 5490 EST\001
4 1 0 50 -1 14 10 0.0000 4 105 315 2250 7065 CLO\001
4 1 0 50 -1 14 10 0.0000 4 105 315 2250 4635 RDY\001
4 0 4 50 -1 14 10 0.0000 4 105 105 2430 4455 7\001
4 0 4 50 -1 14 10 0.0000 4 105 105 2430 5310 8\001
4 0 4 50 -1 14 10 0.0000 4 105 105 2385 6120 9\001
4 0 4 50 -1 14 10 0.0000 4 105 210 2385 6840 10\001
4 1 0 50 -1 14 8 0.0000 4 90 75 7650 6210 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 7650 6435 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 7650 6840 0\001
4 1 0 50 -1 14 8 0.0000 4 90 225 8010 5760 EST\001
4 1 0 50 -1 14 8 0.0000 4 90 75 8010 6210 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 8010 6435 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 8010 6840 0\001
4 1 0 50 -1 14 8 0.0000 4 15 75 8370 5985 -\001
4 1 0 50 -1 14 8 0.0000 4 90 75 8370 6210 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 8370 6435 X\001
4 1 0 50 -1 14 8 0.0000 4 90 225 8730 5760 CLO\001
4 1 0 50 -1 14 8 0.0000 4 90 225 8370 5760 DIS\001
4 1 0 50 -1 14 8 0.0000 4 15 75 8730 5985 -\001
4 1 0 50 -1 14 8 0.0000 4 90 75 8730 6210 X\001
4 1 0 50 -1 14 8 0.0000 4 90 75 8730 6435 X\001
4 1 0 50 -1 14 8 0.0000 4 15 75 8730 6660 -\001
4 1 0 50 -1 14 8 0.0000 4 90 75 8370 6840 1\001
4 1 0 50 -1 14 8 0.0000 4 90 75 8730 6840 1\001
4 1 0 50 -1 14 8 0.0000 4 90 225 7650 5760 RDY\001