Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 320279

Summary:

CVS access fails when you have to configure a proxy connection

Product:

[Eclipse Project] Platform

Reporter:

linux387943

Component:

CVS

Assignee:

platform-cvs-inbox <platform-cvs-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

wojciech.galanciak

Version:

4.0

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

stalebug

Attachments:

Description	Flags
error message	none

Description linux387943

2010-07-19 11:23:01 EDT

Build Identifier: 20100617-1415

When you have to configure a proxy connection the CVS connections do not
work. I used the Helios version. When I used the Galileo version it works fine. 

The CVS server is on the local network. The proxy is needed for internet connections. 

Reproducible: Always

Steps to Reproduce:
1. configure a proxy connection (HTTP, HTTPS)
2. go to the cvs perspective
3. configure a new cvs server
4. error message: SOCKS proxy timed out
5. when proxy configuration is changed to direct connection it works

Comment 1 linux387943

2010-07-20 02:09:32 EDT

Created attachment 174698 [details]
error message

see attachment for complete error message

Comment 2 Wojciech Galanciak

2010-09-30 11:24:00 EDT

Could you check if there is a .log file created cause of this error and if it does, attach it to this bug?

Comment 3 Wojciech Galanciak

2010-09-30 11:25:26 EDT

.log file can be found in ../your_workspace/.metadata/ folder.

Comment 4 linux387943

2010-10-01 02:55:19 EDT

From logfile:

!SESSION 2010-10-01 08:46:34.516 -----------------------------------------------
eclipse.buildId=I20100608-0911
java.version=1.6.0_15
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments:  -product org.eclipse.epp.package.jee.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product

!ENTRY org.eclipse.core.net 1 0 2010-10-01 08:46:40.764
!MESSAGE System property http.proxyHost is not set but should be proxy.abc.com.

!ENTRY org.eclipse.core.net 1 0 2010-10-01 08:46:40.764
!MESSAGE System property http.proxyPort is not set but should be 8080.

!ENTRY org.eclipse.core.net 1 0 2010-10-01 08:46:40.764
!MESSAGE System property https.proxyHost is not set but should be proxy.abc.com.

!ENTRY org.eclipse.core.net 1 0 2010-10-01 08:46:40.764
!MESSAGE System property https.proxyPort is not set but should be 8080.

!ENTRY org.eclipse.core.net 1 0 2010-10-01 08:46:40.764
!MESSAGE System property https.proxyHost is not set but should be proxy.abc.com.

!ENTRY org.eclipse.core.net 1 0 2010-10-01 08:46:40.764
!MESSAGE System property https.proxyPort is not set but should be 8080.

!ENTRY oracle.eclipse.tools.weblogic 1 2000 2010-10-01 08:46:43.466
!MESSAGE Started WebLogic Server Monitor [test@localhost:7001, Version:10.3.2.0]

Comment 5 Eclipse Webmaster

2019-09-06 16:17:40 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 6 Eclipse Genie

2021-11-02 08:49:32 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.