You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Grégoire BELLON-GERVAIS (JIRA)" <ji...@apache.org> on 2012/11/13 11:48:11 UTC
[jira] [Created] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Grégoire BELLON-GERVAIS created DIRSTUDIO-846:
-------------------------------------------------
Summary: 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
[jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Posted by "Grégoire BELLON-GERVAIS (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496120#comment-13496120 ]
Grégoire BELLON-GERVAIS commented on DIRSTUDIO-846:
---------------------------------------------------
So here the error message :
Error while opening connection
- Cannot connect on the server: Connection timed out.
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.OpenConnectionsRunnable.run(OpenConnectionsRunnable.java:111)
at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:109)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
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.
And the netstat informations, I change IP addresses and put fake hostname instead :
socks server is on port 1080 and server ldap is on port ldaps 636.
First connection detected to the socks server :
greg@tpbellon:~$ netstat -an |grep 1080
tcp 0 0 MY_PERSONAL_IP:52173 SOCKS_IP:1080 ESTABLISHED
Second connection detected directly to the ldap server :
greg@tpbellon:~$ netstat -an |grep 636
tcp6 0 1 MY_PERSONAL_IP:47872 LDAP_IP:636 SYN_SENT
> 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
[jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496112#comment-13496112 ]
Pierre-Arnaud Marcelot commented on DIRSTUDIO-846:
--------------------------------------------------
OK, so connections using JNDI respect the Socks proxy settings and those using the Apache Directory LDAP Client API don't, is that it?
If that's the case, this is *not* a normal behavior and we probably need to tell the JVM to use the Socks proxy settings even with the Apache Directory LDAP Client API.
I will look into it.
> 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
[jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496107#comment-13496107 ]
Pierre-Arnaud Marcelot commented on DIRSTUDIO-846:
--------------------------------------------------
Hi Grégoire,
Do the connections use the same "Network Provider" and which one is it ?
Thanks.
> 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
[jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Posted by "Grégoire BELLON-GERVAIS (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496116#comment-13496116 ]
Grégoire BELLON-GERVAIS commented on DIRSTUDIO-846:
---------------------------------------------------
Yes exactly.
The strange behaviour is while I use netstat to see the connections (and of course when provider is set to Apache Directory LDAP Client API) :
I have 2 connections :
- one to the socks server (which is correct),
- and another one on directly to the ldap server, which is not correct.
And after a moment, connection is in error.
Thanks a lot for your fast update.
> 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
[jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Posted by "Grégoire BELLON-GERVAIS (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496133#comment-13496133 ]
Grégoire BELLON-GERVAIS commented on DIRSTUDIO-846:
---------------------------------------------------
Sure, it will be a pleasure.
We have a complex network, so I could try even some exclusions, ldap, ldaps etc...
Thanks a lot.
> 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
[jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496130#comment-13496130 ]
Pierre-Arnaud Marcelot commented on DIRSTUDIO-846:
--------------------------------------------------
Ok, good to know.
Thanks for the update.
In that case, it seems we're only simply ignoring the Sock proxy settings.
Now, the big question is, why does it work for JNDI out of the box and not for the LDAP API?
I hope I can find the answer soon.
> 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
[jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496121#comment-13496121 ]
Pierre-Arnaud Marcelot commented on DIRSTUDIO-846:
--------------------------------------------------
Thanks for all the details.
I was more or less expecting a connection timeout, but that dual connection you noticed with netstat is kind of weird...
One last thing, could please try to hit the following buttons in the connections properties dialog ?
- "Check Network Parameters" in the 'Network Parameter' tab
- "Check Authentication" in the 'Authentication' tab
What are the results?
Thanks again.
> 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
[jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Posted by "Grégoire BELLON-GERVAIS (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496117#comment-13496117 ]
Pierre-Arnaud Marcelot commented on DIRSTUDIO-846:
--------------------------------------------------
Interesting...
What kind of error message do you get when connecting on that 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
[jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Posted by "Grégoire BELLON-GERVAIS (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496124#comment-13496124 ]
Grégoire BELLON-GERVAIS commented on DIRSTUDIO-846:
---------------------------------------------------
Well, maybe you could forget this double connections problem.
I have double check everything, even restart my computer to be sure.
Now when I issue the connection, I don't have anymore the connection to the socks.
Only the direct connection to the ldap server in SYN_SENT.
Sorry for this, I may have a process still running in the background.
> 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
[jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Posted by "Grégoire BELLON-GERVAIS (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496110#comment-13496110 ]
Grégoire BELLON-GERVAIS commented on DIRSTUDIO-846:
---------------------------------------------------
Hello,
for the connection provider, in 1.5.3, it seems that the default connection way is "JNDI LDAP : com.sun.jndi.ldap.LdapCtxFactory".
But in 2.0.0-M3 connection provider was set to "Apache Directory LDAP Client API" by default.
So, I changed to "JNDI (Java Naming and Directory Interface)" and now the connection works correctly and it uses the socks server.
Is it a normal behaviour ?
> 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
[jira] [Commented] (DIRSTUDIO-846) Socks proxy does not work with
version 2.0.0-M3, connections still go directly to server without using the
socks server defined
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496125#comment-13496125 ]
Pierre-Arnaud Marcelot commented on DIRSTUDIO-846:
--------------------------------------------------
Ok thanks for everything.
I'll try to investigate this.
I don't have any Socks proxy that I could use though, so I might ask you to try a specific build when I think I have found the solution, if you don't mind.
> 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