gradle an existing connection was forcibly closed by the remote host #14094

Drezir · 2020-08-11T10:24:17Z

Hi, I am suddenly starting to get this error. I can reproduce it even on newly created project using start.spring.io.

What I have already tried:

deleting $USER_HOME/.gradle directory
deleting project .gradle directory
I have downgraded from 6.5.1 do 6.4 and that works.
Version 6.6 also affected
Version 6.4.1 does not work

Only highlighted changes I have:

java {
    withSourcesJar()
}

C:\Users\aostrozlik\Desktop\core>gradlew -S
Starting a Gradle Daemon, 30 stopped Daemons could not be reused, use --status for details

FAILURE: Build failed with an exception.

* What went wrong:
Could not receive a message from the daemon.

* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Exception is:
org.gradle.launcher.daemon.client.DaemonConnectionException: Could not receive a message from the daemon.
        at org.gradle.launcher.daemon.client.DaemonClientConnection.receive(DaemonClientConnection.java:83)
        at org.gradle.launcher.daemon.client.DaemonClient.executeBuild(DaemonClient.java:168)
        at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:148)
        at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:99)
        at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:56)
        at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:212)
        at org.gradle.launcher.cli.DefaultCommandLineActionFactory$ParseAndBuildAction.execute(DefaultCommandLineActionFactory.java:294)
        at org.gradle.launcher.cli.DefaultCommandLineActionFactory$ParseAndBuildAction.execute(DefaultCommandLineActionFactory.java:266)
        at org.gradle.launcher.cli.DebugLoggerWarningAction.execute(DebugLoggerWarningAction.java:82)
        at org.gradle.launcher.cli.DebugLoggerWarningAction.execute(DebugLoggerWarningAction.java:30)
        at org.gradle.launcher.cli.WelcomeMessageAction.execute(WelcomeMessageAction.java:92)
        at org.gradle.launcher.cli.WelcomeMessageAction.execute(WelcomeMessageAction.java:38)
        at org.gradle.launcher.cli.NativeServicesInitializingAction.execute(NativeServicesInitializingAction.java:44)
        at org.gradle.launcher.cli.NativeServicesInitializingAction.execute(NativeServicesInitializingAction.java:26)
        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:41)
        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:26)
        at org.gradle.launcher.cli.DefaultCommandLineActionFactory$WithLogging.execute(DefaultCommandLineActionFactory.java:259)
        at org.gradle.launcher.Main.doAction(Main.java:35)
        at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:50)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:564)
        at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60)
        at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37)
        at org.gradle.launcher.GradleMain.main(GradleMain.java:31)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:564)
        at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:35)
        at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:108)
        at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:63)
Caused by: org.gradle.internal.remote.internal.MessageIOException: Could not read message from '/127.0.0.1:10627'.
        at org.gradle.internal.remote.internal.inet.SocketConnection.receive(SocketConnection.java:94)
        at org.gradle.launcher.daemon.client.DaemonClientConnection.receive(DaemonClientConnection.java:77)
        ... 32 more
Caused by: com.esotericsoftware.kryo.KryoException: java.io.IOException: Software v hostitelskÚm poŔÝtaŔi ukonŔil vytvo°enÚ p°ipojenÝ
        at com.esotericsoftware.kryo.io.Input.fill(Input.java:148)
        at com.esotericsoftware.kryo.io.Input.require(Input.java:178)
        at com.esotericsoftware.kryo.io.Input.readVarInt(Input.java:355)
        at com.esotericsoftware.kryo.io.Input.readInt(Input.java:350)
        at org.gradle.internal.serialize.kryo.KryoBackedDecoder.readSmallInt(KryoBackedDecoder.java:127)
        at org.gradle.internal.serialize.DefaultSerializerRegistry$TaggedTypeSerializer.read(DefaultSerializerRegistry.java:142)
        at org.gradle.internal.serialize.Serializers$StatefulSerializerAdapter$1.read(Serializers.java:36)
        at org.gradle.internal.remote.internal.inet.SocketConnection.receive(SocketConnection.java:81)
        ... 33 more
