Hi Robbie,

Thank you so much for quick response. However, we have couple of open
questions related with Qpid. If you provide us input that will be too great.
We are using "qpid-jms-client-0.40.0" and sending message to Azure Service
Bus.

1. Condition - if "jms.forceSyncSend=true" + send(Message message,
CompletionListener completionListener);
   Q- Is message will process in SYNC or ASYNC? As i am using
"jms.forceSyncSend=true", so could we get response in CompletionListener or
in same thread? 
   
   I have done testing locally with "qpid-jms-client-0.40.0" and i am
getting response in CompletionListener-onCompletion/onException. 
   
   As per Qpid documentation, "jms.forceSyncSend" should override all
asynchronous send conditions, 
   But it is not doing at this moment because i am getting response back
with CompletionListener . Is this BUG??
   

2. Condition - if "jms.forceAsyncSend=false" + Send with NO
CompletionListener,
   Q -Could you please confirm, in this scenario QPID will send message in
SYNC or ASYNC?

2. Condition - if "jms.forceSyncSend=false" + Send with NO
CompletionListener,
   Q -Could you please confirm, in this scenario QPID will send message in
SYNC or ASYNC? 


3. Can we make assumption that, If we are send message with
CompletionListener, then Qpid always send message to broker in ASYNC way or
it can be SYNC also with "jms.forceSyncSend=true"?

4. SYNCHRONOUS - What is the internal behaviour of Qpid in SYNC messaging?
Is qpid waiting for successful response back from broker or it is working
like NON blocking IO concept?

5. Is there anyway to identify to nature of SEND call, our SEND call is
ASYNC or SYNC? Proton logs?

6. Enforce ASYNC - Can you please tell us best way to enforce ASYNC?

7. Enforce SYNC - Can you please tell us best way to enforce SYNC?


Regards,
Abhishek Kumar



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to