jQuery in Action, 2nd edition*
The moose likes Performance and the fly likes JMS Client - Server Design and Perfomance Query Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Performance
Bookmark "JMS Client - Server Design and Perfomance Query" Watch "JMS Client - Server Design and Perfomance Query" New topic
Author

JMS Client - Server Design and Perfomance Query

Jigs Mehta
Greenhorn

Joined: Apr 02, 2009
Posts: 6
Hi all,

I have a question on how to obtain maximum efficiency and perfomance for JMS Client - server application. I have TIBCO EMS as the JMS service provider.

I have multiple clients (separate systems) all having sending similar requests and expecting appropriate responses. My question is how should I implement the solution on server side form perfomance and efficiency point of view of the clients, server and the TIBCO EMS server. I have 10 clients.

Whether I should use a set of separate request response queues for every client or should I use a single set of request response queues and provide the clients with a different message selectors so they can fetch responses from the same queue.

The main criteria is to have minimum response time from the server but at the same time making sure that neither the server application or the TIBCO EMS server is overloaded.
This will be a real time application with quite a heavy load.

Thanks in advance!!!
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JMS Client - Server Design and Perfomance Query
 
Similar Threads
Tibco EMS server ?
MapMessage of JMS/TIBCO
GUI for Tibco EMS Administration Tool?
Authentication using an MDB towards an external JMS provider
Large messages over JMS?