Caused by: java.io.IOException: Software v hostitelskÚm poŔÝtaŔi ukonŔil vytvo°enÚ p°ipojenÝ
        at java.base/sun.nio.ch.SocketDispatcher.read0(Native Method)
        at java.base/sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:46)
        at java.base/sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:276)
        at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:233)
        at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:223)
        at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:367)
        at org.gradle.internal.remote.internal.inet.SocketConnection$SocketInputStream.read(SocketConnection.java:196)
        at com.esotericsoftware.kryo.io.Input.fill(Input.java:146)
        ... 40 more

Gradle status

  PID STATUS   INFO
  8448 STOPPED  (after the daemon was no longer found in the daemon registry)
 21340 STOPPED  (after the daemon was no longer found in the daemon registry)
 21196 STOPPED  (after the daemon was no longer found in the daemon registry)
 13864 STOPPED  (after the daemon was no longer found in the daemon registry)
 13000 STOPPED  (after the daemon was no longer found in the daemon registry)
 11436 STOPPED  (after the daemon was no longer found in the daemon registry)
 16004 STOPPED  (after the daemon was no longer found in the daemon registry)
   100 STOPPED  (after the daemon was no longer found in the daemon registry)
 20892 STOPPED  (after the daemon was no longer found in the daemon registry)
  9040 STOPPED  (after the daemon was no longer found in the daemon registry)
  7040 STOPPED  (after the daemon was no longer found in the daemon registry)
 19132 STOPPED  (after the daemon was no longer found in the daemon registry)
 15952 STOPPED  (after the daemon was no longer found in the daemon registry)
  9212 STOPPED  (after the daemon was no longer found in the daemon registry)
  8048 STOPPED  (after the daemon was no longer found in the daemon registry)
 16924 STOPPED  (after the daemon was no longer found in the daemon registry)
  1772 STOPPED  (after the daemon was no longer found in the daemon registry)
  1908 STOPPED  (after the daemon was no longer found in the daemon registry)
 17888 STOPPED  (after the daemon was no longer found in the daemon registry)
 11312 STOPPED  (after the daemon was no longer found in the daemon registry)
 16276 STOPPED  (after the daemon was no longer found in the daemon registry)
 16848 STOPPED  (after the daemon was no longer found in the daemon registry)
 17204 STOPPED  (after the daemon was no longer found in the daemon registry)
 13616 STOPPED  (after the daemon was no longer found in the daemon registry)
 15436 STOPPED  (after the daemon was no longer found in the daemon registry)
 11152 STOPPED  (after the daemon was no longer found in the daemon registry)
  9220 STOPPED  (after the daemon was no longer found in the daemon registry)
 17944 STOPPED  (after the daemon was no longer found in the daemon registry)
  9520 STOPPED  (by user or operating system)

Gradle info:

Starting a Gradle Daemon, 29 stopped Daemons could not be reused, use --status for details
Starting process 'Gradle build daemon'. Working directory: C:\Users\aostrozlik\.gradle\daemon\6.5.1 Command: C:\Program Files\AdoptOpenJDK\jdk-14.0.2.12-hotspot\bin\java.exe --add-opens java.base/java.util=ALL-UNNAMED --add-opens ja
va.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED -XX:MaxMetaspaceSize=256m -XX:+HeapDumpOnOutOfMemoryError -Xms256m -Xmx512m -Dfile.encoding=windows-
1250 -Duser.country=CZ -Duser.language=cs -Duser.variant -cp C:\Users\aostrozlik\.gradle\wrapper\dists\gradle-6.5.1-bin\1m5048aptkfynhbvolwgr4ej9\gradle-6.5.1\lib\gradle-launcher-6.5.1.jar org.gradle.launcher.daemon.bootstrap.Gradle
Daemon 6.5.1
Successfully started process 'Gradle build daemon'
An attempt to start the daemon took 1.953 secs.
Removing daemon from the registry due to communication failure. Daemon information: DaemonInfo{pid=10176, address=[db41e774-f36e-45b6-a030-8c68a1a842bf port:10605, addresses:[/127.0.0.1]], state=Busy, lastBusy=1597141329670, context
=DefaultDaemonContext[uid=7c12bead-ca8c-4a3d-a1be-71e4574df391,javaHome=C:\Program Files\AdoptOpenJDK\jdk-14.0.2.12-hotspot,daemonRegistryDir=C:\Users\aostrozlik\.gradle\daemon,pid=10176,idleTimeout=10800000,priority=NORMAL,daemonOp
ts=--add-opens,java.base/java.util=ALL-UNNAMED,--add-opens,java.base/java.lang=ALL-UNNAMED,--add-opens,java.base/java.lang.invoke=ALL-UNNAMED,--add-opens,java.prefs/java.util.prefs=ALL-UNNAMED,-XX:MaxMetaspaceSize=256m,-XX:+HeapDump
OnOutOfMemoryError,-Xms256m,-Xmx512m,-Dfile.encoding=windows-1250,-Duser.country=CZ,-Duser.language=cs,-Duser.variant]}

