Applications that call tibems_Open and
tibems_Close one or more times will allocate and deallocate correctly as long as the close calls match the open calls.
USING BY REFERENCE isAllowed,
|
|
|
Returns true when the client application does not wait for the message callback to return before closing a message consumer, session, or connection. Returns false if the application waits for the callback to return.
|
RETURNING tibems-Return-Value
This setting governs all client tibemsConnection objects, limiting the number of times that connection objects attempt to establish a connection to the server. The default value is 2. The minimum value is 1.
This setting governs all client tibemsConnection objects. It determines the delay time between successive attempt to establish a connection to the server. Its value is the time (in milliseconds) between connection attempts. The default value is 500. The minimum value is 250.
This setting governs all client tibemsConnection objects. It determines the maximum time (in milliseconds) the client allows to establish a connection to the server. The default value is 500.
USING BY REFERENCE isSet,
|
|
|
Returns true if the exception listener is to be called on any of the following fault-tolerant events: disconnected, each reconnect attempt, reconnected. Returns false if it is not to be called. Default is false.
|
Setting an Exception Listener in the
TIBCO Enterprise Message Service User’s Guide
USING BY REFERENCE isSet,
|
|
|
Returns true if the exception listener is to be called on a fault-tolerant switchover and false if it is not to be called. Default is false.
|
Setting an Exception Listener in the
TIBCO Enterprise Message Service User’s Guide
Chapter 13, Using Multicast, in the
TIBCO Enterprise Message Service User’s Guide
See Chapter 13, Using Multicast, in the
TIBCO Enterprise Message Service User’s Guide, for more information.
RETURNING tibems-Return-Value
This setting governs all client tibemsConnection objects limiting the number of times that they attempt to reconnect to the server after a network disconnect. The default value is 4. The minimum value is 1.
Setting Reconnection Failure Parameters in the
TIBCO Enterprise Message Service User’s Guide.
This setting governs all client tibemsConnection objects. It determines the delay time between successive attempt to establish a connection to the server. Its value is the time (in milliseconds) between connection attempts. The default value is 500. The minimum value is 250.
Setting Reconnection Failure Parameters in the
TIBCO Enterprise Message Service User’s Guide.
tibems_int tibems_GetReconnectAttemptTimeout(void);
This setting governs all client tibemsConnection objects. It determines the maximum time (in milliseconds) to client will allow to reestablish a connection to the server. The default value is 500. The minimum value is 250.
Setting Reconnection Failure Parameters in the
TIBCO Enterprise Message Service User’s Guide.
tibems_int tibems_GetSocketReceiveBufferSize(void);
When set, this value overrides the operating system’s default for the size of receive buffers associated with sockets that the client uses for connections to the server. (Some operating systems do not allow you to override the default size.)
When set, this value overrides the operating system’s default for the size of send buffers associated with sockets that the client uses for connections to the server. (Some operating systems do not allow you to override the default size.)
It is possible for a consumer to be a multicast consumer yet only receive messages over TCP. This may happen when the consumer is created on a wildcard destination that includes both unicast and multicast topics.
Applications that do not call tibems_Open will work as expected because the EMS internal global data structures are allocated when any public EMS function is called. However, the EMS data structures will not be deallocated until the application calls the
tibems_Close function or exits.
Applications that call tibems_Open and
tibems_Close one or more times will allocate and deallocate correctly as long as the close calls match the open calls.
USING BY VALUE isAllowed,
|
|
|
When true, the application will not wait for the message callbacks to return before closing a message consumer, session, or connection. When false, the application waits for the callback to return.
|
This function can be used to change the default EMS client behavior, and set whether the client application can call
tibemsMsgConsumer_Close,
tibemsSession_Close, or
tibemsConnection_Close functions from the
tibemsMsgCallback.
The default behavior is to wait for callbacks and parallel the behavior specified in the JMS specification, which the EMS client API adheres to. However, this function allows applications to override the default behavior and close EMS objects inside message callbacks.
Normally, the C client API will wait for the tibemsMsgCallback callback to return before the close functions can return to the calling application. Consequently, if these close functions are called inside the callback it causes a deadlock. If calling close functions inside the callback is allowed, then the close function will not wait for the
tibemsMsgCallback to return. This prevents the deadlock.
This setting governs all client tibemsConnection objects, limiting the number of times that connection objects attempt to establish a connection to the server.
This setting governs all client tibemsConnection objects. It determines the delay time between successive attempt to establish a connection to the server. Its value is the time (in milliseconds) between connection attempts.
This setting governs all client tibemsConnection objects. It determines the maximum time (in milliseconds) the client allows to establish a connection to the server.
tibems_bool* callExceptionListener);
USING BY VALUE callExceptionListener,
This setting determines exception behavior when the fault-tolerant client goes through phases in the failover process. If an exception listener is set on the connection, the callback is invoked when the client detects:
|
|
|
When true, the connection’s ExceptionListener catches an exception, which contains a status code indicating the state of the fault-tolerant failover: TIBEMS_SERVER_DISCONNECTED, TIBEMS_SERVER_RECONNECTING, or TIBEMS_SERVER_RECONNECTED
When false, fault-tolerant failover does not trigger an exception in the client.
|
Setting an Exception Listener in the
TIBCO Enterprise Message Service User’s Guide
tibems_bool callExceptionListener);
USING BY VALUE callExceptionListener,
|
|
|
When true, the connection’s ExceptionListener catches an exception, which contains the name of the new server.
When false, fault-tolerant failover does not trigger an exception in the client.
|
Setting an Exception Listener in the
TIBCO Enterprise Message Service User’s Guide
A connection to the multicast daemon is required when multicast is enabled and a consumer is subscribed to a multicast-enabled topic. Setting the port with this method will override the default port supplied by the server and any port specified in a connection factory for all connections in the application.
Chapter 13, Using Multicast, in the
TIBCO Enterprise Message Service User’s Guide
|
|
|
When true, multicast is enabled for the client.
When false, multicast is disabled and the client application will receive all messages over TCP.
|
tibems_SetMulticastEnabled overrides both the EMS server and factory settings that enable multicast.
multicast and
multicast_daemon_default server parameters in the
TIBCO Enterprise Message Service User’s Guide
tibemsMulticastExceptionCallback listener,
Chapter 13, Using Multicast, in the
TIBCO Enterprise Message Service User’s Guide
This setting governs all client tibemsConnection objects as they attempt to reconnect to the server after a network disconnect.
Setting Reconnection Failure Parameters in the
TIBCO Enterprise Message Service User’s Guide.
This setting governs all client tibemsConnection objects. It determines the delay time between successive attempt to establish a connection to the server. Its value is the time (in milliseconds) between connection attempts.
Setting Reconnection Failure Parameters in the
TIBCO Enterprise Message Service User’s Guide.
This setting governs all client tibemsConnection objects. It determines the maximum time (in milliseconds) to client will allow to reestablish a connection to the server.
Setting Reconnection Failure Parameters in the
TIBCO Enterprise Message Service User’s Guide.
Use this call before creating server connections. This call sets an override buffer size for new socket buffers; it does not change the size of existing socket buffers.
Use this call before creating server connections. This call sets an override buffer size for new socket buffers; it does not change the size of existing socket buffers.
USING BY REFERENCE fileName,
This call directs client tracing information to the file specified by the fileName argument. This function does not generate tracing; tracing must be enabled separately. Tracing can be enabled using the
set server client_trace command in the administration tool, or, for SSL tracing, using the
tibemsSSL_SetTrace or
tibemsSSL_SetDebugTrace function. See the
TIBCO Enterprise Message Service User’s Guide for more information about the administration tool.
To stop sending tracing information to the file and resume regular tracing to stderr or
stdout, call
tibems_SetTraceFile, passing
NULL for
fileName parameter.