#943 ✓resolved
Mark Piper

Autotest: Connection Refused (starts too early)

Reported by Mark Piper | June 28th, 2011 @ 02:33 PM | in 1.3 (closed)

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.2.1
Platform you're using: Ubuntu


We have been seeing intermittent issues with java.net.ConnectExceptions when starting auto-test. On investigation, the problem appears to be that the line that auto-test watches for in the logs ("/@tests to run the tests") is actually output by TestRunnerPlugin.onApplicationReady() before the server is properly started up and ready to receive requests. This normally happens soon enough after to not be a problem (we've been using Play for 3 months and only just started hitting this problem), but every now and again it causes the ConnectException.

We have fixed the issue by simply amending framework/pym/play/commands/base.py to watch for the line "Listening for HTTP" (output by play.server.Server when it actually binds to the port). This seems to have resolved the problems.

On a related note, is it right that a plugin's onApplicationReady() method is called before the server is actually ready to accept requests?

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