Play 2.6.17 released

The Play Team is pleased to announce the release of Play Framework 2.6.17. This is the latest stable release of Play.

Yep, two releases at the same week. But it was for a good reason. This one is a very small release following 2.6.16 to add a fix important to Lagom Framework.

Getting Play

  1. To start a new project, visit
  2. To upgrade an existing Play 2.6 project, edit your project/plugins.sbt file and set the sbt-plugin to 2.6.17.
  3. To update an older Play project, take a look at the Play 2.6 Migration Guide.


Play 2.6.17 brings mainly a fix to enable users to configure the application to start even when a database is not available yet. There is also a fix in our docs. For more details see the full list of changes and 2.6.17 issues on GitHub.


Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Play core team’s efforts. Lightbend offers commercial support for Play.

Special thanks to the following contributors who helped with this release: Marcos Pereira and NickBlow.

Could you elaborate a bit on the database change please? What was the behavior before the fix and how has it changed? Was a negative initializationFailTimeout value previously ignored?

Hi @VeryBueno,

Yes, previously a negative value was ignored because Play was trying to validate the database configuration by accessing that database. That proves not only if the configuration was well-formed (for example, correct URL format for that database), but also if the database was effectively available.

The change is not to check database availability unless configured to do so (the default in 2.6.17), but only if the configuration is well-formed. So now a negative value will be respected, and the application should start as configured. It is essential to explain that there are some cases where a connection is necessary (like checking evolutions) and then it will fail at some point.


Thanks Marcos. This release might solve some of the issues we’re seeing in our deployments.

Are there any plans to backport this to previous Play versions, specifically 2.5.X and 2.4.X?


Hi @VeryBueno,

No, we are not planning to backport this to 2.5.x or 2.4.x.


Any reason that this release is not listed here ?

1 Like