[
https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988253#comment-13988253
]
Stefan Seelmann commented on DIRSTUDIO-846:
-------------------------------------------
The settings made via the Eclipse "Network Connections" preference page just
set system properties -DsocksProxyHost and -DsocksProxyPort. Those system
properties are considered by "old" Java IO, but not by NIO. JNDI still uses old
IO, so the proxy settings are used. But Apache LDAP API uses NIO (via MINA). I
browsed the MINA API and it seems to support Socks, however I didn't find that
the LDAP API makes use of if.
> 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 (2.0.0.v20120224)
> 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 was sent by Atlassian JIRA
(v6.2#6252)
