[GRADLE-1754] Not able to reconnect to a running daemon Created: 19/Aug/11  Updated: 04/Jan/13  Resolved: 19/Aug/11

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-4
Fix Version/s: None

Type: Bug
Reporter: gabriele garuglieri Assignee: Unassigned
Resolution: Duplicate Votes: 0


 Description   

Running builds with daemon i see the following errors:

12:05:37.780 [DEBUG] [org.gradle.messaging.remote.internal.inet.TcpOutgoingConnector] Attempting to connect to [31b205da-067c-451e-b227-50d6af1aff85 port:1350, addresses:[/127.0.0.1]].
12:05:37.780 [DEBUG] [org.gradle.messaging.remote.internal.inet.TcpOutgoingConnector] Trying to connect to address /127.0.0.1.
12:05:38.780 [DEBUG] [org.gradle.messaging.remote.internal.inet.TcpOutgoingConnector] Cannot connect to address /127.0.0.1, skipping.
12:05:38.780 [INFO] [org.gradle.launcher.DaemonConnector] Starting Gradle daemon
12:05:38.858 [DEBUG] [org.gradle.messaging.remote.internal.inet.TcpOutgoingConnector] Attempting to connect to [31b205da-067c-451e-b227-50d6af1aff85 port:1350, addresses:[/127.0.0.1]].
12:05:38.858 [DEBUG] [org.gradle.messaging.remote.internal.inet.TcpOutgoingConnector] Trying to connect to address /127.0.0.1.
12:05:39.796 [DEBUG] [org.gradle.messaging.remote.internal.inet.TcpOutgoingConnector] Cannot connect to address /127.0.0.1, skipping.
12:05:39.999 [DEBUG] [org.gradle.messaging.remote.internal.inet.TcpOutgoingConnector] Attempting to connect to [23193ea3-dca6-45c8-89d9-5972db94185b port:1454, addresses:[/127.0.0.1]].
12:05:39.999 [DEBUG] [org.gradle.messaging.remote.internal.inet.TcpOutgoingConnector] Trying to connect to address /127.0.0.1.
12:05:40.015 [DEBUG] [org.gradle.messaging.remote.internal.inet.TcpOutgoingConnector] Connected to address /127.0.0.1.

No other build is ruuning at the same time.

As the other bug i submitted GRADLE-1753 the frequency of the event depend on how the builds are run:

  1. running builds from within eclipse with STS Gradle tooling, i've never been able to reproduce
  2. running builds from command line or from gradle gui with -d, very very difficult to reproduce
  3. running builds from command line, it happens but rarely
  4. running builds from gradle gui it happens quite often

When not running in debug mode i don't see messages but the behavior of the build make me suppose what's happening, the build stalls for some seconds, the daemon is terminated, another instance is started then the build starts.

If this can help you, with milestone 3 it was very very frequent while with milestone-4-20110811054204+0200 it happens less often.

I've been able to reproduce using the check task from the application sample that comes with distribution.

 Comments   
Comment by Szczepan Faber [ 19/Aug/11 ]

What you're seeing are not errors but debug messages

Anyways, I think I'm going to close it as a duplicate of GRADLE-1748 which I'm working on at the moment.

Generated at Wed Jun 30 12:03:30 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.