Hi, Is there an exception logged with the message? The inner message is an INFO message, so in itself it should be benign. I'd expect the Transaction Synchronization Registry to only be available in JEE, so I don't think there is anything wrong with your environment.
I'm at a loss regarding the javaAccessorNotSet message though. If there is an exception printed, maybe the stack trace will shed some light on the problem. It might also be good to enable trace for OpenJPA.Enhance to make sure the javaagent did enhance your entities. Hope this helps, -mike On Wed, Jul 27, 2011 at 10:39 AM, M. Walter <marc.wal...@sbb.ch> wrote: > Does anyone know what's wrong when this error occurs and how I can fix it? > > I get this message when I test my EJB DAO with JUnit. I create a new entity > and persist it using H2 in-memory database. Next I load the entity from the > database again. When I invoke a getter method from the entity the message > is > printed out. The JUnit test is executed with javaagent runtime enhancement. > > Here are some loggings: > 218 resource-local-pu INFO [main] openjpa.Runtime - Starting OpenJPA > 1.2.3-SNAPSHOT > 331 resource-local-pu INFO [main] openjpa.jdbc.JDBC - Using dictionary > class "org.apache.openjpa.jdbc.sql.H2Dictionary". > 0 [main] INFO server.persistence.dao.MyDaoBean - Persisting new entity with > number [638]. > 260 [main] INFO server.persistence.dao.MyDaoBean - Finding entity with > primary key [1]. > > >>> now I invoke entity.getNumber() <<< > > Jul 27, 2011 5:32:19 PM null null > SEVERE: javaAccessorNotSet > 4725 resource-local-pu INFO [main] openjpa.Runtime - Unable to locate > Transaction Synchronization Registry. > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/openjpa-Runtime-Unable-to-locate-Transaction-Synchronization-Registry-tp6626607p6626607.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
