You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using an invalid host 5.135.240.218 the server side response is a timeout but the client-side time-out happens faster so the exception is not catch and thrown soon enough to get the error in UI.
At the same time, another invalid host 127.0.0.1s gives a faster response so the time-out can be reported in UI.
The case of 5.135.240.218 needs a deeper investigation.
Caused by: LDAPException: Unable to connect to server 5.135.240.218:6,389 (91) Connect Error
java.net.ConnectException: Connection timed out (Connection timed out)
at com.novell.ldap.Connection.connect(Connection.java:476)
at com.novell.ldap.Connection.connect(Connection.java:408)
at com.novell.ldap.LDAPConnection.connect(LDAPConnection.java:2163)
at org.xwiki.contrib.ldap.XWikiLDAPConnection.connect(XWikiLDAPConnection.java:245)
at org.xwiki.contrib.ldap.XWikiLDAPConnection.open(XWikiLDAPConnection.java:212)
... 216 more
Caused by: java.net.ConnectException: Connection timed out (Connection timed out)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:607)
at java.net.Socket.connect(Socket.java:556)
at java.net.Socket.<init>(Socket.java:452)
at java.net.Socket.<init>(Socket.java:229)
at com.novell.ldap.Connection.connect(Connection.java:457)
... 220 more
The text was updated successfully, but these errors were encountered:
Using an invalid host
5.135.240.218
the server side response is a timeout but the client-side time-out happens faster so the exception is not catch and thrown soon enough to get the error in UI.At the same time, another invalid host
127.0.0.1s
gives a faster response so the time-out can be reported in UI.The case of
5.135.240.218
needs a deeper investigation.The text was updated successfully, but these errors were encountered: