Index of exceptions

Event handlers can raise this exception to cancel a group of handlers, events, and resources.

Raised by client_endpoint_connector and server_endpoint_acceptor to indicate that the passed address is not supported by the class.

Raised when the job handlers are already installed

Authentication error

An syntax error in the glob expression; the argument is the bad expression

Raised when a header field cannot be parsed.

The server sent a message which cannot be interpreted.

Some engines indicate this error when they cannot continue because the other endpoint of communication signals an error.

Raised by input methods if the internal buffer of the channel is too empty to read even one byte of data.

Raised when it is tried to get the code point of the BOM at the beginning of the string

The callback function of a multiplex_controller is invoked with this exception if the operation is cancelled.

raised if a conversion can't be done

Raised when a certain Unicode code point cannot be represented in the selected output encoding

The RPC call cannot be performed because the client has been shut down in the meantime.

Raised when channel operations are called when the channel is closed

Raised when a method of a closed channel object is called (only channel methods count).

Raised by mset_pick when no available endpoint can be found, or all available endpoints have reached their maximum load.

Raised by close_in or close_out if the channel is connected with another process, and the execution of that process fails.

an I/O error happened

raised by the 'reply' function if the connection to the original caller has been lost in the meantime.

The variable does not exist

The (dynamically typed) variable has the wrong type

Raised when a violation of the object format is detected

Raised when it is tried to move the cursor beyond the beginning of the string or beyond the end of the string.

Raised when a deadlock situation was detected.

raised if the dest_* function are applied to non-matching xdr_value

A read or write cannot be done because the descriptor is in non-blocking mode and would block.

A read or write cannot be done because the descriptor is in non-blocking mode and would block.

Raised when the queue is empty and the operation cannot be done

Raised when it is tried to access the character after the end of the string (at position n_max)

Passed back as `Error.

Lexical error

Raised when an executable file cannot be found; the argument is the search name

Returned by clients when the server enables an unsupported extension.

Something went wrong, often on socket level

These exceptions may be raised during execution by the FTP method.

The server violates the FTP specification

A timeout on the control or data connection (this is a fatal error)

An error is fatal if it is not possible to recover from it in a predictable manner.

An error on GSSAPI level

Exception raised by various functions of this library to return to the user agent an appropriate error page with the specified http-status (this exception must be caught by the connector and a default answer sent).

This host cannot be resolved

Deprecated in the scope of pipeline.

The request could not be processed because the exception condition was raised.

Raised if it is tried to modify a read-only value.

Returned by clients when something cannot be decoded.

Returned by clients when the signature sent by the server is invalid (i.e.

Returned by clients when the username does not match the requirements.

This exception can be raised by the callback function that is invoked when the server response arrives.

The server indicates a (logical) error.

This can be raised in encryption/decryption functions to prevent that a response is sent.

Raised when the hard limit of the line length is exceeded

May be raised by Uq_io.input_line_e

Raised by a number of functions when encountering a badly formed URL.

Raised when an illegal byte sequence is found

An illegal byte sequence is found at this byte position

May be raised by multiplex controller methods start_mem_reading and start_mem_writing if these methods are not supported for the kind of file descriptor

Moved to Uq_multiplex.Mem_not_supported

got EOF when some pending procedure calls were not replied or even sent

After all retransmissions, there was still no reply

Could not resolve this name - same as Uq_engines.Host_not_found

Raised by functions referring to Unix process groups when the job has not been started in its own process group.

There was no response to the request because some other request failed earlier and it was not allowed to send the request again.

No such resource, or no resource of the expected type

Raised by some functions/exceptions when a feature of the old model cannot be implemented in the new model or vice versa

Raised when the caller's thread is not a container thread

An unsolicited notification.

Raised by run when the event source adds new events to the queue but there are no event handlers to process them

raised if string position out of range

See Netcgi.Argument.Oversized.

Byte position in string

A parsing error.

Raised when the last character of the string is an incomplete multi-byte character, and it is tried to get the code point (using uchar_at).

Returned by clients when the server violates the protocol.

An error status from a proxy.

The "early" redirect is only allowed in stage 1 of HTTP processing.

The "late" redirect is only allowed in stage 3 of HTTP processing.

May be raised by event handlers to reject events

Drop reason: The response exceeded the configured maximum message size

The length of the response exceeds the configured maximum

RPC protocol error (bad data)

an exception generated by the RPC server

Raised when a string cannot be transformed

Returned by clients when the server sent an error code

Procedure calls may end with this exception when the reliability cache disables the service

It is not allowed to set the value

The variable does not exist.

The initial value of a shared exception variable

The (dynamically typed) variable has the wrong type (string/exn)

See gshutdown

Raised when error messages of the SOCKS proxy are received, or because of other SOCKS-related problems.

Some HTTP containers allow you to raise this exception.

The string contains the called commands in a readable representation.

A fatal error occurred (i.e.

A fatal error occurred (i.e.

The server requested a rehandshake (this exception is thrown in the client)

The server requested a rehandshake (this exception is thrown in the client)

The client accepted or denied a rehandshake (this exception is thrown in the server).

The client accepted or denied a rehandshake (this exception is thrown in the server).

A non-fatal error occurred.

A non-fatal error occurred.

Wrapper for exceptions that already passed the exception handler.

May be raised by event handlers to accept events while terminating themselves

Raised when the TCP connection times out.

A timeout.

Used by input_engine and output_engine to indicate timeouts

Hit the limit max_arguments

While following redirections the limit has been reached

Raised when an encapulated type is tried to be unwrapped by the wrong encapsulation module

This URL cannot be parsed after a redirection has been followed.

This exception can be raised by the callback function that is invoked when the server response arrives.

Raises if the crypto backend does not support an algorithm

The notations :class:, .symbol., =eqclass= inside ... are not supported by this implementation.

Used by the watchdog engine to indicate a timeout.

Usually a problem during packing

Format error found during unpacking a string

The message is too long and cannot be packed into a string