7 | Check for index existence ?) and the information on this manual page. support Support I've added the args to my tomcat server |
7 | ObjectDB 2.x is working without any activation code the application whichi is using Tomcat 7.0 and getting the following exception 06-Sep 14:30:01 |
7 | Embedded server featureIs it safe to use this wonderful and undocumented feature in production, and rely on its problem-free functioning? For my case it would be really beneficial: 1 physical server with SSD 1 JVM running on it 2 web applications on Tomcat 1 ObjectDB Server deployed, in embedded server mode 2 ObjectDB |
7 | ODB 2 JDO enhancementIf I label a class @PersistenceCapable do I still need to explicitly enhance? Do I need a package.jdo file? This question relates to experiences with ODB 1, in which one has to: a) create a package.jdo, and b) run the Enhancer In my experience, using this with Tomcat, and running the enhancer in |
7 | Listing large number of complicated objects with paging. part is that running this query needs lots of memory at tomcat side (attached screenshot) and after running it 3-4 |
7 | ObjectDB shuts down to keep the necessary amount of RAM available for itself. I experienced something similar when my app server (Tomcat |
1 | NPE when doing a find()I added a simple User entity during Tomcat startup: class User { @Id @GeneratedValue private long id; @Basic(optional = false) private String firstName; private String middleName; @Basic(optional = false) private String lastName; } Everything works fine until I restart the server, which does a em |
1 | Error in production. Failed to commit transaction: Unexpected database state: BTree -152 is not found.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util |
1 | Embedded Database ReplicationAs we all know, embedded databases out-perform server databases on every occasion. The problem with embedded databases is that theyre difficult to scale. If I were to create an entire enterprise web application within a single jar file using embedded tomcat and embedded objectdb I would run into |
1 | com.objectdb.o.InternalException: java.lang.NullPointerException.getSingleResult(JpaQuery.java:755) ... at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run |
