kamyker opened this issue 5 years ago · 2 comments
On 3.1, it's working fine on old 2.2 that ibm is using by default.
Seems like timeout setter on ibm website is broken and instead of 40 sec it did 40ms.
Or not, setting any timeout also using command line makes it broken.