JMSQueueListener doesn't manage Thread creation for the ActionProcessingPipeline i.e.
can be flooded with messages
------------------------------------------------------------------------------------------------------------------
Key: JBESB-270
URL:
http://jira.jboss.com/jira/browse/JBESB-270
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ESB Core
Affects Versions: 4.0 RC1
Reporter: Tom Fennelly
Assigned To: Mark Little
Fix For: 5.0
This listener receives messages from a JMS queue and spawns a new thread for the
ActionProcessingPipeline instance that is created to process the message. If you hammer
this listener with messages (e.g 20 concurrent threads continually pumping messages into
the in queue), you'll kill the process through running out of threads to process the
messages.
The listener should manage the Threads. Use of a Threadpool would probably take care of
this for you i.e. can probably get the pool to block while waiting for a free thread to be
returned to the pool.
--
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