ObjectDB ObjectDB

Internal Website Search

1-10 of 60 resultsRefresh
174

RT Java application recording into 100DB run OOM after a few hours.

Hi, I am running a java application that records data from 100 feeds into 100 different database - this is done is one thread. It works fine several hours - and suddenly i got an out of memory issue (I checked there is no leak in java - I cleared the entity manager every 10 new entity) - I run
65

Date and Time in JPQL and Criteria Queries

such functions as an extension. ObjectDB supports 6 functions for extracting the YEAR, MONTH, DAY, HOUR ... '}) is evaluated to 12. DAY({d '2011-12-31'}) is evaluated to 31. HOUR({t '23:59:00'}) is evaluated to 23 ... <Integer> hour = cb.function("hour", Integer.class, time); Expression<Integer> minute =     cb
22

ObjectDB is opening too many sockets

the default pool 50 on client), and our app crashed after few hours with Too many open connections (55 ... ]> Next occurence couple hours later. strace: Process 33702 attached [pid 26650] 22:12:27.202012 socket ... to start ObjectDB Server on my working computer with MacOS for few hours without connecting
22

Grouping by date()

to 12. DAY({d '2011-12-31'}) is evaluated to 31. HOUR({t '23:59:00'}) is evaluated to 23. MINUTE({t ... ) - Extracts the time part (hour, minute, second, millisecond) as a Date instance. Please try the new ... , Calendar.HOUR was used in resetting the time part instead of Calendar.HOUR_OF_DAY , so AM and PM timestamps
21

TemporalType injection with Calendar using JPA

=5,AM_PM=1,HOUR=7,HOUR_OF_DAY=19,MINUTE=14,SECOND=43,MILLISECOND=31,ZONE_OFFSET=0,DST_OFFSET=3600000 ... =30,DAY_OF_YEAR=150,DAY_OF_WEEK=2,DAY_OF_WEEK_IN_MONTH=5,AM_PM=1,HOUR=7,HOUR_OF_DAY=19,MINUTE=14 ... ,AM_PM=1,HOUR=7,HOUR_OF_DAY=19,MINUTE=14,SECOND=43,MILLISECOND=31,ZONE_OFFSET=0,DST_OFFSET=3600000
18

Occasionally slow requests in load testing

is resized approximately every hour. Each time at the same time we see these slow response incidents ... . It was running great for 6 hours and after that the performance destabilised and did not recover ... . Slow drives also do not explain the behavior we are observing - running fine for 6 hours
16

query on calendar class

:00:00'}", Cdr.class); Query query=em.createQuery("SELECT c FROM Cdr c where HOUR({ts c.start}) >= 23", Cdr.class); Query query=em.createQuery("SELECT c FROM Cdr c where HOUR({t c.start}) >= 23 ... rewrite manual functions. I should use HOUR(c.start) instead of HOUR({t c.start}).Correct query look
14

Date field Index is corrupted due to time change

when Madrid changed clocks one hour back and moved from CEST to CET time. We store time data as ... particular back one hour, may have impact on the operation of Object DB. I'll post additional information ... any records to the DB change the system time zone to B (we used Australia/Brisbane which is 1 hour
2

stress test -> com.objectdb.o.InternalException: null

. If the load is relatively low, the errors start to appear after some minutes or half an hour, or even an hour ... hours). Both cases were tested with 9 API requests / millisecond from custom samplers in JMeter ... for the 4 hours one: It's split in part 1 and two, to see how the memory usage goes. Running on Oracle
2

ObjectDB 2.3.6

Improved performance of collection and map size evaluation in queries. Fixed a critical bug in page caching (issues #610, #621, #625). Fixed a bug in optimization of non ASCII string indexes. Fixed the new query HOUR function to return hours as 0 to 23 (using 24-hour clock). Fixed a regression bug

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support