L
Lieven De Foor
Guest
Hi, Refering to this thread, the -clientConnectTimeout parameter to the CONNECT statement yields another error message than doing the CONNECT without that parameter. with: Connection timeout for host localhost port 12345 transport TCP. without: Connection failure for host localhost port 12345 transport TCP. (9407) Also notice the absence of a Progress error number in the first case. The worst part is that the first error is not caught in a catch block, nor does it set ERROR-STATUS:ERROR to true! This is alarming. This means the ON ERROR is seemingly ignored for that error, and any subsequent statements are executed even after the error occurred. Fortunately ERROR-STATUS:NUM-MESSAGES is set to 1 so this can be used as a workaround together with NO-ERROR... I would assume this is a low level error occuring, which Progress should catch and rethrow as a Progress.Lang.Error. Are there any other known cases of this behaviour, and should this be considered a bug?
Continue reading...
Continue reading...