#1263 new
Fredrik Rødland

Secure module: LocalVariablesNamesTracer.checkEmpty, constraint violated (1)

Reported by Fredrik Rødland | November 18th, 2011 @ 07:28 AM

I have an application using the secure module to handle login, logout and re-direction to a login-page.

I get the following log-entry for each call to my application:
20111117 09:05:58.991 ERROR play: LocalVariablesNamesTracer.checkEmpty, constraint violated (1) [play-thread-1]

Framework version: play 1.2.3
Platform you're using: mac OS X 10.7

Reproduction steps:
log out of application in the browser
play stop
play start
login to application in browser

I get rid of the error if I - while still being logged into the application in the browser run:
play stop
play start

debugging the app reveals:

  1. localVariables.get() returns an array of hashmap - size 1
  2. the entry is a map of size: 5 containing:
    allowed => true
    remember => false
    username =>
    e => java.lang.UnsupportedOperationException (with no message or stacktrace)
    password =>
  3. these all correspond to variable-names in controllers.Secure.authenticate() from the play secure module.

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.

People watching this ticket