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.
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
>
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
