policies:binding_establishment:max_binding_iterations

 

 The policy "max_binding_iterations" specifies the number of times a client can try to establish a binding before raising a TRANSIENT exception is thrown. The default is "5". Setting this to "-1" configures unlimited retries.

 

 

policies:binding_establishment:relative_expiry

 

 The policy "relative_expiry" specifies the time, in milliseconds, allowed to establish a binding.

 

 

policies:relative_request_timeout

 

The policy "relative_request_timeout" specifies the time, in milliseconds, allowed to deliver a request. Request delivery is considered complete when the last fragment of the GIOP request is sent over the wire to the target object.

 

The timeout period includes any delay in establishing a binding. This policy type is useful to a client that only needs to limit request delivery time.

 

 

policies:relative_roundtrip_timeout

 

The policy "relative_roundtrip_timeout" specifies the time, in milliseconds, allowed to deliver a request and its reply. The timeout countdown starts with the request invocation, and includes:

  • Marshalling in/inout parameters.

  • Any delay in transparently establishing a binding.

 

If the request times out before the client receives the last fragment of reply data, the request is cancelled using a GIOP CancelRequest message and all received reply data is discarded.

 

policies:relative_binding_exclusive_request_timeout

 

The policy "relative_binding_exclusive_request_timeout" specifies the time, in milliseconds, allowed to deliver a request, exclusive of binding attempts. The countdown begins immediately after a binding is obtained for the invocation.

 

 

policies:relative_binding_exclusive_roundtrip_timeout

 

The policy "relative_binding_exclusive_roundtrip_timeout" specifies the time, in milliseconds, allowed to deliver a request and receive its reply, exclusive of binding attempts.

 

 

policies:relative_connection_creation_timeout

 

The policy "relative_connection_creation_timeout" specifies the time, in milliseconds, allowed to resolve each address in an IOR, within each binding iteration. Default is 8 seconds.

 

Please note, an IOR can have several TAG_INTERNET_IOP (IIOP transport) profiles, each with one or more addresses, while each address can resolve via DNS to multiple IP addresses. Furthermore, each IOR can specify multiple transports, each with its own set of profiles.

 

This variable applies to each IP address within an IOR. Each attempt to resolve an IP address is regarded as a separate attempt to create a connection.