[
http://jira.jboss.com/jira/browse/JBMESSAGING-1163?page=all ]
Abel Munoz Alcaraz updated JBMESSAGING-1163:
--------------------------------------------
Attachment: MessagingTimeoutFactory.patch
Looking at source code this is an easy implementation of this issue.
MessgingTimeoutFactory is accesed in a static way from ServerPeer, ChannelSupport and
MessagingQueue.
It is not configurable using a deployment descriptor file. If you want to do this, you
need to rewrite MessagingTimeoutFactory and change its management in ServerPeer (it
seems).
But, at the moment, this solution works until I will finish a better solution.
Set MessagingTimeoutFactory thread pool configurable
----------------------------------------------------
Key: JBMESSAGING-1163
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-1163
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.0.SP1
Environment: All environments
Reporter: Abel Munoz Alcaraz
Assigned To: Tim Fox
Attachments: MessagingTimeoutFactory.patch
It is desirable to do the limits of MessagingTimeoutFactory's thread pool
configurables: MaximumQueueSize, MaximumPoolSize, etc.
--
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