The text was updated successfully, but these errors were encountered:

big-guy · 2020-08-12T01:16:43Z

Could you run with --debug and send me the build log to sterling@gradle.com with 6.4 and 6.6?

Camork · 2020-09-08T01:36:06Z

I got into the same issue, I have to reboot to resolve it, but it will come soon.

hborchardt · 2020-09-29T10:24:00Z

I got this issue and solved it by deactivating the Windows 10 mobile hotspot internet sharing. I then reproduced it by activating the hotspot and connecting a device to it, and starting ./gradlew -S --no-daemon to spawn a new daemon, which produced the error again.

kriegaex · 2020-10-09T01:04:16Z

OMG, Windows 10 mobile hotspot! Thank you so much! I could not start a single Gradle build for months, neither with or without daemon, because I always activate the hotspot. As soon as I deactivate the mobile hotspot, it works.

Please fix this issue ASAP, it must be a networking issue.

kriegaex · 2020-10-09T02:32:40Z

Trusting @Drezir and his original problem report, it used to work in Gradle 6.4 and started failing in 6.4.1. ~~I have not checked in order to confirm that.~~ I have just checked and can confirm it. Hence, the problem should be somewhere in this diff: v6.4.0...v6.4.1

Maybe one of the maintainers wants to check the diff, it is not very big, only 11 commits. This change seems to be network-related, for instance. It is from commit 490d43b.

hborchardt · 2020-10-14T09:00:55Z

I investigated a little more and it appears that after connecting a device to the mobile hotspot, even a ping 127.0.0.1 on the console does not work for me. This is very strange behaviour on Microsoft's part, and very likely the reason for this bug, as @kriegaex pointed out a commit with the addition of a check if the loopback interface address is reachable. Accessing services started on 127.0.0.1 is possible though (e.g. curl http://127.0.0.1 works).
I wasn't able to find any resources on this behaviour, or even how the hotspot feature exactly works.

Maybe @big-guy can figure out an alternative to the reachability check, as I don't fully understand why it was added :)

kriegaex · 2020-10-15T02:11:51Z

after connecting a device to the mobile hotspot, even a ping 127.0.0.1 on the console does not work for me.

Confirmed.

