Multiple JMS subscriber performance in same VM ---------------------------------------------- Key: JBAS-3377 URL: http://jira.jboss.com/jira/browse/JBAS-3377 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public(Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.4.GA Reporter: floe fliep Priority: Optional Consider the following JMS publish/subscribe setup in JB AS 4.0.4GA: - one JMS topic publisher running in the AS VM - several JMS subscribers to the same topic, running on several threads in one client VM, sharing a single TopicConnection While debugging through the JBoss AS 4.0.4GA code, it seems, and as far I was able to see, that the AS sends for each message sent through the TopicPublisher.publish(msg) several identical instances of org.jboss.mq.ReceiveRequest over the network connection, i.e. as many instances as we have subscriptions on the client side. This induces considerable network overhead with larger messages any many clients. One workaround to it is to make a client-side construction where there is only subscriber consuming messages, which in its turn distributes them locally. But this feels a bit like building your own JMS. Would there be a way to improve this or is this related to constraints imposed by the JMS spec.?