 14 | to know whether there is a change or an outlook regarding the topic: Is it possible, or planned, to run ... . then i erase this line then i could able to run the explorer and server. EntityManagerFactory emf = Persistence.createEntityManagerFactory("objectdb:test.mem"); After running program it gives |
14 | " />
When enabled, embedded mode runs automatic server at the background ... file. May be, this is the cause of the problem! The explorer requires objectdb.jar to run |
14 | )
at com.tradeunafraid.TradeUnafraid.run(TradeUnafraid.groovy:64)
at com.tradeunafraid.TradeUnafraid$run.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall |
14 | The Explorer should support running ObjectDB tools (such as ObjectDB Server and ObjectDB Doctor) visually within the Explorer. This is one of the features that have been supported by the old Explorer of ObjectDB 1. It has been temporarily removed due to incompatibility with the new ObjectDB 2 code base. |
14 | ObjectDB support wrote elsewhere: ... you do not need the Enhancer agent, since you use build time emhancement, but GlassFish invokes it automatically. Currently there is no setting in ObjectDB to disable the enhancer agent ... Q: Does run time enhancer due to GlassFish/Payara |
14 | Hi, When using both JMX Remote and ODB as agent, there is a problem to run JVM at all. All this is on Debian linux with two different JVM's. Let me show you some logs from console: - pure java
homplex@homplex01:~$ java -version
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8 |
14 | It seems that there is a bug in logging mechanism, if you try to start the database which is already started it starts filing the log continuously until it runs out of space on disk. How to check is the database runing from command promt. regards. This is caused by a recurring attempt to start |
14 | Hi I have created in Eclipse a new plugin from existing jar file and than I tried to enhance my classes (using Ehancer from that new bundle), however I got an error : [ObjectDB 2.2.8_02] Package datamodel.core.base is not found by the enhancer (error 108) The Enhancer was run in the following way |
14 | We are getting massively different results on field loading between explicit post-compile enhancement and automatic run-time enhancement. Testing exactly where and when the results are different for our demo web app is a very time consuming task, and very difficult, it means testing literally 100s |
14 | ();
else
onRollback(); If anyone can see what is going wrong I would really like to know. I am running |