# Gradle hangs when I run jettyRun on quickstart webApplication sample

**URL:** <https://discuss.gradle.org/t/gradle-hangs-when-i-run-jettyrun-on-quickstart-webapplication-sample/1982>\
**Category:** Old Forum Archive\
**Created:** [November 19, 2011, 4:27pm UTC](https://discuss.gradle.org/t/gradle-hangs-when-i-run-jettyrun-on-quickstart-webapplication-sample/1982 "2011-11-19T16:27:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bouiaw](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/bouiaw/32/122_2.png) [@Bouiaw](https://discuss.gradle.org/u/Bouiaw)\
**Post date:** [November 19, 2011, 4:27pm UTC](https://discuss.gradle.org/t/gradle-hangs-when-i-run-jettyrun-on-quickstart-webapplication-sample/1982/1 "2011-11-19T16:27:00Z")

</div>

Hi,

With Gradle 1.0-milestone-6 (but also with 1.0-milestone-5), Gradle hangs when I run “gradle jettyRun” on quickstart webApplication sample

Output is :

C:\Apps\gradle\samples\webApplication\quickstart\>gradle jettyRun

:compileJava UP-TO-DATE

:processResources UP-TO-DATE

:classes UP-TO-DATE

> Building \> :jettyRun

And it hangs forever. I am under Windows 7 64 bits, not behind a proxy and have no firewall. I tested this on 2 computers, and the same issue occured.

Regards

---

<div class="post-metadata">

**Author:** ![adammurdoch](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/adammurdoch/32/17_2.png) [@adammurdoch](https://discuss.gradle.org/u/adammurdoch)\
**Post date:** [November 22, 2011, 7:00pm UTC](https://discuss.gradle.org/t/gradle-hangs-when-i-run-jettyrun-on-quickstart-webapplication-sample/1982/2 "2011-11-22T19:00:00Z")

</div>

The build waits for jetty to be stopped. And Jetty’s sitting there waiting to serve up HTTP requests.

Though, it looks like the sample pick an arbitrary port to run Jetty on, and doesn’t tell you which one. Which makes it pretty useless. You’ll need to remove these lines from the sample build.gradle:

```gradle
[jettyRun, jettyRunWar]*.doFirst {
    project.httpPort = portFinder.nextAvailable
    project.stopPort = portFinder.nextAvailable
}

```

You can also tweak the ‘httpPort = 8163’ setting to choose which port you’d like Jetty to listen on.

---

<div class="post-metadata">

**Author:** ![Bouiaw](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/bouiaw/32/122_2.png) [@Bouiaw](https://discuss.gradle.org/u/Bouiaw)\
**Post date:** [November 22, 2011, 11:29pm UTC](https://discuss.gradle.org/t/gradle-hangs-when-i-run-jettyrun-on-quickstart-webapplication-sample/1982/3 "2011-11-22T23:29:00Z")

</div>

Perfect, it works. Thanks.

---

<div class="post-metadata">

**Author:** ![adammurdoch](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/adammurdoch/32/17_2.png) [@adammurdoch](https://discuss.gradle.org/u/adammurdoch)\
**Post date:** [November 23, 2011, 1:04am UTC](https://discuss.gradle.org/t/gradle-hangs-when-i-run-jettyrun-on-quickstart-webapplication-sample/1982/4 "2011-11-23T01:04:00Z")

</div>

I’ve updated the sample, too.

---

<div class="post-metadata">

**Author:** ![adammurdoch](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/adammurdoch/32/17_2.png) [@adammurdoch](https://discuss.gradle.org/u/adammurdoch)\
**Post date:** [November 23, 2011, 1:05am UTC](https://discuss.gradle.org/t/gradle-hangs-when-i-run-jettyrun-on-quickstart-webapplication-sample/1982/5 "2011-11-23T01:05:00Z")

</div>

Oh, and running ‘gradle jettyRun’ task displays this now:

```gradle
:compileJava
:processResources
:classes
> Building > :jettyRun > Listening on port 8080

```

---

<div class="post-metadata">

**Author:** ![Bouiaw](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/bouiaw/32/122_2.png) [@Bouiaw](https://discuss.gradle.org/u/Bouiaw)\
**Post date:** [November 23, 2011, 7:51pm UTC](https://discuss.gradle.org/t/gradle-hangs-when-i-run-jettyrun-on-quickstart-webapplication-sample/1982/6 "2011-11-23T19:51:00Z")

</div>

Nice, I am going to test Gradle on a real life project and blog about this from my “Maven expert user” point of view.