About logging

191-200 of 200Refresh
Forum
0

database migration

.. version is on another server, the log i attached is generated by wildfly 10.1 server. Both wildfly
Forum
0

Deadlock problems solved - a suggestion

Thanks to the new logging capability, I have managed to solve all the deadlock problems, as they were a result of Objectdb encountering new classes in multi-threaded code.  I have a suggestion that might be useful for other users - how about an Ant task that, given a database URL, performs
Forum
0

Dependency from enhanced classes to the objectDB library

“com.btc.ep.base.dal.impl” to enhance the classes. The log of the enhancer is correct. But in
Forum
0

Deploying a BIRT Project using ObjectDB onto Tomcat

the ODA dataSource extension (%oda.data.source.id). Check the workspace log file for any problems
Forum
0

Deploying objectdb.jar to karaf 4.0.7 seems to fail

Hello, I'm evaluating ObjectDB for a future use in an OSGi project using Apache Karaf 4.0.7 (and later) as OSGi container. When I try to deploy the objectdb.jar file to Karaf (copy the jar file to the deploy folder in Karaf) I get a stacktrace in the Karaf log file with the following message
Forum
0

Does run time enhancer due to GlassFish/Payara do anything that would affect loaded compile-time entity classes ?

do anything that would affect loaded compile-time enhanced entity classes (other than just logging, typically just info
Forum
0

dual access

direct SQL coding? ObjectDB doesn't support SQL but JDOQL and JPQL (the later is very similar to SQL). Queries can be logged before execution. cpanon
Forum
0

Enhancement API - NullPointerException

) at my.package.Main.main(Main.java:34) I checked the logs, but there is no more information
Forum
0

Error 363 - Failed to read value of inverse relationship

and submission deadline. The error log is as follows:   WARNING: DTX5014: Caught exception in
Issue
0

Error 990 when querying a class with persistence-capable-superclass

is hidden by this internal cleanup exception. You may find more information in the log file