Bug #525

Feature #1022: RCP: X.X, proxy settings in TXM and its components

RCP: 0.7.5, Fix timeout error at start-up when user is using a proxy

Added by Matthieu Decorde almost 6 years ago. Updated over 4 years ago.

Status:Closed Start date:01/17/2014
Priority:Normal Due date:
Assignee:- % Done:

100%

Category:Network Spent time: -
Target version:TXM 0.7.7

Description

During TXM startup, the splash screen is frozen for X minutes.
See attached log file for stacktraces.

Solution1: Change the timeout length.

The timeout parameter is stored in a HttpParams and read with
PlainSocketFactory.connectSocket :
int timeout = HttpConnectionParams.getConnectionTimeout(params);
Using pref name :
public static final String CONNECTION_TIMEOUT = "http.connection.timeout";

To change the behavior, ones need to modify this global variable
org.apache.http.params.CoreConnectionPNames

Solution 2: set native mode

We also need to try to define the default "Network connection" preference to "Native". A link : http://eclipsesource.com/blogs/2012/06/01/eclipse-proxy-and-p2/
Or to it programmaticaly:

/**
 * Activates the proxy service and sets the network connection active provider as native.
     */
    private void  activateProxyService() {
        Bundle bundle = Platform.getBundle("org.eclipse.ui.ide"); //$NON-NLS-1$
        IProxyService  proxyService = null;
        if (bundle != null) {
            ServiceReference ref = bundle.getBundleContext().getServiceReference(IProxyService.class.getName());
            if (ref != null)
                proxyService = bundle.getBundleContext().getService(ref);
        }
        if (proxyService == null) {
            Log.warning("Proxy service could not be found."); //$NON-NLS-1$
        }
        // Set the network connection active provider as native
        else    {
             proxyService.setSystemProxiesEnabled(true);
            proxyService.setProxiesEnabled(true);
        }
    }

The native OS proxy detection may be done by adding some native packages linked to org.eclipse.core.net for each target platform (eg. org.eclipse.core.net.win32.x86_64)

Solution 3:

  • something is trying to use the network before the proxy is set
    • like the automatic update: #1036
    • something else ?? not found yet

Solution 4

Add the following run arguments to the product configuration:

-Dorg.eclipse.ecf.provider.filetransfer.retrieve.connectTimeout=1000
-Dorg.eclipse.ecf.provider.filetransfer.browse.connectTimeout=2000
-Dorg.eclipse.ecf.provider.filetransfer.browse.readTimeout=1000
-Dorg.eclipse.ecf.provider.filetransfer.retrieve.closeTimeout=2000
-Dorg.eclipse.ecf.provider.filetransfer.retrieve.readTimeout=2000
-Dorg.eclipse.ecf.provider.filetransfer.retrieve.retryAttempts=2

proxy_stacktrace.txt Magnifier (19.4 kB) Matthieu Decorde, 10/01/2014 03:00 pm


Related issues

related to Feature #868: TBX: X.X, R proxy configuration during TXM work session Closed 06/17/2014

History

#1 Updated by Matthieu Decorde almost 6 years ago

  • Subject changed from RCP: 0.7.5, Fix timeout errorat start-up when user is using a proxy to RCP: 0.7.5, Fix timeout error at start-up when user is using a proxy

#2 Updated by Sebastien Jacquot almost 6 years ago

We also need to try to define the default "Network connection" preference to "Native". A link : http://eclipsesource.com/blogs/2012/06/01/eclipse-proxy-and-p2/

#3 Updated by Sebastien Jacquot almost 6 years ago

This method appears to work on my Windows 7 + proxy :

/**
 * Activates the proxy service and sets the network connection active provider as native.
*/
private void activateProxyService() {
Bundle bundle = Platform.getBundle("org.eclipse.ui.ide"); //$NON-NLS-1$
IProxyService proxyService = null;
if (bundle != null) {
ServiceReference ref = bundle.getBundleContext().getServiceReference(IProxyService.class.getName());
if (ref != null)
proxyService = bundle.getBundleContext().getService(ref);
}
if (proxyService == null) {
Log.warning("Proxy service could not be found."); //$NON-NLS-1$
}
// Set the network connection active provider as native
else {
proxyService.setSystemProxiesEnabled(true);
proxyService.setProxiesEnabled(true);
}
}

