[
https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496123#comment-13496123
]
Grégoire BELLON-GERVAIS commented on DIRSTUDIO-846:
---------------------------------------------------
For the first one, "Check Network Parameters", I have the same error message I
already send to you.
For the second one, "Check Authentications", I have about the same with some
add :
The authentication failed
- Cannot connect on the server: Connection timed out.
- No Connection
org.apache.directory.ldap.client.api.exception.InvalidConnectionException:
Cannot connect on the server: Connection timed out.
at
org.apache.directory.ldap.client.api.LdapNetworkConnection.connect(LdapNetworkConnection.java:576)
at
org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$1.run(DirectoryApiConnectionWrapper.java:228)
at
org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.runAndMonitor(DirectoryApiConnectionWrapper.java:1173)
at
org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.doConnect(DirectoryApiConnectionWrapper.java:263)
at
org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.connect(DirectoryApiConnectionWrapper.java:169)
at
org.apache.directory.studio.connection.core.jobs.CheckBindRunnable.run(CheckBindRunnable.java:80)
at
org.apache.directory.studio.connection.ui.RunnableContextRunner$1.run(RunnableContextRunner.java:123)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.net.ConnectException: Connection timed out.
at
org.apache.mina.core.polling.AbstractPollingIoConnector.processTimedOutSessions(AbstractPollingIoConnector.java:467)
at
org.apache.mina.core.polling.AbstractPollingIoConnector.access$800(AbstractPollingIoConnector.java:64)
at
org.apache.mina.core.polling.AbstractPollingIoConnector$Connector.run(AbstractPollingIoConnector.java:511)
at
org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
at java.lang.Thread.run(Thread.java:779)
Cannot connect on the server: Connection timed out.
java.lang.Exception: No Connection
at
org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.doBind(DirectoryApiConnectionWrapper.java:469)
at
org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.bind(DirectoryApiConnectionWrapper.java:308)
at
org.apache.directory.studio.connection.core.jobs.CheckBindRunnable.run(CheckBindRunnable.java:81)
at
org.apache.directory.studio.connection.ui.RunnableContextRunner$1.run(RunnableContextRunner.java:123)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
No Connection
> Socks proxy does not work with version 2.0.0-M3, connections still go
> directly to server without using the socks server defined
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: DIRSTUDIO-846
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-846
> Project: Directory Studio
> Issue Type: Bug
> Affects Versions: 2.0.0-M3
> Environment: Tested on Ubuntu 12.10 32bits and Redhat Enterprise 6.0
> 64 Bits.
> Reporter: Grégoire BELLON-GERVAIS
> Priority: Critical
> Fix For: 1.5.3
>
>
> This behaviour has been tested on an Ubuntu 12.10 32bits and a Redhat
> Enterprise 6.0 64 Bits.
> Same error on both.
> Under version 1.5.3, when we set proxy server to socks and put "Active
> Provider" to Manual, connections go through the defined socks.
> Under version 2.0.0-M3, when we set also proxy server to socks and put
> "Active Provider" to Manual, the behaviour is different :
> - One connection go directly to the server and not through the socks server,
> - another connection go through the socks server.
> Checked with netstat to see the connections informations.
> And of course, we can't connect to ldap server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
