[
http://jira.jboss.com/jira/browse/JBAS-1338?page=all ]
Adrian Brock closed JBAS-1338.
------------------------------
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.
Thread Pool improvements on the client
--------------------------------------
Key: JBAS-1338
URL:
http://jira.jboss.com/jira/browse/JBAS-1338
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
Reporter: Adrian Brock
The thread usage on the client needs to be improved.
The users of threads are:
1) The invocation layers for message delivery
2) The message listeners to wait for messages
These should be combinded to use a single thread pool.
There is no need for a message listener to hold a thread while it is waiting for a
message.
It can add itself to a registry which is then used by delivery to invoke the correct
listener
when a message arrives.
In fact, by spec the listeners should register themselves with the session and the
session
deliver the messages (single threadedly - is that a word? :-).
--
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