Re: [REPOST] [PATCH] emi2 reconnection behaviour

Andreas Fink <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
On Freitag, September 20, 2002, at 09:59  Uhr, Angel Fradejas wrote:

>
> 1) Removes "retry" smsc config directive for EMI2. It always assumes 
> reconnection, as the rest of drivers.
> 2) Adds a "reconnect-delay" directive, as SMPP and SM/ASI drivers: 
> optional time between attemps in seconds. It defaults to 10 seconds.
>  

Somehow I disageee. Some folks use EMI/UCP on dialup links so you don't 
want to have it retry all the time and open the link. "It always 
assumes reconnection" is thus not a good idea.

> The reason for this changes (apart from making all drivers 
> consistent), is that current EMI2 handling of reconnection attempts is 
> a mess.
> Let me explain why:
>  
> 1) It defaults to not retrying reconnection. That means that when you 
> start bearerbox, if a single EMI2 driver fails, the whole bearerbox 
> refuses to start. This is not acceptable for production use.
>

This is to be fixed. But this simply means it should not panic at 
startup if it fails.

>  2) When it tries a reconnection (other than first time remember), it 
> doubles the time between attempts, until it reaches a fixed value. If 
> you have retry=yes it will grow until 64 minutes (!!!) and then 
> settles on 60 minutes (too much for production use).
> Weirdly, if you have retry=no, it will also try to reconnect, but the 
> time between attemps grows only until 10 minutes.
>  

Changing the timing behaviour is an issue.

Andreas Fink
Global Networks, Inc.

------------------------------------------------------------------
Tel: +41-61-6932730  Fax: +41-61-6932729   Mobile: +41-79-2457333
Global Networks, Inc. Schwarzwaldallee 16, 4058 Basel, Switzerland
Web: http://www.global-networks.ch/      [email protected]
------------------------------------------------------------------
Member of the GSM Association
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.