[clebert.suconic]

What does your message has to do with this thread? you should probably open a new thread.

Don't hijack a thread into another issue... try to isolate the subjects of the threads. This thread was already answered before.

Anyway: We can't help you with spring... and the way you addressed the message here it's more a job for a consultant than t forum question. You should break down your problem until you get into a specific hornetq problem. Putting a high level problem like this in our hands will be pretty much asking free consulting...

Anyway.. even if I wanted to give you free consulting (I even tried to understand your issue)...  I don't have much information to help you there. You need to break down whatever issue you're finding into a lower level issue we can understand.

If you give us a little bit more information to a level we can understand.. we will try to help you.

[harikrishnan_pillai]

Hi,Apologize for hijacking the thread. it seems that this thread matched my  current problem i am facing with load balencing consumers(client side) across a hornetq cluster of nodes .Before explaining my problem i would like to give some context on what i am trying to do. i am working as a lead enginner on an IT  firm.We are trying to upgrade all our systems to new gen technologies. So my job is to evaluate Hornetq to be used as an enterprise wide messaging system(which may lead to buying an official support from redhat too) and move out from IBM MQ.i am trying out every possible scenarios like clustering,failover,performance etc.

As part of the evaluation  i set up hornetq (2.2.14.Final) in a clustered mode. we have two machines running hornetq standalone.i have configured it for  clustering through multicast.

I have a JMS Client(defintely configured through Spring  caching connection factory) sending messages to the hornetq cluster.The server side load balencing of messages are working fine.When messages arrive at one node its correctly balencing the messages to other node also.

I am  trying to load balance (Round robin) from client side for message sending and message consumption.

Say as an instance when two threads sending messages, first message should go  to node 1 and second should go to node 2.In the HornetQ Client Connection factory(both servers are added as a transport configuration.Static list).

The behaviour i am seeing is messages from both threads are always going to node 1 only.(defintely messages are being routed to node2 from server side).

Similary when i confgure a message listener (camel component using spring DMLC and spring caching connection  factory) ,all concurrent consumers are always attaching  to one of the nodes only.

As per the Hornetq Documentation, client  side sessions(sending or consumimg) will be load balenced to all the available hornetq nodes rather than attaching  to one node .

With Spring connection factory the behaviour is not working as expected.The whole scenario is working correctly  if we bypass Spring connection  factory and use HornetQ Connection fcatory directly.

If its a spring problem i will take up this issue with Spring support ,but i just want to under stand why different sessions created are not balenced across hornetq nodes irrespective of the framework we are using.

From hornetq documenation

With HornetQ client-side load balancing, subsequent sessions created using a single session factory can be connected to different nodes of the cluster. This allows sessions to spread smoothly across the nodes of a cluster and not be "clumped" on any particular node.

I Could not make this  work  from the sessions created  using SpringConnectionfactory and spring DMLC.

I have seen your below reply in the forum:

6. Nov 30, 2010 4:27 PM (in response to Maciej Miklas)

  Re: Round Robin Client Load Balancing not working?     

Are you talking about HornetQ Core sessions (our API) or JMS Sessions?

If you're talking about JMSSessions it's a different thing: The main Connection will be holding a session and all the JMS Sessions will be going towards the same node respected the connection at the JMSConnection.

////////////////////

I guess i am dealing  with JMsSessions.Basically what i understood from your  explanation is unless we use Sessions Created from HornetQClient directly Client side load balancing will not work.

Spring  Caching Connection factory Using a Single  Connection (mapped to actual hornetq Connection ) and all sessions are created from that Connection only.

Could you please confirm whether my understanding is correct?

Message was edited by: Hari krishnan

[clebert.suconic]

I Could not make this  work  from the sessions created  using SpringConnectionfactory and spring DMLC.

I have seen your below reply in the forum:

6. Nov 30, 2010 4:27 PM (in response to Maciej Miklas)

  Re: Round Robin Client Load Balancing not working?    

Are you talking about HornetQ Core sessions (our API) or JMS Sessions?

You saw no reply because you made the same mistake twice... once a thread is marked as answered we rarely look at it again (at least on my case).

If you (or someone) marked it as solved.. and if you ask another question in top of that, you will be hijacking a thread.. hence it's unlikely you will ge an answer.

Can you open a new thread? And when you do it.. can you post clearly the steps you're using to post your messages? I'm a bit confused in what step your message is not being load balanced.

I'm a big confused to be honest. you said the load balancing is working fine.. but then at some point I'm not sure what you're expecting. I guess it's because you are writing a long text and that's confusing me. If you make it straight to the point it will be clearer to me.

BTW: Here at HornetQ we don't do much with Spring. Since you're interested in becoming a customer, I believe it is possible to establish a trial for the support contract. Someone on the support team know a bit more of spring, and that may be a bit of a better help for you? I'm not sure about that

[clebert.suconic]

Please, notice I'm just trying to understand your issue..

and please open a new thread... lets start over

[harikrishnan_pillai]

I understood.I will be opening a new thread.