Sending Direct Messages
When sending a Direct message, client applications must consider the following factors:
- When using the Solace Java RTO API, whether you want to send messages using a blocking or non-blocking mode. See Blocking and Non-blocking Network I/O.
- The number of messages to publish per send invocation. See Sending One Message at a Time or Sending Multiple Messages at a Time.
- Whether you want to send messages that require a reply from the receiver. See Publishing Messages that Request Replies.
Related Samples
For examples of how to publish and receive Direct messages, see the DirectPubSub sample for the Solace Java RTO API.
Blocking and Non-blocking Network I/O
The Solace Java RTO API can use a blocking or non‑blocking network I/O model for send operations. This is controlled by the send blocking session property. By default, this property is set to true, so that a blocking mode is used.
When the send blocking session property is set to false, a non-blocking mode is used. If the OS/network cannot send the whole message without blocking the calling thread until more buffer space is available, the client application gets a WOULD_BLOCK return code. When a WOULD_BLOCK return code is received, the message is not sent and the client application must wait for a CAN_SEND Session event, which indicates that the network is then ready for the send.
Sending One Message at a Time
To publish a single message per API call, call one of the send methods or functions listed below.
In the Solace Java RTO API, use SessionHandle.send(...)
Sending Multiple Messages at a Time
A group of Direct messages can be sent through a single API call. This allows messages to be sent in a batch or a vector. The messages to be sent are specified as an array; up to fifty messages can be sent through the call.
When batch sending messages, a Direct delivery mode should be set for all of the messages (see Delivery Mode).
When using the Solace Java RTO API, an array of messages must be passed in. Message destinations are not set through a send method; rather, they are set as a property for each message.
When a blocking mode is configured for the session through the session properties, the call blocks until all messages can be accepted by the Solace Java RTO API. If a non‑blocking mode is configured, and the API cannot accept all messages to publish, SOLCLIENT_WOULD_BLOCK is returned, and the number of messages that were accepted is returned in the in_out_howManySent, numberOfMessagesWritten, or messagesSent parameter. The application can reattempt to send the messages that were not accepted or take another action.
In the Solace Java RTO API, use SessionHandle.send(...)
Related Samples
For examples of how to publish a group of messages, see the PerfTest sample for the Solace Java RTO API.