The Sockets Server gives a "Protocol panic" when it finds incorrect protocol module behavior.
0 |
An unknown request completed |
1 |
Protocol completed a connect request unexpectedly |
2 |
Unused |
3 |
Protocol completed a connect with data request unexpectedly |
4 |
Protocol completed a shutdown with data request unexpectedly |
5 |
CProtocolFamilyBase::Remove() failed |
6 |
Protocol made incorrect call to the server through a MSocketNotify function |
7 |
Protocol made call to [[[ERROR: [NOKX000E] Unable to find definition for key reference 'MSocketNotify']]]NewDataL with bad |
8 |
Unused |
9 |
Protocol made call to [[[ERROR: [NOKX000E] Unable to find definition for key reference 'MSocketNotify']]]DisConnect with connectionless socket |
10 |
Server could not get expected received data from protocol |
11 |
Protocol has returned an invalid |
12 |
Protocol has not implemented CProtocolBase::Error() |
13 |
Protocol has not implemented descriptor-overload of CProtocolBase::Process() |
14 |
Protocol has not implemented |
15 |
Protocol has not implemented descriptor-overload ofCProtocolBase::Send() |
16 |
Protocol has not implemented |
17 |
Protocol has not implemented CProtocolBase::BindToL() |
18 |
Protocol has not implemented CProtocolBase::BindL() |
19 |
Protocol made call to MSocketNotify::ConnectComplete() on non-listening socket |
20 |
Protocol made call to |
21 |
When the protocol provider is incomplete. |
22 |
When the protocl has a null snap |
23 |
The panic occurs when the protocol is in the bad resolver state. |
24 |
When the protocol is misconfigured. |
25 |
When the protocol has corrupt initialization data. |
26 |
When the protocol has duplicate worker ID. |
27 |
When the protocol has a non Esock thread. |
28 |
When the protocol has a bad subsession unique id. |
29 |
When the protocol has ambiguous roles. |
30 |
When there is a bad disconnect from the listener. |