#4 Updated by Matthieu Decorde almost 6 years ago

Test to do : On Linux, set an open proxy service and run TXM

#5 Updated by Sebastien Jacquot almost 6 years ago

For the tests on Linux we should test without proxy too, I don't know if calling these methods keeps the 'direct' provider when necessary, I can't test.

And there's still a problem with this method, as you said Matthieu, the user network connection preferences will be overridden each time TXM start, we may add a test at first TXM run or only call :

proxyService.setSystemProxiesEnabled(true);
proxyService.setProxiesEnabled(true);

if the linked preferences are not defined but at the moment I don't see how to know if the user has changed the preferences or not.

Notes :
- these preferences are saved in the file org.eclipse.core.net.prefs.
- we can get the proxies data with :

IProxyData[] proxyData = proxyService.getProxyData();

#6 Updated by Matthieu Decorde almost 6 years ago

  • Target version changed from TXM 0.7.5 to 5

#7 Updated by Sebastien Jacquot almost 6 years ago

  • Target version changed from 5 to TXM 0.7.5

Here is the stack trace in "Roaming\.txm\.metadata\.log" when launching TXM 0.7.5 final for the first time, in OS connection by proxy environment :

!ENTRY org.eclipse.equinox.p2.transport.ecf 2 0 2014-02-13 15:28:17.121
!MESSAGE Connection to http://txm.textometrie.org/updates/TXM/p2.index failed on Connection to http://txm.textometrie.org refused. Retry attempt 0 started
!STACK 0
org.apache.http.conn.HttpHostConnectException: Connection to http://txm.textometrie.org refused
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:158)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:150)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:575)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1074)
at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:621)
at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:879)
at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:570)
at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106)
at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:422)
at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:355)
at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadIndexFile(AbstractRepositoryManager.java:735)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:657)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
at org.txm.rcpapplication.p2.plugins.TXMUpdateHandler.addURL(TXMUpdateHandler.java:196)
at org.txm.rcpapplication.p2.plugins.TXMUpdateHandler.addDefaultUpdateSite(TXMUpdateHandler.java:174)
at org.txm.rcpapplication.p2.plugins.FixUpdateHandler.run(FixUpdateHandler.java:67)
at org.txm.rcpapplication.ApplicationWorkbenchAdvisor.postStartup(ApplicationWorkbenchAdvisor.java:371)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2708)
at org.eclipse.ui.internal.Workbench.access$7(Workbench.java:2591)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:608)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.txm.rcpapplication.Application.run(Application.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at org.eclipse.ecf.internal.provider.filetransfer.httpclient4.ECFHttpClientProtocolSocketFactory.connectSocket(ECFHttpClientProtocolSocketFactory.java:84)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148)
... 48 more

!ENTRY org.eclipse.equinox.p2.updatechecker 4 0 2014-02-13 15:47:06.527
!MESSAGE Exception in update check thread
!STACK 0
java.lang.NullPointerException
at org.eclipse.equinox.p2.engine.ProvisioningContext.loadMetadataRepository(ProvisioningContext.java:220)
at org.eclipse.equinox.p2.engine.ProvisioningContext.getLoadedMetadataRepositories(ProvisioningContext.java:194)
at org.eclipse.equinox.p2.engine.ProvisioningContext.getMetadata(ProvisioningContext.java:275)
at org.eclipse.equinox.internal.p2.director.SimplePlanner.updatesFor(SimplePlanner.java:784)
at org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker.checkForUpdates(UpdateChecker.java:134)
at org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker$UpdateCheckThread.run(UpdateChecker.java:72)


.
.
.
And the stack trace in TXM console after waiting 7-8 minutes when TXM is launched :
.
.
.
---------------------------------------------------------------------------------------------------------------------------------

