[GRADLE-2871] Gradle 1.7 build fails because of java.net.BindException: Permission denied Created: 15/Aug/13 Updated: 27/Aug/14 Resolved: 27/Aug/14 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | 2.2-rc-1 |
Type: | Task | ||
Reporter: | Gradle Forums | Assignee: | Luke Daley |
Resolution: | Fixed | Votes: | 9 |
Description |
I am trying to use Gradle 1.7 to build my OpenShift Java projects. Everything worked with 1.6 version but with 1.7 version I am getting following exception remote: 10:05:22.820 [ERROR] [org.gradle.BuildExceptionReporter] |
Comments |
Comment by Gradle Forums [ 15/Aug/13 ] |
Looks like a problem related to the network configuration of the box that's running the build (or the permissions of the Gradle process). Apparently it's not possible to open a local UDP socket. |
Comment by Gradle Forums [ 15/Aug/13 ] |
Hello Peter, I looked at Gradle source code and exception is coming at this line [1]https://github.com/gradle/gradle/blob... . This class did not exist in Gradle 1.6. In that line you are creating an instance of DatagramSocket. As you are not specifying any host or port it will arbitrary use any port number and probably use 0.0.0.0 as Ip address. This does not work in OpenShift as you can only bind to $OPENSHIFT_INTERNAL_IP and ports between 15000 to 65535. Is it feasible that I can override these values? Thanks |
Comment by Shekhar Gulati [ 15/Aug/13 ] |
Hello, If you want to reproduce this issue I have created an OpenShift quickstart which can help you do that. Please look at https://github.com/shekhargulati/gradle-1.7-openshift-quickstart Thanks |
Comment by Marcel Overdijk [ 10/Apr/14 ] |
+1 (now have to downgrade form 1.11 to 1.6 to get Gradle working on openshift) |
Comment by Albert Gorski [ 25/Apr/14 ] |
+1 (one year old bug guys ... time to fix ?! ) |
Comment by Adam Murdoch [ 28/Apr/14 ] |
We'd welcome a pull request to fix this. There's an initial pull request here but it needs some changes: https://github.com/gradle/gradle/pull/242 If you'd like to help out with the fix, take a look at the discussion in that pull request, make the changes suggested there and submit a new pull request. |
Comment by Marcel Overdijk [ 01/Jul/14 ] |
Is it worth checking if this issue is solved in 2.0 release? Or can I better safe the time? |
Comment by Luke Daley [ 01/Jul/14 ] |
It's not fixed. |
Comment by Marcel Overdijk [ 01/Jul/14 ] |
Thanks for confirming Luke. I was hoping maybe some internal stuff in 2.0 was changed which could have resolved this automatically. Unfortunately not, and thus have to keep using Maven. |
Comment by Marcel Overdijk [ 10/Jul/14 ] |
For reference here the link to the PR: https://github.com/gradle/gradle/pull/292 to track required change on github. |