Unexpected behavior while loading a faulty WSDL URL

Good morning,

I have a web service URL like this:

http://172.22.200.21:8080/ISMSG/ws/SmsManager?wsdl

I want to simulate the connection timeout exception by putting a faulty http port as it figures on the altered URL:
http://172.22.200.21:10040/ISMSG/ws/SmsManager?wsdl

However the result is:

NullPointerException after 86 seconds despite the SOCKET TIMEOUT param is set to 20.

As i know, the param SOCKET_TIMEOUT is different from the param CONNECTION_TIMEOUT for the HTTPClientManager used by SOAPUI.

So why i got the described behavior and how can i configure the CONNECTION_TIMEOUT in order to get the expected connection timeout exception ?

Regardless.
Abderrazzek