#821 ✓resolved
Marcin Cetnarski

Having @OnApplicationStart job and database evolution causes null on first request

Reported by Marcin Cetnarski | May 11th, 2011 @ 02:10 PM

Handling of InvalidDatabaseRevision is not succeeded.


public static void serve500(Exception e, ChannelHandlerContext ctx, HttpRequest nettyRequest) {

    Logger.trace("serve500: begin");
    HttpResponse nettyResponse = new DefaultHttpResponse(HttpVersion.HTTP_1_1, HttpResponseStatus.INTERNAL_SERVER_ERROR);
    if (exposePlayServer) {
        nettyResponse.setHeader(SERVER, signature);

    Request request = Request.current();

request is null so NullPointerException is thrown on

    String format = request.format;

Framework version: 1.2.1
Platform you're using: OS X 10.6

Reproduction steps:
Run application with evolution applied on empty database. Bootstrap job is needed with annotation @OnApplicationStart (might be empty class). If Bootstrap job is removed then it works fine.

It worked with play 1.2

Comments and changes to this ticket

  • Erwan Loisant

    Erwan Loisant June 1st, 2011 @ 02:25 PM

    • State changed from “new” to “resolved”

    This has been fixed in 1.2.2RC1.

  • Brandon Riley

    Brandon Riley April 22nd, 2017 @ 07:10 PM

    This site proves that it is actual one of the best essay-services-review.com site. Congratulation you have complete your one year on the internet. Now you have more followers, more fame, and more success. I really appreciate the consistency of your efforts and devotion which you put here to become your page one of the number 1.

  • EuricanaCiara

    EuricanaCiara January 25th, 2018 @ 05:19 AM

    In some cases you will commit an error in your advancement contents, and they will fall flat. For this situation, Play will check your database diagram as being in a conflicting state and will ask you to physically resolve the issue before proceeding.
    visit: Essay Help Online

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