Hey all, Just an update for those experiencing the same issue:
I was able to get around the problem by using "activator start" instead of "activator run". This essentially starts the app in production mode -- you can still debug and do everything you could with "run", but it doesn't suffer from the same issue. I'm guessing this is a problem with Activator specifically. On Wednesday, September 23, 2015 at 6:00:30 PM UTC-4, aedb wrote: > > Hey all, > > I just updated to Java 8 and I'm also seeing this issue. Sadly, adding > "fork := true" to the build.sbt file *doesn't* helps at all. Here's what > I know: > > 1. This issue *only* occurs in Play when running with the "activator run" > command > 2. The issue does *not* occur when deploying the rest app and running it > as a jar file > 3. This issue does *not* occur in unit tests > > I'm running: > > - Activator 1.3.2 > - Play 2.3.8 > - OrientDB 2.1 > - Java 8 > > Does anybody have thoughts on how to fix this? Would be a great help! > > Error dump: > > play.api.Application$$anon$1: Execution exception[[RuntimeException: > GraphFactory could not instantiate this Graph implementation > [com.tinkerpop.blueprints.impls.orient.OrientGraph].]] > at play.api.Application$class.handleError(Application.scala:296) > ~[play_2.11-2.3.8.jar:2.3.8] > at play.api.DefaultApplication.handleError(Application.scala:402) > [play_2.11-2.3.8.jar:2.3.8] > at > play.core.server.netty.PlayDefaultUpstreamHandler$$anonfun$14$$anonfun$apply$1.applyOrElse(PlayDefaultUpstreamHandler.scala:205) > > [play_2.11-2.3.8.jar:2.3.8] > at > play.core.server.netty.PlayDefaultUpstreamHandler$$anonfun$14$$anonfun$apply$1.applyOrElse(PlayDefaultUpstreamHandler.scala:202) > > [play_2.11-2.3.8.jar:2.3.8] > at > scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:36) > [scala-library-2.11.7.jar:na] > Caused by: java.lang.RuntimeException: GraphFactory could not instantiate > this Graph implementation > [com.tinkerpop.blueprints.impls.orient.OrientGraph]. > at com.tinkerpop.blueprints.GraphFactory.open(GraphFactory.java:50) > ~[blueprints-core-2.6.0.jar:na] > at > com.kickstand.data.models.GraphDatabaseHelper$.InTx(GraphModel.scala:32) > ~[core-1.0-SNAPSHOT.jar:na] > at > com.kickstand.services.FriendService.getFriendList(FriendService.scala:417) > ~[core-1.0-SNAPSHOT.jar:na] > at > controllers.FriendController$$anonfun$getFriends$1$$anonfun$apply$1.apply(FriendController.scala:30) > > ~[classes/:1.3.12] > at > controllers.FriendController$$anonfun$getFriends$1$$anonfun$apply$1.apply(FriendController.scala:27) > > ~[classes/:1.3.12] > Caused by: java.lang.reflect.InvocationTargetException: null > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > ~[na:1.8.0_60] > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > > ~[na:1.8.0_60] > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > > ~[na:1.8.0_60] > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > ~[na:1.8.0_60] > at com.tinkerpop.blueprints.GraphFactory.open(GraphFactory.java:43) > ~[blueprints-core-2.6.0.jar:na] > Caused by: java.lang.NoClassDefFoundError: Could not initialize class > com.orientechnologies.orient.core.db.ODatabaseRecordThreadLocal > at > com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.activateOnCurrentThread(ODatabaseDocumentTx.java:2800) > > ~[orientdb-core-2.1.1.jar:2.1.1] > at > com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.<init>(ODatabaseDocumentTx.java:171) > > ~[orientdb-core-2.1.1.jar:2.1.1] > at > com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.<init>(ODatabaseDocumentTx.java:165) > > ~[orientdb-core-2.1.1.jar:2.1.1] > at > com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.openOrCreate(OrientBaseGraph.java:1847) > > ~[orientdb-graphdb-2.1.1.jar:2.1.1] > at > com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.<init>(OrientBaseGraph.java:172) > > ~[orientdb-graphdb-2.1.1.jar:2.1.1] > > On Friday, January 23, 2015 at 11:09:42 AM UTC-5, Bertrand Quenin wrote: >> >> Hi Andrey, >> >> Thanks for your reply but actually the problem was different. I was >> running from sbt with the "run" command. However, sbt was not setup to use >> forkedJvm mode. I just needed to add: >> >> fork := true >> >> to my build.sbt and it fixed everything. >> >> Regards, >> BQ. >> >> -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
