Hello Guillaume,

Checked the implementation again. When servicemix is used as we use it
than we have for each component e.g. eip, ftp, file and so on one thread
who is polling every second and never get an exchange because of seda
but consumes cpu every second. Would you agree to say that we can avoid
this with the Long.MAX_VALUE. I tested id and it worked. So it might be
not to bad to make this configurable, doesn't it?

Cheers
Thomas

Guillaume Nodet wrote:
> Yes, but the threads are created by the SEDA flow, and each message is
> given directly to the JBI components.
> 
> On Thu, Aug 28, 2008 at 1:58 PM, Thomas Termin
> <[EMAIL PROTECTED]> wrote:
> 
>>Guillaume Nodet wrote:
>>
>>>Yes, you're right.  We may want to increase this timeout.
>>>However, when deployed in ServiceMix 3, the components do not use this
>>>code, as exchanges are given directly to the components through the
>>>MessageExchangeListener interface.  So such code is only executed in
>>>ServiceMix 4 and in other JBI containers.
>>
>>Are you sure? You know we still use servicemix 3 and we have lot of
>>threads polling.
>>
>>Cheers
>>Thomas
>>
>>
>>>On Thu, Aug 28, 2008 at 10:50 AM, Thomas Termin
>>><[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>>Hello,
>>>>
>>>>Is there a special reason, that the polling timeout in
>>>>AsyncBaseLifeCycle.pollDeliveryChannel is just a second? That sounds a
>>>>bit like busy waiting, doesn't it.
>>>>
>>>>AsyncBaseLifeCycle
>>>>
>>>>protected void pollDeliveryChannel() {
>>>>      synchronized (polling) {
>>>>          polling.set(true);
>>>>          polling.notify();
>>>>      }
>>>>      while (running.get()) {
>>>>      ........
>>>>              final MessageExchange exchange = channel.accept(1000L);
>>>>      ........
>>>>
>>>>in DeliveryChannelImpl
>>>>
>>>> public MessageExchange accept(long timeoutMS) throws MessagingException {
>>>>      .......
>>>>          MessageExchangeImpl me = queue.poll(timeoutMS,
>>>>TimeUnit.MILLISECONDS);
>>>>      .......
>>>>
>>>>Could it not be blocked for a longer time in poll? If there are no
>>>>exchanges we don't have to do anything there, right?
>>>>
>>>>Cheers,
>>>>Thomas
>>>>--
>>>>Thomas Termin
>>>>_______________________________
>>>>blue elephant systems GmbH
>>>>Wollgrasweg 49
>>>>D-70599 Stuttgart
>>>>
>>>>Tel    :  (+49) 0711 - 45 10 17 676
>>>>Fax    :  (+49) 0711 - 45 10 17 573
>>>>WWW    :  http://www.blue-elephant-systems.com
>>>>Email  :  [EMAIL PROTECTED]
>>>>
>>>>blue elephant systems GmbH
>>>>Firmensitz      : Wollgrasweg 49, D-70599 Stuttgart
>>>>Registergericht : Amtsgericht Stuttgart, HRB 24106
>>>>Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>--
>>Thomas Termin
>>_______________________________
>>blue elephant systems GmbH
>>Wollgrasweg 49
>>D-70599 Stuttgart
>>
>>Tel    :  (+49) 0711 - 45 10 17 676
>>Fax    :  (+49) 0711 - 45 10 17 573
>>WWW    :  http://www.blue-elephant-systems.com
>>Email  :  [EMAIL PROTECTED]
>>
>>blue elephant systems GmbH
>>Firmensitz      : Wollgrasweg 49, D-70599 Stuttgart
>>Registergericht : Amtsgericht Stuttgart, HRB 24106
>>Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
>>
>>
> 
> 
> 
> 


-- 
Thomas Termin
_______________________________
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart

Tel    :  (+49) 0711 - 45 10 17 676
Fax    :  (+49) 0711 - 45 10 17 573
WWW    :  http://www.blue-elephant-systems.com
Email  :  [EMAIL PROTECTED]

blue elephant systems GmbH
Firmensitz      : Wollgrasweg 49, D-70599 Stuttgart
Registergericht : Amtsgericht Stuttgart, HRB 24106
Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle

Reply via email to