[jboss-jira] [JBoss JIRA] Closed: (JBAS-3377) Multiple JMS subscriber performance in same VM

[Adrian Brock (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-3377?page=all ]

Adrian Brock closed JBAS-3377.
------------------------------

    Resolution: Deferred

Closing features that are (or will be) implemented in JBoss Messaging.
http://jira.jboss.com/jira/browse/JBMESSAGING

If anybody wants to provide a patch that implements these,
the issue can be reopened.

Duplicates of these issues will be closed
unless they provide an implementation/patch.

Patches should first be discussed in the
development forum:
http://www.jboss.com/index.html?module=bb&op=viewforum&f=153
if there isn't already a forum link attached to this issue.

> 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.?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira