i just tested it using our integration test and it worked for me.
Your error seems to indicate that you may have two EhCachePlugin configured, so please make sure
you do not have a second plugin registered somewhere (ie in your play.plugins).
On Saturday, March 31, 2012 4:32:51 PM UTC-4, KajMagnus wrote:
I'm getting an "Cache play already exists" in EhCachePlugin when I
deploy my Play 2 app on my production machine.
I deploy by building Play with "play dist" and unzipping the generated
zip file and rsync:ing it to the production server.
I've worked around the problem by disabling the ehcache, in the
application.conf file, like so:
(( But perhaps soon you'll need to specify:
instead, because there's either a documentation bug or a code bug in
(Perhaps someone else runs into the same problem,
or perhaps the Play 2 devs aren't aware about it yet,
hence this email.)
(I found some old threads related to Play 1 when I searched for "Cache
play already exists", but I got the impression that that issue had
already been fixed. So perhaps that was another issue.)
Here's the error and stack trace:
[ec2-user@dw0azewdbpv11danny debiki.se]$ Play server process ID is
Oops, cannot start the server.
net.sf.ehcache.ObjectExistsException: Cache play already exists