Uploaded image for project: 'Gradle'
  1. Gradle
  2. GRADLE-2444

Gradle daemon becomes unusable

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.3-rc-1

      Description

      After using the gradle daemon a lot, eventually it becomes unusable. By this I mean, that when I try to use it, it will wait a long time and eventually reports an error that it have tried to connect 100 different Gradle daemon without success. Usually there are no java processes are running (though sometimes there are java process executing the Gradle daemon) and deleting the "daemon" directory in the ".gradle" directory solves the problem.

      This problem is rather frustrating because the Tooling api requires me to use the Gradle daemon. That is, I see no way to avoid using it.

      I believe I currently use the binaries for the Tooling api found in Gradle 1.0. It seems, that it does not matter what version (1.0 or 1.1) I specify using the `GradleConnector.useInstallation` method.

        Attachments

        1. console.debug.zip
          16 kB
        2. daemon.from.commandline.zip
          2 kB
        3. daemon.zip
          6 kB
        4. daemon2.zip
          2 kB
        5. gradle.console.zip
          15 kB
        6. logs.from.commandline.zip
          10 kB

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            forums Gradle Forums
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: