This behavior is exactly what I get under Windows 7 sometimes while building gradle itself and it runs some of the unit and/or integration tests, so yes, this type of issue has been seen before.
-Spencer --- On Sat, 8/27/11, Merlyn Albery-Speyer <[email protected]> wrote: From: Merlyn Albery-Speyer <[email protected]> Subject: Re: [gradle-user] Gradle on Win7: could not write to socket To: [email protected] Date: Saturday, August 27, 2011, 12:33 PM If you create a simple script to listen on that port can you connect to it successfully? On Aug 26, 2011 2:09 AM, "Strong Liu" <[email protected]> wrote: > same error on RHEL x86-64 > > anyone? > > ----------- > Strong Liu <[email protected]> > http://hibernate.org > http://github.com/stliu > > On May 24, 2011, at 3:43 PM, Markus Schlichting wrote: > >> Hi, >> I'm trying to use gradle (ms-3) on Windows 7 for the first time and get a >> wierd behavior. Upon trying to use the java plugin to run my tests, i get: >> >> Could not dispatch message >> org.gradle.messaging.remote.internal.EndOfStreamEvent >> @0 to socket connection at tcp://localhost:59178 with tcp://localhost:59179. >> Discarding message. >> >> org.gradle.api.GradleException: Could not write message to >> 'tcp://localhost:5917 >> 9'. >> >> Has anyone seen this before ? >> >> The windows firewall is diabled. >> >> cheers >> Markus >> >> >> <canoo_signature.png> >> Markus Schlichting >> Canoo Engineering AG >> Kirschgartenstrasse 5 >> CH-4051 Basel >> Tel: +41 61 228 94 44 >> Fax: +41 61 228 94 49 >> [email protected] >> http://www.canoo.com >> >> >
