Thank you, it solved the problem
Alexander Malysh wrote:
Hi,
try to set 'immediate-sendsms-reply = true' for the smsbox group.
Thanks,
Alex
Ady Wicaksono schrieb:
More investigation
1. Sometimes when i hit smsbox to send SMS, smsbox not response for a
minute
my thread sender is waiting for response HTTP/1.x 202 Accepted up
to a minutes
If until a minutes no responses, my thread sender will close
connection.
2. i think my thread sender is normal for not waiting forever for
response :), the question is, why smsbox sometimes
not respons for a few minutes?
3. How to reproduce unresponse smsbox :D, i need to reproduce this bug
Thank you
Ady Wicaksono wrote:
When smsbox hit by sms thread sender, sometimes, it leaves in
CLOSE_WAIT state.
Like this:
smsbox 17645 sbox 899u IPv4 1607296 TCP
localhost:6290->localhost:39644 (CLOSE_WAIT)
smsbox 17645 sbox 900u IPv4 1607298 TCP
localhost:6290->localhost:39645 (CLOSE_WAIT)
smsbox 17645 sbox 902u IPv4 1607518 TCP
localhost:6290->localhost:39696 (CLOSE_WAIT)
smsbox 17645 sbox 904u IPv4 1682991 TCP
localhost:6290->localhost:56769 (CLOSE_WAIT)
smsbox 17645 sbox 905u IPv4 1746535 TCP
localhost:6290->localhost:42577 (CLOSE_WAIT)
When CLOSE_WAIT is growing, up to the max limit of open files,
smsbox will refuse connection.
I found no such linux kernel parameters to decrease or give some
timeout capabilities for CLOSE_WAIT TCP socket.
So, is it bug of kannel or what? How to clean CLOSE_WAIT without
restart smsbox?
I use Kannel/cvs-20051226
Thank you.
