#355 ✓wontfix
sanity

Play tries to use port 9000, which is used by xdebug in Eclipse

Reported by sanity | October 29th, 2010 @ 01:41 PM

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.

Framework version: 1.1RC3
Platform you're using: OSX, Eclipse Helios

Reproduction steps:
Create a play project, eclipsify it, and import it into Eclipse
Try running the project, note that there is the following error and the app immediately exits:

22:54:49,434 ERROR ~ Could not bind on port 9000

The Problem:
By default Eclipse listens on port 9000 for "xdebug".

Workaround:
Go into Eclipse preferences and modify the xdebug port from 9000 to another number (I used 9001)

Fix:
Since Play's instructions suggest that Play should work out of the box with Eclipse, I would strongly recommend that Play use a port other than 9000 which is not used by Eclipse, and which does not require a change to Eclipse's configuration.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

Referenced by

Pages