Win a copy of Machine Learning for Business: Using Amazon SageMaker and JupyterE this week in the Jython/Python forum
or Object Design Style Guide in the Object-Oriented programming forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
  • Knute Snortum
Sheriffs:
  • Liutauras Vilda
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Joe Ess
  • salvin francis
  • fred rosenberger

MDB's, JMS and scaling.

 
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
 
mister krabs
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.
 
Ranch Hand
Posts: 217
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
WebSphere 5.0 will support MDB, not at 4.0 level.
5.0 is available for developer on IBM website.
MQ load balancing/clustering is not specified in JMS specification. Usually it is up to the MQ provider to implement necessary features.
I believe MQSeries supports these features, but you have to configure it outside of WebSphere. It is pure MQ admin tasks.
 
I guess everyone has an angle. Fine, what do you want? Just know that you cannot have this tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!