Since upgrade from SQL Anywhere 10 to 16 (build 2043) we have problems with a database that does not response anymore. All clients that are connected are freezing. A new connection in ISQL freezes after a click on the "Connect" button. This happens with a few customers now.
With request log we saw that the problem is in the command xp_startsmtp(). I created a small test stored procedure that executed only the startsmpt. I could reproduce the problem with that test sp. But a month later I am not able to reproduce the error again with the same test sp. However, the customer was hang again.
It looks that the xp_startsmtp() is causing the problem but it seems more complicated than just calling xp_startsmtp(). It looks like a spam block or something...? That the problems occurs after 'somethings' happen..? The xp_startsmtp is called from a scanner (by ODBC). But the test sp was executed from the server.
Questions: - anybody how to fix this? - how is it possible that a xp_startsmtp can hold all clients?
asked 07 Dec '15, 02:33
This could be related to a recently fixed issue with versions 16 and 17 where a smtp server could fail to respond or respond correctly. The fix was identifed as 793866 and for version 16 the change was made in build# 2298. You may find some relief if you include a specific value for the "timeout" parameter.
FWIW, here's the CR note: