send problem

[Cinar Eren]

Hello,

Although it happens rarely, i face the following situation:

_session.send(nos);

The above method call returns true but no message is sent by the framework. (i confirm this through protocol log)

What could be the cause of this? What should i check?
Could it be caused by a concurrency issue? (two different threads might be calling send methods of the same session concurrently, but doesnt the spin_lock in the write method allow these calls?)

thanks in advance.
best regards.


[Ian McKane]

Doubtful it is concurrency - the send queue has a spinlock on the write. Other threads will block momentarily until that is released so they should only return after they have attempted to send.

Ian

[Cinar Eren]

Hello ian,

Do you have any recommendation to find the root cause of this problem?

Best regards

[Mazz Barker]

The problem isn't really clear. How have you determined the message isn't sent? Let's see the logs. Try printing the message before you send it. Has the message you are trying to send encoded successfully?

Mazz

[Cinar Eren]

Hello Mazz,

I understood the problem when i did not receive any responses from the exchange for a change-price message i sent. Then i checked the protocol log of the framework and could not see that this change-price message is there. But my application log wrote that i sent that message as send() request returned true.

Also a question; although write() method has a spinlock, send() method which calls write() doesnt have it. Could this cause a synchronization problem?

best regards.