Accessing services started on 127.0.0.1 is possible though (e.g. curl http://127.0.0.1 works).

Confirmed.

I wasn't able to find any resources on this behaviour, or even how the hotspot feature exactly works.

I did not investigate, but maybe the output of route print helps (in German, sorry). I hope it is not information overkill for a simple problem:

===========================================================================
Schnittstellenliste
 11...8c 16 45 1f 66 b4 ......Intel(R) Ethernet Connection (4) I219-V
 28...00 28 f8 57 0c 70 ......Microsoft Wi-Fi Direct Virtual Adapter #2
 22...00 ff a4 0d f7 3a ......TAP-Windows Adapter V9
  8...00 28 f8 57 0c 6f ......Intel(R) Dual Band Wireless-AC 8265
 34...02 28 f8 57 0c 6f ......Microsoft Wi-Fi Direct Virtual Adapter
 21...00 ff a3 5c 53 9f ......TeamViewer VPN Adapter
  1...........................Software Loopback Interface 1
  7...84 9d 96 57 56 56 ......Generic Mobile Broadband Adapter
 49...00 15 5d 25 50 96 ......Hyper-V Virtual Ethernet Adapter
===========================================================================

IPv4-Routentabelle
===========================================================================
Aktive Routen:
     Netzwerkziel    Netzwerkmaske          Gateway    Schnittstelle Metrik
          0.0.0.0          0.0.0.0     192.168.88.1    192.168.88.14     50
        127.0.0.0        255.0.0.0   Auf Verbindung         127.0.0.1    331
        127.0.0.1  255.255.255.255   Auf Verbindung         127.0.0.1    331
  127.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    331
   172.17.205.176  255.255.255.240   Auf Verbindung    172.17.205.177   5256
   172.17.205.177  255.255.255.255   Auf Verbindung    172.17.205.177   5256
   172.17.205.191  255.255.255.255   Auf Verbindung    172.17.205.177   5256
     192.168.88.0    255.255.255.0   Auf Verbindung     192.168.88.14    306
    192.168.88.14  255.255.255.255   Auf Verbindung     192.168.88.14    306
   192.168.88.255  255.255.255.255   Auf Verbindung     192.168.88.14    306
    192.168.137.0    255.255.255.0   Auf Verbindung     192.168.137.1    306
    192.168.137.1  255.255.255.255   Auf Verbindung     192.168.137.1    306
  192.168.137.255  255.255.255.255   Auf Verbindung     192.168.137.1    306
        224.0.0.0        240.0.0.0   Auf Verbindung         127.0.0.1    331
        224.0.0.0        240.0.0.0   Auf Verbindung     192.168.88.14    306
        224.0.0.0        240.0.0.0   Auf Verbindung     192.168.137.1    306
        224.0.0.0        240.0.0.0   Auf Verbindung    172.17.205.177   5256
  255.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    331
  255.255.255.255  255.255.255.255   Auf Verbindung     192.168.88.14    306
  255.255.255.255  255.255.255.255   Auf Verbindung     192.168.137.1    306
  255.255.255.255  255.255.255.255   Auf Verbindung    172.17.205.177   5256
===========================================================================
Ständige Routen:
  Keine

IPv6-Routentabelle
===========================================================================
Aktive Routen:
 If Metrik Netzwerkziel             Gateway
  1    331 ::1/128                  Auf Verbindung
  8    306 fe80::/64                Auf Verbindung
 34    306 fe80::/64                Auf Verbindung
 49   5256 fe80::/64                Auf Verbindung
  8    306 fe80::583:b5c6:49b9:e830/128
                                    Auf Verbindung
 34    306 fe80::7127:a101:c3cf:a4cc/128
                                    Auf Verbindung
 49   5256 fe80::a07d:19cf:66a1:e4eb/128
                                    Auf Verbindung
  1    331 ff00::/8                 Auf Verbindung
  8    306 ff00::/8                 Auf Verbindung
 34    306 ff00::/8                 Auf Verbindung
 49   5256 ff00::/8                 Auf Verbindung
===========================================================================
Ständige Routen:
  Keine

mahdi-malv · 2020-11-02T12:37:36Z

Any updates on this?
Experiencing this issue with Gradle:6.5 on Windows 10 build 19041

kriegaex · 2020-11-02T12:46:49Z

Experiencing this issue with Gradle:6.4 on Windows 10 build 19041

Hm, are you sure? 6.4 should work, it should start failing at 6.4.1.

mahdi-malv · 2020-11-02T16:07:01Z

@kriegaex Sorry for typo. I meant 6.5

Likqez · 2020-11-26T09:50:21Z

Experiencing this on 6.6 too, forced to downgrade gradle for now..

andre-paulo98 · 2020-12-05T23:16:03Z

Can also reproduce on 6.5, turning off Mobile Hotspot solves the issue.
@big-guy do you still need debug logs?

RaMui · 2020-12-21T08:28:14Z

Can also reproduce on 6.7.1 with Windows 10 build 19041.488

ice1000 · 2021-03-05T08:45:13Z

Reproduced with gradle 6.8.1

XiXiongMaoXiong · 2021-03-11T18:55:56Z

Same with versions 6.7.x and 6.8.x

XiXiongMaoXiong · 2021-03-12T18:25:39Z

The only solution for now is to either:

Downgrade to Gradle 6.1.1.
Do not use a WiFi hotspot on Windows 10.
Do not start a program which listens on the localhost address of your PC, e.g. a Node or an Apache webserver, or whatever that binds to your loopback address.
Set Android Studio to use ipv6.
If you're sharing your network adapter's connection with another adapter, or you're bridging 2 network adapter connections (like I do), give them a static IP outside the range of your default gateway. For example if your main network's gateway is 192.168.1.x then when you Bridge or Share connections, set the Receiver adapter (the one which the internet is shared to) to use a static IP in a range like 192.168.0.x (trust me it will work).

gza-slc · 2021-03-13T12:56:02Z

Reproduced with Gradle 6.8.1 and Windows 10 19041.867

kriegaex · 2021-03-14T07:08:01Z

It is from commit 490d43b.

I wonder why users are expected to make complicated local configurations. Why don't the maintainers just revert that commit I found 5+ months ago? It did not add much value anyway. Until you find a way to do the network check in a more precise way, just revert to the old behaviour. Using the Win10 local WiFi hotspot is a very common thing. Because of that I am still using Gradle 6.4 because my upgrade path is blocked. Why is nobody taking care of this very simple issue?

Likqez · 2021-03-14T11:04:13Z

@jjohannes bumb

XiXiongMaoXiong · 2021-03-16T19:51:20Z

It is from commit 490d43b.

I wonder why users are expected to make complicated local configurations. Why don't the maintainers just revert that commit I found 5+ months ago? It did not add much value anyway. Until you find a way to do the network check in a more precise way, just revert to the old behaviour. Using the Win10 local WiFi hotspot is a very common thing. Because of that I am still using Gradle 6.4 because my upgrade path is blocked. Why is nobody taking care of this very simple issue?

As the owner and founder of the world's most notorious tech company which is Google of course, I agree with you.

+1

scrouthtv · 2021-04-19T07:16:54Z

@kriegaex @prettydev For me, it's fixed in Gradle 7.0 (I didn't try anything in between 6.5 and 7.0). I also couldn't downgrade bc Android Studio requires gradle 6.5 min.

