Concurrently using ClientRequestor.request

[thomaslo]

I just discovered if I use ClientRequestor.request concurrently I will have issue on receiving the response. This is the situation:

1) use ClientRequestor.request to send in Request A and expect Response A

2) before Response A comes back, use ClientRequestor.request (same instance in 1) to send in Request B and expect Response B

If Request A takes longer time on the server side to generate Response A then Request B, then the client thread that issues Request A will receive Request B as response. Does that mean we cannot use ClientRequestor same instance concurrently? If not then what is the properly way to use hornetQ concurrently on the client side? Do we need to use multiple ClientRequestors then? Thanks

[ataylor]

you shouldnt be using it concurrently, underneath it uses the core API, like most messaging API (JMS included) it should always be used single threaded

[thomaslo]

Andy, thanks for the response.

if that being the case, usually on client side what is the best approach to deal with concurrent request. Do I need to do a pool of session similar to connection pool?

Or can I possibly use a queue approach with single thread to dispatch request and notify response with unique request id because establishing many sessions seem to be a bit overkill

[jbertram]

You need a session per thread since sessions are single-threaded (as Andy mentioned).  Whether or not you implement that with a pool or some kind of "queue" pattern doesn't really matter from my perspective.

[clebert.suconic]

As everybody mentioned a Session represents the interaction of a thread. you can switch the context of a thread.. as long as you don't access it concurrently. (that goes to anything used within the session).