如何为Eclipse、Maven或通用Java设置Socket网络超时？

Hey there, I’ve been in your exact shoes dealing with stuck Maven tasks in Eclipse when behind restricted networks—those un-cancelable, infinitely waiting jobs are such a headache! Let’s walk through all the ways you can set up 5-second timeouts, both for Eclipse/Maven specifically and Java globally:

Maven lets you define connection and read timeouts directly in its settings file, which Eclipse will respect if configured correctly:

• Open your Maven settings.xml (usually in ~/.m2/settings.xml or Eclipse’s configured user settings location)
• Add or update your repository and mirror entries to include timeout values:

  <repositories>
    <repository>
      <id>central</id>
      <url>https://repo.maven.apache.org/maven2</url>
      <connectionTimeout>5000</connectionTimeout> <!-- 5 seconds -->
      <readTimeout>5000</readTimeout>
    </repository>
  </repositories>
  
  <mirrors>
    <mirror>
      <id>central-mirror</id>
      <mirrorOf>central</mirrorOf>
      <url>https://repo.maven.apache.org/maven2</url>
      <connectionTimeout>5000</connectionTimeout>
      <readTimeout>5000</readTimeout>
    </mirror>
  </mirrors>
  

• In Eclipse, make sure it’s using this settings file: Go to Window > Preferences > Maven > User Settings and point to your updated file, then click Update Settings.

Beyond Maven’s settings, Eclipse has its own network timeout configurations to cover broader scenarios:

• Eclipse Global Network Timeout: Go to Window > Preferences > General > Network Connections. Select your active provider (e.g., Manual if you use proxies), then edit the HTTP/HTTPS entries. In the Proxy Details window, set the Timeout field to 5000 (milliseconds).
• Maven Run Configuration Overrides: For individual Maven tasks in Eclipse, you can add VM arguments to enforce timeouts:
  1. Open Run > Run Configurations
  2. Select your Maven Build configuration
  3. Go to the JRE tab
  4. In the VM arguments field, add:

     -Dmaven.wagon.http.connectionTimeout=5000 -Dmaven.wagon.http.retryHandler.count=1
     

  This ensures the specific Maven job times out quickly and doesn’t retry unnecessarily.

If you want to apply timeouts across all Java-based tools (including Maven run outside Eclipse), use system properties:

• Per Maven Command: When running Maven from the terminal, append the timeout flags:

  mvn clean install -Dmaven.wagon.http.connectionTimeout=5000 -Dmaven.wagon.http.readTimeout=5000
  

• Global Maven Default: Set the MAVEN_OPTS environment variable to apply these settings automatically:
  • Linux/macOS: Add this to your ~/.bashrc or ~/.zshrc:

    export MAVEN_OPTS="-Dmaven.wagon.http.connectionTimeout=5000 -Dmaven.wagon.http.readTimeout=5000"
    

  • Windows: Open Command Prompt and run:

    set MAVEN_OPTS="-Dmaven.wagon.http.connectionTimeout=5000 -Dmaven.wagon.http.readTimeout=5000"
    

• Java-Wide Global Timeout: For a universal timeout that affects all Java network requests (not just Maven), use these system properties:

  java -Dsun.net.client.defaultConnectTimeout=5000 -Dsun.net.client.defaultReadTimeout=5000 ...
  

  You can add these to MAVEN_OPTS as well to cover Maven’s Java runtime.

A quick note: Some niche Maven plugins might use custom network clients that ignore these settings, but 90% of the time, the above steps will fix those stuck, un-cancelable tasks.

内容的提问来源于stack exchange，提问作者Jonathan S. Fisher