#1180 confirmed

Session ID changes with suspended requests

Reported by Stikkos | October 22nd, 2011 @ 05:10 PM

When a play app is invoked for the first time (so when no session cookie exists yet), and the request gets suspended, the session ID gets changed after each await() call.

    public static void index() throws InterruptedException, ExecutionException {
        Logger.info("Test app index started with session ID [%s]", session.getId());
        Promise promise1 = new TestJob().now();
        Logger.info("promise1 finished with session ID [%s]", session.getId());
        Promise promise2 = new TestJob().now();
        Logger.info("promise2 finished with session ID [%s]", session.getId());
        Logger.info("Test app index finished with session ID [%s]", session.getId());

Will result in:
18:06:10,171 INFO ~ Application 'test-app' is now started !
18:06:10,266 INFO ~ Test app index started with session ID [3d7ba1b3-19fe-4e4f-b397-d2952f166bf6]
18:06:10,276 INFO ~ doJob started on [Sat Oct 22 18:06:10 BST 2011]
18:06:12,277 INFO ~ doJob finished on [Sat Oct 22 18:06:12 BST 2011]
18:06:12,281 INFO ~ promise1 finished with session ID [85d32ea0-5492-4445-b9aa-67401530ce8f]
18:06:12,285 INFO ~ doJob started on [Sat Oct 22 18:06:12 BST 2011]
18:06:14,286 INFO ~ doJob finished on [Sat Oct 22 18:06:14 BST 2011]
18:06:14,291 INFO ~ promise2 finished with session ID [fbd74b00-bbdc-41c9-8986-719d43d16c9f]
18:06:14,294 INFO ~ doJob started on [Sat Oct 22 18:06:14 BST 2011]
18:06:16,295 INFO ~ doJob finished on [Sat Oct 22 18:06:16 BST 2011]
18:06:16,300 INFO ~ promise3 finished with session ID [a68b894b-05e5-44c0-9d68-b11d3130e165]
18:06:16,300 INFO ~ Test app index finished with session ID [a68b894b-05e5-44c0-9d68-b11d3130e165]

The SessionId changes after every await(promise) invocation

Framework version: 1.2.3
Platform you're using: os x

Reproduction steps:
Unzip attached test-app directory
play run
clear cookies in browser
go to localhost:9000
check the logs

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.