You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2010/06/27 19:54:50 UTC
[jira] Commented: (WSCOMMONS-548) Ability to suspend the JMS
polling task for interested amount of time
[ https://issues.apache.org/jira/browse/WSCOMMONS-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882968#action_12882968 ]
Andreas Veithen commented on WSCOMMONS-548:
-------------------------------------------
The JMS transport has a thread pool that is grown automatically (up to some configurable limit) such that at any moment there is at least one thread ready to receive a message. The net effect of suspending these threads will therefore be that the JMS transport creates more threads. Therefore I don't understand the use case for this. I also don't understand how this could influence the behavior of the transport in a well defined way (it surely has an impact, but I'm not sure it is well defined).
> Ability to suspend the JMS polling task for interested amount of time
> ---------------------------------------------------------------------
>
> Key: WSCOMMONS-548
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-548
> Project: WS-Commons
> Issue Type: Improvement
> Components: Transport
> Reporter: Rajika Kumarasiri
> Attachments: WSCOMMONS-548.patch
>
>
> Currently the polling task of JMS transport will immediately re-try which I think we need to control over in some instance. So I have added a new parameter for the connection factory "transport.jms.TaskSuspendDuration" which can use to specify the time in millisecond that we need to suspend the current polling task. A negative or zero value will not suspend the task.
> Rajika
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.