No repo - create a newmetadata repo
No repo - create a new artifact repo
Error while adding artifact repo: http://txm.textometrie.org/updates/TXM
org.eclipse.equinox.p2.core.ProvisionException: Unable to connect to repository http://txm.textometrie.org/updates/TXM/artifacts.xml
at org.eclipse.equinox.internal.p2.repository.CacheManager.createCache(CacheManager.java:192)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepositoryFactory.getLocalFile(SimpleArtifactRepositoryFactory.java:65)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepositoryFactory.load(SimpleArtifactRepositoryFactory.java:88)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepositoryFactory.load(SimpleArtifactRepositoryFactory.java:76)
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.factoryLoad(ArtifactRepositoryManager.java:73)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.loadRepository(ArtifactRepositoryManager.java:104)
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.loadRepository(ArtifactRepositoryManager.java:100)
at org.txm.rcpapplication.p2.plugins.TXMUpdateHandler.addURL(TXMUpdateHandler.java:212)
at org.txm.rcpapplication.p2.plugins.TXMUpdateHandler.addDefaultUpdateSite(TXMUpdateHandler.java:174)
at org.txm.rcpapplication.p2.plugins.FixUpdateHandler.run(FixUpdateHandler.java:67)
at org.txm.rcpapplication.ApplicationWorkbenchAdvisor.postStartup(ApplicationWorkbenchAdvisor.java:371)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2708)
at org.eclipse.ui.internal.Workbench.access$7(Workbench.java:2591)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:608)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.txm.rcpapplication.Application.run(Application.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Caused by: org.apache.http.conn.HttpHostConnectException: Connection to http://txm.textometrie.org refused
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:158)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:150)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:575)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:263)
at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148)
... 9 more

#8 Updated by Sebastien Jacquot almost 6 years ago

  • Target version changed from TXM 0.7.5 to 5

#9 Updated by Matthieu Decorde over 5 years ago

FR : notes

Sous TXM depuis un setup je ne peux pas choisir 'Native' comme 'Active Provider', si je mets 'Native', il ne m'affiche pas les réglages de mon proxy system et si je sauvegarde il me repasse directement en 'Direct'.
Sous TXM lancé depuis Eclipse tout fonctionne, je peux choisir 'Native' et il m'affiche bien mes proxies system. Sous Eclipse aussi d'ailleurs, en fait la config d'Eclipse est donc transmise à TXM.
A priori je pense que mon Eclipse doit posséder un bundle supplémentaire permettant de détecter les proxies system au démarrage, il faudrait trouver lequel pour pouvoir l'ajouter à TXM je pense, je vais faire des recherches. Tout ce que j'ai comme infos pour l'instant c'est que la détection de proxy contient du code natif différent pour chaque plateforme.

#10 Updated by Matthieu Decorde over 5 years ago

  • Target version changed from 5 to TXM 0.7.6

#11 Updated by Sebastien Jacquot over 5 years ago

The native OS proxy detection may be done by adding some native packages linked to org.eclipse.core.net for each target platform (eg. org.eclipse.core.net.win32.x86_64)

#12 Updated by Matthieu Decorde over 5 years ago

  • % Done changed from 0 to 80

Add org.eclipse.core.net.win32.x86 and org.eclipse.core.net.win32.x86_64, solved the problem.
Tested on :
- Windows7 64bit (Besançon)
- WindowsXP? 32bit (Besançon)
- Virtual WindowsXP 32bit (Lyon)

#13 Updated by Sebastien Jacquot over 5 years ago

The fix is not easily available from the 0.7.5 setup because updating to 0.7.6 is only possible by waiting ~10 minutes at the splash screen, by unplugging the network wire or by disabling the Internet connection. We should provide a new setup for 0.7.6.

#14 Updated by Matthieu Decorde over 5 years ago

  • Tracker changed from Task to Bug

#15 Updated by Matthieu Decorde over 5 years ago

  • Category set to Démarrage

#16 Updated by Sebastien Jacquot about 5 years ago

  • Target version changed from TXM 0.7.6 to TXM 0.7.7

#17 Updated by Sebastien Jacquot about 5 years ago

TODO:
- test the next setup of 0.7.7 with proxy on Windows, Linux and Mac OS
- install TXM then run it and check in "Parameters\General\Network Connections" that the "Active Provider" is "Native"
- set the release channel to alpha or dev then update to a newer version
NOTE: the difficulty is that a hang on can also occur at start-up, after the GUI is launched, but related to the R check packages bug: #868

