• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

MDB's, JMS and scaling.

 
Neil Goldsmith
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In our design, we use a JMS queue (MQSeries) to receive work. This queue is listened to by our MDB's, who forward the work to a session bean for business rule processing all deployed in Websphere.
To scale the system, we should be able to add another replicated app server on another machine which can also process work the same way.
Now, the component that creates the work will simply forward to one queue. our MDB's will all listen to that queue.
In a Websphere environment, how will that work be distributed? Is this controllable? We want the work to spread evenly if you add a new machine, not to bog down one server.
Will we need to implement some middle component that can distribute the work maybe in a round robin fashion, least used fasion, etc, or does Websphere's work flow generator handle this for us? Is there a better way of scaling this than having all MDB's listen on one queue?
thanks
 
Thomas Paul
mister krabs
Ranch Hand
Posts: 13974
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would imagine that since WebSphere supports a multi-server environment which includes load balancing that this should not be an issue.
I am moving this to the WebSphere forum.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic