Try async requests to see how the replies arrive
From 'solClient_session_sendRequest' doc:
"
When the application needs to do a blocking request (that is, the timeout parameter is non-zero), the replyTo destination must be a topic that the application has subscribed to for Direct messages. If the replyTo destination is set to an unsubscribed topic, a call to solClient_session_sendRequest() will block until the amount of time set for the timeout parameter expires and then return SOLCLIENT_INCOMPLETE with subcode SOLCLIENT_SUBCODE_TIMEOUT.
If the timeout parameter is zero, this function returns immediately with SOLCLIENT_IN_PROGRESS upon successful buffering of the message for transmission. Any response generated by the destination client is delivered to the replyTo destination as a receive message callback with the response attribute set - solClient_msg_isReplyMsg() returns true. It is entirely within the responsibility of the application to manage asynchronous responses.
"
Try async requests to see how the replies arrive
From 'solClient_session_sendRequest' doc:
"
When the application needs to do a blocking request (that is, the timeout parameter is non-zero), the replyTo destination must be a topic that the application has subscribed to for Direct messages. If the replyTo destination is set to an unsubscribed topic, a call to solClient_session_sendRequest() will block until the amount of time set for the timeout parameter expires and then return SOLCLIENT_INCOMPLETE with subcode SOLCLIENT_SUBCODE_TIMEOUT.
If the timeout parameter is zero, this function returns immediately with SOLCLIENT_IN_PROGRESS upon successful buffering of the message for transmission. Any response generated by the destination client is delivered to the replyTo destination as a receive message callback with the response attribute set - solClient_msg_isReplyMsg() returns true. It is entirely within the responsibility of the application to manage asynchronous responses.
"