#2165 new
greenLED

[1.5.0] No route able to invoke action WebSocket.ChatRoomSocket.join was found

Reported by greenLED | April 15th, 2018 @ 07:40 PM

Hi. I tried to test the sample chat app in Play! 1.5.0 and got an Internal Server Error when generating the reverse route to the websocket controller action. Tried with the trivial example from documentation in a new project and it also failed. Checked the same example app in Play! 1.4.4 and it's working fine.

Framework version: 1.5.0
Java version: openjdk 1.8
Platform you're using: Ubuntu 16.04

Reproduction steps:

  1. Download and install Play! 1.5.0 from https://downloads.typesafe.com/play/1.5.0/play-1.5.0.zip
  2. Run the Chat example app
  3. Try to use the websockets example

Details:

This is the error stack trace:

Internal Server Error (500) for request GET /websocket/room?user=asd

No route found (In /app/views/WebSocket/room.html around line 52)
No route able to invoke action WebSocket.ChatRoomSocket.join was found.

play.exceptions.NoRouteFoundException: No route found
    at play.templates.BaseTemplate.throwException(BaseTemplate.java:79)
    at play.templates.GroovyTemplate.internalRender(GroovyTemplate.java:292)
    at play.templates.Template.render(Template.java:28)
    at play.templates.GroovyTemplate.render(GroovyTemplate.java:230)
    at play.mvc.results.RenderTemplate.<init>(RenderTemplate.java:28)
    at play.mvc.Controller.renderTemplate(Controller.java:804)
    at play.mvc.Controller.renderTemplate(Controller.java:782)
    at play.mvc.Controller.render(Controller.java:843)
    at controllers.WebSocket.room(WebSocket.java:20)
    at play.mvc.ActionInvoker.invokeWithContinuation(ActionInvoker.java:539)
    at play.mvc.ActionInvoker.invoke(ActionInvoker.java:476)
    at play.mvc.ActionInvoker.invokeControllerMethod(ActionInvoker.java:470)
    at play.mvc.ActionInvoker.invokeControllerMethod(ActionInvoker.java:437)
    at play.mvc.ActionInvoker.invoke(ActionInvoker.java:160)
    at Invocation.HTTP Request(Play!)

Regards,
Juan Carlos

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.

Pages