[
https://issues.apache.org/jira/browse/WSCOMMONS-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894296#action_12894296
]
Hiranya Jayathilaka commented on WSCOMMONS-548:
-----------------------------------------------
> If the setting is only effective with a thread pool size of 1, then this
> should be enforced.
IMV this parameter can be used to "slow down" the listener even with more than
one thread. Being able to enforce an interval between two successive
invocations of a worker is a useful feature IMO.
> There is no documentation (neither code nor user documentation) that clearly
> explains the purpose of this setting.
That's true. We need to update the documentation. I believe Rajika will be more
than happy to provide another patch with some documentation :)
> It doesn't handle InterruptedException correctly
Is this really needed? What can possibly interrupt a sleeping listener task? If
it is the thread pool shutdown event, then I guess we can safely ignore that.
> 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.
