StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POPlayframework standalone jobs connect to database twice
primarykey
Id
12881514
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2012-10-14T10:49:05.870
FavoriteCount
0
LastActivityDate
2012-10-15T13:11:06.147
LastEditDate
LastEditorUserId
0
OwnerUserId
156906
ParentId
0
PostTypeId
1
Score
0
ViewCount
335
LastEditorDisplayName
text
Body
I have a standalone job in Play 2.0.4 that I want to run on Heroku as described in <a href="https://github.com/jamesward/play2-scheduled-job-demo" rel="nofollow">https://github.com/jamesward/play2-scheduled-job-demo</a> I start the application just like in the samples: <pre><code>public class QueueWorker { public static void main(String[] args) { Application application = new Application(new File(args[0]), QueueWorker.class.getClassLoader(), null, Mode.Dev()); Play.start(application); } } </code></pre> But now, judging from the logs, Play connects to the database twice for some reason and EhCache fails the second time because it the name is already registered: <pre><code>[[37minfo[0m] play - database [default] connected at jdbc:mysql://localhost/myproject?characterEncoding=UTF-8 [[37minfo[0m] play - database [default] connected at jdbc:mysql://localhost/myproject?characterEncoding=UTF-8 Exception in thread "main" net.sf.ehcache.ObjectExistsException: Cache play already exists at net.sf.ehcache.CacheManager.addCache(CacheManager.java:990) at play.api.cache.EhCachePlugin.x$3(Cache.scala:111) at play.api.cache.EhCachePlugin.cache(Cache.scala:109) at play.api.cache.EhCachePlugin.onStart(Cache.scala:127) at play.api.Play$$anonfun$start$1.apply(Play.scala:60) at play.api.Play$$anonfun$start$1.apply(Play.scala:60) at scala.collection.LinearSeqOptimized$class.foreach(LinearSeqOptimized.scala:59) at scala.collection.immutable.List.foreach(List.scala:45) at play.api.Play$.start(Play.scala:60) at play.api.Play.start(Play.scala) at jobs.QueueWorker.main(QueueWorker.java:32) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) </code></pre> Interestingly this does not happen when I start the project with the "play run" command. Has anybody got a hint for me what this could be, or how I can debug where it's coming from?
Tags
<playframework><playframework-2.0>
Title
Playframework standalone jobs connect to database twice
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USkeyboardsamurai
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.