Hello,

I have a strange behaviour on the smsc_emi module that sometimes blocks after writing the "closing connection" on the log, I'm using gateway-1.4.3. This occurs after a miss on receiving the ACK or NACK from the SMSC after the configured timeout.
The log looks like this:
2012-01-18 12:09:06 [18043] [29] WARNING: EMI2[****]: received neither ACK nor NACK for message 19 in 120 seconds, disconnecting and reconnection
2012-01-18 12:09:06 [18043] [29] INFO: EMI2[****]: closing connection.

and it stays like that until I restart the kannel, then the log indicates:
2012-01-18 12:18:09 [18043] [29] DEBUG: EMI2[****]: clear_sent called
2012-01-18 12:18:09 [18043] [28] DEBUG: Thread 28 (gw/smsc/smsc_emi.c:emi2_listener) terminates. 2012-01-18 12:18:09 [18043] [29] DEBUG: EMI2[****]: connection has completed shutdown. 2012-01-18 12:18:09 [18043] [29] DEBUG: Thread 29 (gw/smsc/smsc_emi.c:emi2_sender) terminates. 2012-01-18 12:18:28 [12873] [29] INFO: EMI2[****]: connecting to Primary SMSC

I tried to check for the reason on the code, but unfortunately I'm not that familiar with it ... Can it be blocking on a conn_destroy call on the emi2_idleprocessing function after sending the "closing connection" string to the log?

Does anyone has any idea on how to solve this problem?

Best regards,
Paulo Correia



Reply via email to