Hi Samus, Currently every subscription creates a JMS consumer proxy on the server. To make things more efficient in your case you could use a single Consumer with a selector expression that will filter for data relevant to all panels being displayed and you'd do a bit of work when you receive a message to sort out which panel(s) requires updating.
We have an enhancement request logged to optimize this in some non-durable cases. HTH, Seth ________________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of capitalsemi Sent: Monday, November 27, 2006 2:46 PM To: [email protected] Subject: [flexcoders] Multiple JMS Consumers... Efficient? I have a dashboard application which consists of a number of screens, each with a number of panels containing various charts. Currently, each of these panels contains a single consumer, all of which are listening to the same JMS topic. Each consumer's selector is set so that only messages relevant to that panel are handled (based on information in the JMS message header). My question is, does each consumer subscribe individually to the JMS topic, or does the destination configured in messaging-config.xml subscribe once to the topic and then forward messages to each of its consumers? I am trying to go with the most efficient design (minimize network traffic and load on the JMS server). If each consumer is subscribing individually to the JMS topic, I can see this being a huge bottleneck... and I will likely have to have a single consumer receiving the messages and sending events out to the rest of the app. However, if there is only a single subscription to the JMS topic, I would prefer to stick with multiple consumers and thereby keep all panels autonomous. Any help is greatly apreciated! Cheers, Samus
