error codes

User Error Codes

Valid for package version 0.2.0.
This is a list of integer error codes which may emerge in replies of the JennyNet network layer.

Code	Occurrence	Impact	Meaning
0			no error occurred
1	Connection Disconnected	serious	internal socket error during sending
2	Connection Disconnected	harmless	serialisation error, probably object size overflow
3	Connection Disconnected	serious	internal socket error during receiving
4	Connection Disconnected	harmless	de-serialisation error, probably object size overflow
5	Connection Disconnected	harmless	timeout on ALIVE signals from remote
99	Connection Disconnected	harmless	Connection lost algorithmic reference and has been closed via "finalize()".
101	File Transmission Sender	harmless	Transmission failed due to receiver inability to realise the storage destination. This may occur if the receiver's file-root-path has not been set or if there is a problem with storage accessibility or capacity.
102	File Transmission Receiver	harmless	Transmission failed due to local inability to realise the storage destination. This may occur if the local file-root-path has not been set or if there is a problem with storage accessibility or capacity.
103	File Transmission Sender	serious	Transmission failed due to missing CONFIRM signal from receiver (timeout). The cause is possibly serious as it might consist in a hanging IO operation at the receiver or some mysterious delay. It may be attempted to prevent the condition by enlarging the connection parameter value CONFIRM_TIMEOUT.
104	File Transmission Receiver	serious	Transmission failed because the opposite station reported a CONFIRM timeout on the transfer. The cause is possibly serious as it might consist in a hanging local IO operation or some mysterious delay. It may be attempted to prevent the condition by enlarging the connection parameter value CONFIRM_TIMEOUT.
105	File Transmission Sender	harmless	Transmission failed because the local user (sender) issued a transmission BREAK (interface method).
106	File Transmission Receiver	harmless	Transmission failed because the user of the opposite station (sender) issued a transmission BREAK (interface method).
107	File Transmission Sender	harmless	Transmission failed because the user of the opposite station (receiver) issued a transmission BREAK (interface method).
108	File Transmission Receiver	harmless	Transmission failed because the local user (receiver) issued a transmission BREAK (interface method).
109	File Transmission Sender	harmless	Transmission failed as the opposite station (receiver) reports a low-level transmission error (code 110).
110	File Transmission Receiver	serious	Transmission failed due to a parcel sequence, data integrity or IO-error occurring on the reception side. This may include local storage out-of-space errors.
111	File Transmission Sender	serious	Transmission failed due to a local IO-error occurring while reading the data source.
112	File Transmission Receiver	harmless	Transmission failed as the opposite station (sender) reports a low-level IO-related transmission error (code 111).
113	File Transmission Sender	harmless	Transmission failed because the connection closed while transmission was ongoing.
114	File Transmission Receiver	harmless	Transmission failed because the connection closed while transmission was ongoing.