I am running Windows 10 Version 2004 Build 19041.928

kriegaex · 2021-04-19T07:50:54Z

@scrouthtv, I can confirm after a quick test that in 7.0 it seems to work. The reason is simple: The reachability check has been reverted, just like I requested. The corresponding commit 83f4323 just did not mention this issue in its commit message.

I am not acquainted with the Gradle release strategy. Does the 7.0 release mean that there will be no more 6.x maintenance releases in which this could be back-ported? If so, this issue could be closed. Otherwise, I am still requesting back-ports to all affected release branches still maintained.

scrouthtv · 2021-04-19T07:52:38Z

I am not acquainted with the Gradle release strategy.

Me neither, I'm just trying to write an Android app :( Just wanted to give a quick heads-up if anyone else faces this issue.

kriegaex · 2021-04-19T07:57:37Z

Another tiny bit of information: While ping 127.0.0.1 really does not work on Windows 10 when the mobile hotspot is active and arguably this could be regarded as a Windows bug, like someone said at 490d43b#r48297140, I happened to notice that ping localhost works because it uses IPv6, equivalent to ping ::1 (sorry, in German):

XXX>ping -n 1 127.0.0.1

Ping wird ausgeführt für 127.0.0.1 mit 32 Bytes Daten:
Zeitüberschreitung der Anforderung.

Ping-Statistik für 127.0.0.1:
    Pakete: Gesendet = 1, Empfangen = 0, Verloren = 1
    (100% Verlust),

XXX>ping -n 1 localhost

Ping wird ausgeführt für Xander-Ultrabook [::1] mit 32 Bytes Daten:
Antwort von ::1: Zeit<1ms

Ping-Statistik für ::1:
    Pakete: Gesendet = 1, Empfangen = 1, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms

XXX>ping -n 1 ::1

