About reproduce

forum_thread

JPQL keyword in entity - what to do?

Hi, I have a problem with entity that is using one of JPQL keywords as one of the fields. It's a 'type' field. When I try to build a query that looks for example like this: select new ResultData(p.type.name, count(p.id)) from Product as p group by p.type.name I got this exception: #1 2011-03-01 22:22 Hi, I have a problem with entity that is using one of JPQL keywords as one of the fields. It's a 'type' f ...

 
forum_thread

ODB should auto-restart if it detects it's necessary

Hi! I find very tricky the need to restart ObjectDB server after schema modifications in a distributed environment. Moreover, not doing it does sometimes trigger ugly errors, which mean application downtime. It might be very useful to have an additional feature (that could be enabled/disabled in objectdb.config) that each time ObjectDB detects a schema change that requires restart, it should automatically restart itself. This way we save a lot of headaches from our dev. ops. Currently we have to manually do: ... you can provide a test application and instructions how to reproduce the problem it could help in providing a solution in the short term. ...

 
forum_thread

Internal exception when updating date filed (TemporalType.DATE)

Hello! ObjectDB version 2.5.3_02. I get internal exception when commiting update Date field (javax.persistence.TemporalType.DATE). ... than 1,000 users. I slightly changed my example to reproduce my issue (set timezone to "Europe/Moscow"). My output: ...

 
issue

Error on commit

I get the following on commit:  (v2.3.7_15) Let me know if you need more info. ... Anyway, since the problem is solved and there is no way to reproduce it now I will close the issue. Please reopen it if you get that ...

 
issue

Negative snapshot user count

I finally hit an instance of the "Negative snapshot user count" exception 1) ... is released while it is still in use. I could reproduce both problems with the following test: import javax. ...

 
forum_thread

Connection is closed Caused by: java.io.EOFException

I am getting this exception on a regular basis, after a period of time of repeating the same code execution.  I don't understand why.  I restart the DB server and my code works again for another period of time until same exception is encountered again.  I cannot pin down a pattern e.g. after a certain period of time,  because the time  periods between exceptions are not regular, although frequent.  Any test case  I use will pass most of the time but will fail after an undetermined period. #1 2011-06-18 13:34 I am getting this exception on a regular basis, after a period of time of repeating the same code execution. &nbs ...

 
issue

NullPointer when accessing persistent field

I am afraid this is a large and complex example, and I do not encounter the problem in simple cases, therefore there is no example attached. I appreciate this may make the bug unreproduceable from your end.   Bug Version: 2.3.2 Priority: Normal Status: Fixed Replies: 7 Type:  Bug ...

 
issue

Internal exception on flush

Today I received the exception below on running the following code: Bug Version: 2.3.3 Priority: Critical Status: Fixed Replies: 3 Type:  Bug ...

 
forum_thread

Failed to commit transaction: Attempt to commit a rollback only transaction

Anyone know what this means?? Suddenly cropped up.   Failed to commit transaction: Attempt to commit a rollback only transaction (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:271) at javax.jdo.Transaction$commit.call(Unknown Source) ... for both the client and the server. Try to reproduce the exception. Check the client and server log files ...

 
forum_thread

Server connection management

The server does not appear to release broken connections. My typical development pattern is to keep reloading my war file in tomcat until the permgen space runs out, and then I kill and restart tomcat. After a few days of this, the server stops responding, and I see the following in the server logs: ... I just ran a quick test and couldn't reproduce the problem: package com. objectdb . test . bug ; ...