#1665 new
David Morana

Play service deployed as WAR on tomcat 7 eventually slows way down

Reported by David Morana | May 1st, 2013 @ 05:24 PM

Framework version: 1.2.5

Platform you're using: Linux with tomcat 7.0.34

Reproduction steps:
deploy a play web service war to tomcat and see if it slows down

I created a web service using OpenText LAPI and Java jre7
I deployed it to the tomcat server and it eventually slows down.
I found this error in the log:
May 01, 2013 12:50:16 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/LisaWebSvc] appears to have started a thread named [net.sf.ehcache.CacheManager@33055eb5] but has failed to stop it. This is very likely to create a memory leak.

I also found this link from G. Bort on google groups regarding a similar error:

Is there any way to improve the performance of the WAR?
I'm going to run the play code as a service; that way if it slows down, I'll know it's a tomcat issue.
Meanwhile, can you tell me where in the play source I should be looking? You mentioned ThreadLocal variables might be the culprit.

Thank you,

Comments and changes to this ticket

  • TonyaMartinez

    TonyaMartinez December 22nd, 2017 @ 10:22 AM

    Please help with assignment writers australia to update that when we get the repaired version. As play work is still in maintenance mode and it is not working properly as it should be. Maybe due to this mode, I think. So please let us know when we will have the latest version.

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.