Index of exceptions

These conditions may be passed back to the caller of a RPC function: `Message_lost: The client was shut down before the response arrived. The reason is unrelated to the RPC call that sees `Message_lost (i.e. it is a follow-up error). The argument says whether the request message was tried to send (true) or not (false)., `Message_timeout: The maximum time for replying the RPC call has been exceeded., `Transport_timeout: The transport level (TCP level) blocks for too long. (This is a fatal error, and the client is shut down.), `Connect_timeout: The transport level (TCP level) blocks for too long while connecting to a server, or while doing the initial handshake. It is ensured that the server has never seen the RPC call. (This is a fatal error, and the client is shut down.), `Connect_error e: An error happened while connecting to the server, or while doing the initial handshake. The exception e explains the error. It is ensured that the server has never seen the RPC call. (This is a fatal error, and the client is shut down.), `Client_is_down: A call is tried with a client that is already shut down, `User_exception sv: The remote function raises a user-level exception, i.e. an exception that is declared in the Ice IDL. The sliced value sv represents the exception., `Object_does_not_exist(id,facet,op): Cannot call the function op, optionally in facet, of the remote object id because the object is unknown to the server., `Facet_does_not_exist(id,facet,op): Cannot call the function op, optionally in facet, of the remote object id because the facet is unknown to the server., `Operation_does_not_exist(id,facet,op): Cannot call the function op, optionally in facet, of the remote object id because the function is unknown to the server., `Unknown_local_exception s: While performing the remote operation the server caught an exception that is declared in the IDL as local exception (such exception cannot be marshalled at all). The string s explains the exception., `Unknown_user_exception s: While performing the remote operation the server caught an exception that is declared in the IDL but not for the operation. The string s explains the exception., `Unknown_exception s: While performing the remote operation the server caught an unknown exception. The string s explains the exception., `Error e: An error happened that is not one of the above. The exception e explains the error. (This is a fatal error, and the client is shut down.)

A DNS name cannot be resolved.

An error produced by the generated lang mapping code.

A coercion cannot be done

A Hydro limitation was hit: `UnsupportedEncodingVersion: Hydro only understands version 1.0, `UnsupportedProtocolVersion: Hydro only understands version 1.0

A value cannot be marshalled, i.e.

An error prevented the check from being done

A violation of the protocol has been detected: `MessageFormatViolation reason: The data received over the wire cannot be even split into messages. reason explains why., `CompressionNotSupported: A compressed message was received although Hydro announces that it does not support compression., `BadMessageType: XXX

The proxy is unable to fulfill the request: `NoCallableEndpointFound: After the endpoint resolution procedure no endpoint turns out to be usable. Note that also DNS failures can lead to this error., `NoEndpointIsReachable: None of the resolved endpoints is actually reachable., `NoLocatorIsReachable: No locator (i.e. IceGrid node) is actually reachable, and the resolution procedure fails because of this., `ProxyIsDown: The proxy has been shut down

An exception that has not to be caught by a exception handler built into Hydro.

This operation was called, but the actual definition is missing

A received message cannot be decoded into a value.