#1360 ✓resolved
Johan Miller

Error launching through eclipse using jdk 1.7

Reported by Johan Miller | January 5th, 2012 @ 10:36 AM | 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. WARNING: Do not fill bugs related describing security vulnerabilities. Email directly guillaume dot bort at gmail dot com for that.

Framework version: 1.2.4
Platform you're using: Windows 7 x64

Reproduction steps:
1. Create a new project "play new test".
2. Edit dependecies.yml to include secure module "-play -> secure"
3. Edit routes to import secure module routes "* / module:secure"
4. Go into the created project directory
5. Run "play dependencies" and "play eclipsify"
6. Set jdk 1.7 as the default java environment in eclipse
7. Import the created project into eclipse and run using the launch configuration
8. Open "http://localhost:9000/login" and click "Sign in" button
An error "VerifyError occured : Expecting a stack map frame in method controllers.Secure$Security.authentify(Ljava/lang/String;Ljava/lang/String;)Z at offset 33" should be shown.

This error does not occur when the same application is run from the command line using "play run".

The probleem seems to be with the "-XX:-UseSplitVerifier" jvm flag which was introduced for jdk 1.7. It seems that this flag is automatically added when the application is run from the command line but the flag is not included in the eclipse .launch file under jvm arguments.

After manually adding the flag to applications launch configuration in eclipse the error is no longer shown and the application behaves the same as launched from the command line.

It seems that the fix should be to simply add the flag to the default .launch files in the frameworks resources/eclipse/ directory.

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