You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Thomas Termin (JIRA)" <ji...@apache.org> on 2008/09/09 09:11:52 UTC
[jira] Created: (SM-1563) polling timeout is to low in
AbstractBaseLifeCycle which results in busy waiting
polling timeout is to low in AbstractBaseLifeCycle which results in busy waiting
--------------------------------------------------------------------------------
Key: SM-1563
URL: https://issues.apache.org/activemq/browse/SM-1563
Project: ServiceMix
Issue Type: Bug
Components: servicemix-common
Affects Versions: 3.2.2
Reporter: Thomas Termin
Assignee: Thomas Termin
Fix For: 3.2.3, 3.3
The timeout which is used for polling the channel for exchanges is to low. What makes it worse is, that this method to get the exchange is not used in SMX3 with seda flow. So there are threads polling every second which should not happen.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1563) polling timeout is to low in
AbstractBaseLifeCycle which results in busy waiting
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang updated SM-1563:
-----------------------------
Fix Version/s: 3.3.1
3.4
(was: 3.3)
(was: 3.2.3)
> polling timeout is to low in AbstractBaseLifeCycle which results in busy waiting
> --------------------------------------------------------------------------------
>
> Key: SM-1563
> URL: https://issues.apache.org/activemq/browse/SM-1563
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-common
> Affects Versions: 3.2.2
> Reporter: Thomas Termin
> Assignee: Thomas Termin
> Fix For: 3.3.1, 3.4
>
>
> The timeout which is used for polling the channel for exchanges is to low. What makes it worse is, that this method to get the exchange is not used in SMX3 with seda flow. So there are threads polling every second which should not happen.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1563) polling timeout is to low in
AbstractBaseLifeCycle which results in busy waiting
Posted by "Thomas Termin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45590#action_45590 ]
Thomas Termin commented on SM-1563:
-----------------------------------
If container is servicemix 3 the threads are not needed and with this fix not started at all.
The timeout is still an issue. It is to low.
Author: tterm
Date: Wed Sep 10 04:46:18 2008
New Revision: 693800
URL: http://svn.apache.org/viewvc?rev=693800&view=rev
Log:
SM-1583 polling timeout is to low in AbstractBaseLifeCycle which results in busy waiting
Modified:
servicemix/components/shared-libraries/trunk/servicemix-common/src/main/java/org/apache/servicemix/common/AsyncBaseLifeCycle.java
> polling timeout is to low in AbstractBaseLifeCycle which results in busy waiting
> --------------------------------------------------------------------------------
>
> Key: SM-1563
> URL: https://issues.apache.org/activemq/browse/SM-1563
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-common
> Affects Versions: 3.2.2
> Reporter: Thomas Termin
> Assignee: Thomas Termin
> Fix For: 3.2.3, 3.3
>
>
> The timeout which is used for polling the channel for exchanges is to low. What makes it worse is, that this method to get the exchange is not used in SMX3 with seda flow. So there are threads polling every second which should not happen.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.