#1204 new

Error occured when await used in Controller in Play 1.2.3

Reported by mahidhar | November 2nd, 2011 @ 03:38 PM

Hi ,

I am making asynchronous API calls to retrieving the data. For this i have used await method in the controller level. After adding this method i have getting the below exception.

Can any on help me on this issue.

Oops: UnexpectedException
An unexpected error occured caused by exception UnexpectedException: While applying class play.classloading.enhancers.ContinuationEnhancer on controllers.Facebook

play.exceptions.UnexpectedException: While applying play.CorePlugin@cf710e on controllers.Facebook

  at play.plugins.PluginCollection.enhance(PluginCollection.java:454)
  at play.classloading.ApplicationClasses$ApplicationClass.enhance(ApplicationClasses.java:208)
  at play.classloading.ApplicationClassloader.loadApplicationClass(ApplicationClassloader.java:157)
  at play.classloading.ApplicationClassloader.getAllClasses(ApplicationClassloader.java:417)
  at play.Play.start(Play.java:485)
  at play.Play.detectChanges(Play.java:599)
  at play.Invoker$Invocation.init(Invoker.java:186)
  at Invocation.HTTP Request(Play!)

Caused by: play.exceptions.UnexpectedException: While applying class play.classloading.enhancers.ContinuationEnhancer on controllers.Facebook

  at play.CorePlugin.enhance(CorePlugin.java:296)
  at play.plugins.PluginCollection.enhance(PluginCollection.java:451)
  ... 7 more

Caused by: java.lang.IllegalArgumentException: Invalid operand (must be a signed byte): 128

  at org.objectweb.asm.util.CheckMethodAdapter.checkSignedByte(Unknown Source)
  at org.objectweb.asm.util.CheckMethodAdapter.visitIntInsn(Unknown Source)
  at org.apache.commons.javaflow.bytecode.transformation.asm.ContinuationMethodAdapter.visitMethodInsn(ContinuationMethodAdapter.java:279)
  at org.objectweb.asm.tree.MethodInsnNode.accept(Unknown Source)
  at org.objectweb.asm.tree.InsnList.accept(Unknown Source)
  at org.objectweb.asm.tree.MethodNode.accept(Unknown Source)
  at org.apache.commons.javaflow.bytecode.transformation.asm.ContinuationMethodAnalyzer.visitEnd(ContinuationMethodAnalyzer.java:140)
  at org.objectweb.asm.ClassReader.accept(Unknown Source)
  at org.objectweb.asm.ClassReader.accept(Unknown Source)
  at org.apache.commons.javaflow.bytecode.transformation.asm.AsmClassTransformer.transform(AsmClassTransformer.java:49)
  at org.apache.commons.javaflow.bytecode.transformation.asm.AsmClassTransformer.transform(AsmClassTransformer.java:41)
  at play.classloading.enhancers.ContinuationEnhancer.enhanceThisClass(ContinuationEnhancer.java:65)
  at play.CorePlugin.enhance(CorePlugin.java:293)
  ... 8 more

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