Ping wird ausgeführt für ::1 mit 32 Bytes Daten:
Antwort von ::1: Zeit<1ms

Ping-Statistik für ::1:
    Pakete: Gesendet = 1, Empfangen = 1, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms

Maybe using ::1 instead of 127.0.0.1 on Windows is a possible path to re-introduce the reachability check in the future in a more "Win10 mobile hotspot friendly" way.

ArcticLampyrid · 2021-05-03T04:20:05Z

Have feedbacked to microsoft
https://aka.ms/AAce99f

DerpyDashie · 2021-08-19T17:13:38Z

Was having the same problem without hotspot(probably because of ICS), but after some research was able to fix it by forcing java to use IPv4 by setting _JAVA_OPTIONS environment variable to -Djava.net.preferIPv4Stack=true, works with Gradle 6.7

ArcticLampyrid · 2021-08-24T09:16:56Z

Win11 fixed loopback problem with hotspot.

kriegaex · 2021-08-27T07:11:42Z

Was having the same problem without hotspot(probably because of ICS), but after some research was able to fix it by forcing java to use IPv4 by setting _JAVA_OPTIONS environment variable to -Djava.net.preferIPv4Stack=true, works with Gradle 6.7

I can confirm that this approach also works with Windows 10 Mobile Hotspot. Because in IntelliJ IDEA there is no way to set environment variables or JVM parameters for the Gradle runner directly, I had to set a system environment variable.

I am still hoping for a Gradle 6.x bugfix. Gradle 7 proves that reverting the commit I found fixes the problem, so why not port it back to Grade 6.x, reinstating the situation in 6.4 which broke in 6.4.1?

ghost · 2021-09-01T13:43:03Z

I can confirm that this approach also works with Windows 10 Mobile Hotspot. Because in IntelliJ IDEA there is no way to set environment variables or JVM parameters for the Gradle runner directly, I had to set a system environment variable.

I can also confirm this works without needing to disable Windows 10 Hotspot, which is what I needed. Thanks.

sky-clr · 2022-12-12T03:25:07Z

win11 also encountered this problem, did not open the hotspot

ArcticLampyrid · 2022-12-12T08:25:41Z

win11 also encountered this problem, did not open the hotspot

Perhaps not related to this issue.
Maybe what you meet is a simple network failure.

jbartok · 2023-09-15T12:21:15Z

Fixed in Gradle 7.0.

Drezir added a:bug from:contributor labels Aug 11, 2020

voidzcy mentioned this issue Dec 29, 2020

MessageIOException occurs when building grcp-core:test grpc/grpc-java#7767

Closed

StevenL98 mentioned this issue Mar 4, 2021

Bounty payout voting and payment execution - self-evolving AI-DAO Tribler/tribler#5986

Open

ice1000 mentioned this issue Mar 5, 2021

Gradle and JDK 16 aya-prover/aya-prover-proto#198

Closed

jjohannes added @core Issue owned by GBT Core and removed contributor labels Mar 29, 2021

scrouthtv mentioned this issue May 15, 2021

Add support for Gradle 7.0 MinecraftForge/ForgeGradle#763

Closed

vp-mazekine mentioned this issue Jul 19, 2021

"An existing connection was forcibly closed by the remote host" during the generateContractWrappers task hyperledger/web3j-gradle-plugin#54

Closed

DerpyDashie mentioned this issue Aug 19, 2021

Could not receive a message from the daemon. #16996

Closed

nomisRev added a commit to arrow-kt/arrow that referenced this issue Dec 25, 2021

https://github.com/gradle/gradle/issues/14094#issuecomment-700612298

639e8e5

nomisRev added a commit to arrow-kt/arrow that referenced this issue Dec 25, 2021

https://github.com/gradle/gradle/issues/14094#issuecomment-902092837

cbbbec8

ov7a added in:daemon re:windows Issue related to using Gradle on Windows to-triage has:workaround Indicates that the issue has a workaround and removed @core Issue owned by GBT Core labels Sep 13, 2023

jbartok closed this as completed Sep 15, 2023

jbartok added this to the 7.0 milestone Sep 15, 2023