#18 Updated by Matthieu Decorde about 5 years ago

  • Target version changed from TXM 0.7.7 to TXM 0.7.6

#19 Updated by Matthieu Decorde about 5 years ago

  • Parent task set to #1022

#20 Updated by Matthieu Decorde about 5 years ago

  • File proxy_stacktrace.txt added
  • Description updated (diff)

#21 Updated by Matthieu Decorde about 5 years ago

  • Description updated (diff)

#22 Updated by Matthieu Decorde about 5 years ago

  • Description updated (diff)

#23 Updated by Matthieu Decorde about 5 years ago

  • Description updated (diff)

#24 Updated by Matthieu Decorde about 5 years ago

  • File deleted (proxy_stacktrace.txt)

#26 Updated by Matthieu Decorde about 5 years ago

  • Description updated (diff)

#27 Updated by Matthieu Decorde about 5 years ago

  • Description updated (diff)

#28 Updated by Sebastien Jacquot about 5 years ago

  • Target version changed from TXM 0.7.6 to TXM 0.7.7

#29 Updated by Matthieu Decorde almost 5 years ago

  • Description updated (diff)

#30 Updated by Matthieu Decorde almost 5 years ago

  • Status changed from New to Feedback

#31 Updated by Sebastien Jacquot almost 5 years ago

I'm doing complementary tests. Actually I think the solution 1 and 2 should be implemented. The time out should be reduced in any case. The time out value when doing "Check for update" is at this moment approximatively 5 minutes.

Note: the exception thrown after that is not a time out exception but a connection refused exception. We should aim to raise a time out exception before the connection refused exception. The involved classes are:

org.eclipse.equinox.p2.core.ProvisionException: Unable to connect to repository http://txm.textometrie.org/updates/TXM/artifacts.xml
Caused by: org.apache.http.conn.HttpHostConnectException: Connection to http://txm.textometrie.org refused
Caused by: java.net.ConnectException: Connection refused

Test #1, add:

-Dorg.eclipse.ecf.provider.filetransfer.retrieve.closeTimeout=30
-Dorg.eclipse.ecf.provider.filetransfer.retrieve.readTimeout=30

to TXM.ini => failed, time out value stays of 5 minutes.

Test #2, add:

org.eclipse.ecf.provider.filetransfer.retrieve.closeTimeout=30
org.eclipse.ecf.provider.filetransfer.retrieve.readTimeout=30

to TXM/configuration/config.ini => failed.

Test #3, add:

http.connection.timeout=1

to TXM/configuration/config.ini => failed.

#32 Updated by Sebastien Jacquot almost 5 years ago

At first, could we ensure that there are some cancelable dialog boxes for the update at start and the update at "Check for updates" commands ?
The "Add an extension" dialog box provides a cancel button. The result is that user can cancel during the hang up when no proxies are defined or well defined, can't we do the same thing for the update command ?

#33 Updated by Sebastien Jacquot almost 5 years ago

  • Category changed from Démarrage to Network

#34 Updated by Matthieu Decorde over 4 years ago

  • Description updated (diff)

#35 Updated by Matthieu Decorde over 4 years ago

  • Description updated (diff)

#36 Updated by Sebastien Jacquot over 4 years ago

Notes :
- solutions 2 and 4 are complementary
- please see https://forge.cbp.ens-lyon.fr/redmine/issues/1022#note-27 about the solution 4. Not all the preference values have to be reduced

#37 Updated by Sebastien Jacquot over 4 years ago

Closed for redundancy, see #1022 for next steps.
Current TXM RCP behaviors are:
- we set the RCP network provider as native on Windows and Linux
- unknown current state on Mac OS X
- we have reduced the connection timeouts
- we now force the JRE-http based transport instead of the ECF httpclient provider

Therefore the solution 2 et 4 has been partially implemented.

#38 Updated by Sebastien Jacquot over 4 years ago

  • Status changed from Feedback to Closed
  • % Done changed from 80 to 100

Also available in: Atom PDF