• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Jeanne Boyarsky
  • Ron McLeod
Sheriffs:
  • Paul Clapham
  • Liutauras Vilda
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

Singleton MDB

 
Ranch Hand
Posts: 145
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

We have a situation that JMS messages should be processed in the same serial order as it arrives in the Queue. We are using MDB running on Weblogic 9 cluster (3 servers). Our JMS Queue is actually a foreign server (JMS Bridge) listening to a Tibco server. My question is even if we set the max count of bean in pool at 1, won�t there be possibility of 3 beans getting processed simultaneously (which opens a risk of younger message overtaking the older message).
I would like to know
1.Is there any way to make MDB singleton in cluster environment i.e. preserving the serial order in which messages appeared in Weblogic Queue.

2.Is there any way to make TIBCO fire JMS message to only one server so only one MDB will be executed?


Thanks,
Sandeep
[ September 02, 2008: Message edited by: Sandeep Ghosh ]
 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

Your admin server will receive all requests. And then forward the requests to the managed servers.
Hence, calls will not get duplicated.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic