Newer
Older
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
`*Cannot listen at port when trying to open the listen port: <port>*`
The listen system call failed.
`*getsockname() system call failed on the server socket when trying to open the listen port: <port>*`
The getsockname system call failed.
`*getaddrinfo: <errortexr> for host <host> service <service>*`
The getaddrinfo system call failed.
`*getnameinfo() system call failed on the server socket when trying to open the listen port: <port>*`
The getnameinfo system call failed.
`*Cannot open socket when trying to open client connection: <errortext>*`
The socket system call failed.
`*Setsockopt failed when trying to open client connection: <errormessage>*`
The setsockopt system call failed.
`*Cannot bind to port when trying to open client connection: <errortext>*`
The bind system call failed.
`*Already tried <n> times, giving up when trying to open client connection: <errortext>*`
The deadlock counter exceeds the hard coded limit when trying to connect to a server in client mode. When connecting on a socket, sometimes it is unsuccessful. The next try usually solves the problem and the connection will be successfully accepted. The test port retries to connect as a workaround. The number of tries however limited to avoid hanging the test port.
Different operating systems behave in a different way. This problem is rare on Solaris, Unix and Linux systems, but much more often on Cygwin.
[[warning_messages_in_case_SSL_connections_are_used]]
== Warning Messages In Case SSL Connections Are Used
`*Warning: race condition while setting current client object pointer.*`
The current client object pointer is already set.
`*Connection from client <value> is refused*`
The connection from a client is refused in the server.
`*Connection to server is refused*`
The connection from the client is refused by the server.
`*Server did not send a session ID*`
The SSL server did not send a session ID.
`*Verification failed*`
The verification of the other side is failed. The connection will be shut down.
`*SSL object not found for client <value>*`
It should never show up.
`*SSL_Socket::receive_message_on_fd: SSL connection was interrupted by the other side*`
The TLS/SSL connection has been closed. If the protocol version is SSL 3.0 or TLS 1.0, this warning appears only if a closure alert has occurred in the protocol, i.e. if the connection has been closed cleanly. Note that in this case it does not necessarily indicate that the underlying transport has been closed.
`*Other side does not have certificate*`
The other side of the SSL connection does not have a certificate.
`*Solaris patches to provide random generation devices are not installed*`
Solaris patches to provide random generation devices are not installed. A workaround will be used to seed the PRNG.
`*Private key does not match the certificate public key*`
The private key specified for the test port does not match with the public key.
= Terminology
*Sockets:* +
The socket is a method for communication between a client program and a server program in a network. A socket is defined as "the endpoint in a connection". Sockets are created and used with a set of programming requests or "function calls" sometimes called the sockets application programming interface (API). The most common socket API is the Berkeley UNIX C language interface for sockets. Sockets can also be used for communication between processes within the same computer.
*Blocking and non-blocking sockets:* +
Using a blocking socket, some socket operations (send, receive, connect, accept) will block until the operation is finished or an error occurs. Using a non-blocking socket, these operations will never block but return with an error and set `errno` to the appropriate value.
*OpenSSL:* +
The OpenSSL Project is a collaborative effort to develop a robust, commercial-grade, full-featured, and open source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library. For more information on the OpenSSL project see <<_3, [3]>>
= Abbreviations
AS:: Abstract Socket
ASP:: Abstract Service Primitive
IPv4:: Internet Protocol version 4
IPv6:: Internet Protocol version 6
PEM:: Privacy Enhanced Mail
RTE:: Run-Time Environment
SSL:: Secure Sockets Layer
SUT:: System Under Test
TCP:: Transmission Control Protocol
TLS:: Transport Layer Security
TTCN-3:: Testing and Test Control Notation version 3
= References
[[_1]]
[1] ETSI ES 201 873-1 (2002) +
The Testing and Test Control Notation version 3. Part 1: Core Language
[[_2]]
[2] User Guide for TITAN TTCN–3 Test Executor
[[_3]]
[3] OpenSSL toolkit +
http://www.openssl.org