7;s not it). You have a
>> problem in your architecture of your backend. Maybe you can talk to your
>> SMSc and ask them to observe the same inbound throuput restrictions that
>> they have for outbound traffic. 25 SMS/s in, 25 SMS/s out.
>>
>> Nikos
>> - Original
one line at a time as it comes in. So
> it is both very light and fast.
>
> Advisory: For the trained professionals only!
>
> Nikos
> - Original Message - From: "seikath"
> To:
> Sent: Friday, April 02, 2010 2:40 AM
> Subject: Re: Too many dlr at
s is quite subjective, but I hope people will resist the temptation
to flame.
BR,
Nikos
- Original Message -
From: Alejandro Guerrieri
To: Gabor Maros ; users@kannel.org
Sent: Friday, April 02, 2010 12:11 AM
Subject: Re: Too many dlr at once
Hmm, I wouldn't throw an op
er than all the rest. You can even do all the db
pooling you want by batching inserts together in real time (of course it
is up to you to code this part) ;-)
Nikos
- Original Message - From: "seikath"
To:
Sent: Thursday, April 01, 2010 8:16 PM
Subject: Re: Too many dlr at once
st and lighter than all the rest. You can even do all the db
> pooling you want by batching inserts together in real time (of course it
> is up to you to code this part) ;-)
>
> Nikos
> - Original Message - From: "seikath"
> To:
> Sent: Thursday, Apri
hey have for outbound traffic. 25 SMS/s in, 25 SMS/s out.
>
>
> Nikos
> - Original Message - From: "Gabor Maros" >
> To:
> Sent: Thursday, April 01, 2010 9:22 PM
> Subject: Re: Too many dlr at once
>
>
>
>
> Hi Seikath,
>
> Dlrs are very imp
bserve the same inbound throuput restrictions that
they have for outbound traffic. 25 SMS/s in, 25 SMS/s out.
Nikos
- Original Message -
From: "Gabor Maros"
To:
Sent: Thursday, April 01, 2010 9:22 PM
Subject: Re: Too many dlr at once
Hi Seikath,
Dlrs are very important for
Hi Seikath,
Dlrs are very important for us they are in an Oracle database, and the web
application is running in a WebLogic cluster (it makes DB connectio
pooling). I can not use other infrastructure. I think opening 40k network
connection at once is not the best and effective thing (allowing so
kos
> - Original Message -
> From: "Nikos Balkanas"
> To: "Gabor Maros" ;
> Sent: Thursday, April 01, 2010 8:00 PM
> Subject: Re: Too many dlr at once
>
>
> Hi,
>
> Most people here use lighttpd for dlr web receiver. It is very fast and
> sh
up to you to code
this part) ;-)
Nikos
- Original Message -
From: "seikath"
To:
Sent: Thursday, April 01, 2010 8:16 PM
Subject: Re: Too many dlr at once
In general DLR is not so important info to be injected right away into the
database.
if you have high load of MO/DLR, cons
In general DLR is not so important info to be injected right away into the
database.
if you have high load of MO/DLR, consider db pooling and even better, drop the
http requests.
The Apache or Lighty or even ISS can handle the traffic you have mentioned with
no issues.
What I do for high load of
Why are you getting 1 dlrs/sec when you onl;y have peak 25 SMS/sec?
Something seems wrong here.
BR,
Nikos
- Original Message -
From: "Nikos Balkanas"
To: "Gabor Maros" ;
Sent: Thursday, April 01, 2010 8:00 PM
Subject: Re: Too many dlr at once
Hi,
Most peop
Hi,
Most people here use lighttpd for dlr web receiver. It is very fast and
should have no problem with this kind of traffic.
BR,
Nikos
- Original Message -
From: "Gabor Maros"
To:
Sent: Thursday, April 01, 2010 6:33 PM
Subject: Re: Too many dlr at once
Thanks Niko
Thanks Nikos,
it may help but there is another problem i haven't mentioned before. We have
a webapplication that receives dlrs from kannel. If kannel gets 10k dlr in
one sec then kannel tries to send all of them in the same sec to the app.
This behaviour kills the app (and the database behind it)
Hi,
Check if you havd /etc/hosts, and if you do you should have specified your
gateway.
Also check if named is running (Linux)
BR,
Nikos
- Original Message -
From: "Gabor Maros"
To:
Sent: Thursday, April 01, 2010 12:58 PM
Subject: Too many dlr at once
Hi,
I've got a kannel ins
15 matches
Mail list logo
