Jump to: navigation, search

Difference between revisions of "Equinox/p2/TransportDebugging"

< Equinox‎ | p2
(add retrying property)
 
(3 intermediate revisions by 3 users not shown)
Line 9: Line 9:
 
Timeout controls for JRE-http based transport. The JRE-http transport is automatically used when we are connecting to an NTLM proxy.
 
Timeout controls for JRE-http based transport. The JRE-http transport is automatically used when we are connecting to an NTLM proxy.
  
 +
- org.eclipse.ecf.provider.filetransfer.retrieve.connectTimeout=15000
 
  - org.eclipse.ecf.provider.filetransfer.retrieve.readTimeout=1000
 
  - org.eclipse.ecf.provider.filetransfer.retrieve.readTimeout=1000
 
  - org.eclipse.ecf.provider.filetransfer.retrieve.retryAttempts=20
 
  - org.eclipse.ecf.provider.filetransfer.retrieve.retryAttempts=20
 
  - org.eclipse.ecf.provider.filetransfer.retrieve.closeTimeout=1000
 
  - org.eclipse.ecf.provider.filetransfer.retrieve.closeTimeout=1000
 +
- org.eclipse.ecf.provider.filetransfer.browse.connectTimeout=3000
 +
- org.eclipse.ecf.provider.filetransfer.browse.readTimeout=1000
  
 
Timeout controls for Httpclient based transport. This is what is used in the eclipse SDK and various Eclipse packages by default.  
 
Timeout controls for Httpclient based transport. This is what is used in the eclipse SDK and various Eclipse packages by default.  
  
  - org.eclipse.ecf.provider.filetransfer.httpclient.browse.connectTimeout
+
  - org.eclipse.ecf.provider.filetransfer.httpclient.browse.connectTimeout=120000 (HEAD)
  - org.eclipse.ecf.provider.filetransfer.httpclient.retrieve.connectTimeout
+
  - org.eclipse.ecf.provider.filetransfer.httpclient.retrieve.connectTimeout=120000 (GET)
  - org.eclipse.ecf.provider.filetransfer.httpclient.retrieve.readTimeout
+
- org.eclipse.ecf.provider.filetransfer.httpclient.retrieve.connectTimeout=120000
 +
  - org.eclipse.ecf.provider.filetransfer.httpclient.retrieve.readTimeout=120000
  
[[Category:Equinox p2| Transport debugging / tracing]]
+
The number of retrying attempts(Socket Timeout and Reset exception) for ECF based transport implementation. The default value is no retrying. Since '''Juno M2'''.
 +
-Dorg.eclipse.equinox.p2.transport.ecf.retry=5
 +
 
 +
[[Category:Equinox p2|Transport debugging / tracing]]

Latest revision as of 00:41, 27 September 2011

The following set of system properties can be enabled to debug http / https connection when p2 is setup to use the Apache Http Client (this is the default case in the eclipse SDK)

-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
-Dorg.apache.commons.logging.simplelog.showdatetime=true 
-Dorg.apache.commons.logging.simplelog.log.httpclient.wire.header=debug
-Dorg.apache.commons.logging.simplelog.log.org.apache.commons.httpclient=debug
-Dorg.apache.commons.logging.simplelog.log.httpclient.wire=debug

Timeout controls for JRE-http based transport. The JRE-http transport is automatically used when we are connecting to an NTLM proxy.

- org.eclipse.ecf.provider.filetransfer.retrieve.connectTimeout=15000
- org.eclipse.ecf.provider.filetransfer.retrieve.readTimeout=1000
- org.eclipse.ecf.provider.filetransfer.retrieve.retryAttempts=20
- org.eclipse.ecf.provider.filetransfer.retrieve.closeTimeout=1000
- org.eclipse.ecf.provider.filetransfer.browse.connectTimeout=3000
- org.eclipse.ecf.provider.filetransfer.browse.readTimeout=1000

Timeout controls for Httpclient based transport. This is what is used in the eclipse SDK and various Eclipse packages by default.

- org.eclipse.ecf.provider.filetransfer.httpclient.browse.connectTimeout=120000 (HEAD)
- org.eclipse.ecf.provider.filetransfer.httpclient.retrieve.connectTimeout=120000 (GET)
- org.eclipse.ecf.provider.filetransfer.httpclient.retrieve.connectTimeout=120000
- org.eclipse.ecf.provider.filetransfer.httpclient.retrieve.readTimeout=120000

The number of retrying attempts(Socket Timeout and Reset exception) for ECF based transport implementation. The default value is no retrying. Since Juno M2.

-Dorg.eclipse.equinox.p2.transport.ecf.retry=5