jbartok removed the to-triage label Sep 15, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

gradle an existing connection was forcibly closed by the remote host #14094

gradle an existing connection was forcibly closed by the remote host #14094

Drezir commented Aug 11, 2020 •

edited

Loading

big-guy commented Aug 12, 2020 •

edited

Loading

Camork commented Sep 8, 2020

hborchardt commented Sep 29, 2020

kriegaex commented Oct 9, 2020 •

edited

Loading

kriegaex commented Oct 9, 2020 •

edited

Loading

hborchardt commented Oct 14, 2020

kriegaex commented Oct 15, 2020

mahdi-malv commented Nov 2, 2020 •

edited

Loading

kriegaex commented Nov 2, 2020

mahdi-malv commented Nov 2, 2020

Likqez commented Nov 26, 2020

andre-paulo98 commented Dec 5, 2020

RaMui commented Dec 21, 2020

ice1000 commented Mar 5, 2021

XiXiongMaoXiong commented Mar 11, 2021

XiXiongMaoXiong commented Mar 12, 2021

gza-slc commented Mar 13, 2021

kriegaex commented Mar 14, 2021

Likqez commented Mar 14, 2021

XiXiongMaoXiong commented Mar 16, 2021 •

edited

Loading

scrouthtv commented Apr 19, 2021 •

edited

Loading

kriegaex commented Apr 19, 2021

scrouthtv commented Apr 19, 2021

kriegaex commented Apr 19, 2021 •

edited

Loading

ArcticLampyrid commented May 3, 2021

DerpyDashie commented Aug 19, 2021

ArcticLampyrid commented Aug 24, 2021

kriegaex commented Aug 27, 2021

ghost commented Sep 1, 2021

sky-clr commented Dec 12, 2022

ArcticLampyrid commented Dec 12, 2022

jbartok commented Sep 15, 2023

gradle an existing connection was forcibly closed by the remote host #14094

gradle an existing connection was forcibly closed by the remote host #14094

Comments

Drezir commented Aug 11, 2020 • edited Loading

big-guy commented Aug 12, 2020 • edited Loading

Camork commented Sep 8, 2020

hborchardt commented Sep 29, 2020

kriegaex commented Oct 9, 2020 • edited Loading

kriegaex commented Oct 9, 2020 • edited Loading

hborchardt commented Oct 14, 2020

kriegaex commented Oct 15, 2020

mahdi-malv commented Nov 2, 2020 • edited Loading

kriegaex commented Nov 2, 2020

mahdi-malv commented Nov 2, 2020

Likqez commented Nov 26, 2020

andre-paulo98 commented Dec 5, 2020

RaMui commented Dec 21, 2020

ice1000 commented Mar 5, 2021

XiXiongMaoXiong commented Mar 11, 2021

XiXiongMaoXiong commented Mar 12, 2021

gza-slc commented Mar 13, 2021

kriegaex commented Mar 14, 2021

Likqez commented Mar 14, 2021

XiXiongMaoXiong commented Mar 16, 2021 • edited Loading

scrouthtv commented Apr 19, 2021 • edited Loading

kriegaex commented Apr 19, 2021

scrouthtv commented Apr 19, 2021

kriegaex commented Apr 19, 2021 • edited Loading

ArcticLampyrid commented May 3, 2021

DerpyDashie commented Aug 19, 2021

ArcticLampyrid commented Aug 24, 2021

kriegaex commented Aug 27, 2021

ghost commented Sep 1, 2021

sky-clr commented Dec 12, 2022

ArcticLampyrid commented Dec 12, 2022

jbartok commented Sep 15, 2023

Drezir commented Aug 11, 2020 •

edited

Loading

big-guy commented Aug 12, 2020 •

edited

Loading

kriegaex commented Oct 9, 2020 •

edited

Loading

kriegaex commented Oct 9, 2020 •

edited

Loading

mahdi-malv commented Nov 2, 2020 •

edited

Loading

XiXiongMaoXiong commented Mar 16, 2021 •

edited

Loading

scrouthtv commented Apr 19, 2021 •

edited

Loading

kriegaex commented Apr 19, 2021 •

edited

Loading