Internal Website Search

101-150 of 177 results

Project runs in Eclipse but not when exported to runnable jar

cannot reproduce the exception (on Windows XP with JDK 1.6.0_26). The application starts and the main

Inconsistent return types from JDO query

the query and specify the relevant types. support Support I am attaching sample code which reproduces

Attempt to remove a detached entity object (error 613)

was not able to reproduce the bug outside my production environment :( So i have 1 simple question

alter table

instructions (that have been verified by you first) how to reproduce it. As already explained

EntityManagerFactory Fails To Swtich Over To Slave When Master Is Unavailable

$     imofe thomas simms Thank you for this revised test. Unfortunately I couldn't reproduce

Retrieval by Access bug?

that there may be an issue on a specific scenario, and this has not been revealed or reported yet. Can you reproduce

First query takes 4+ minutes to complete

before running the query to see if we can reproduce the problem every time we run the query

JPA JPQL WHERE clause for IN :variable not working if variable is a list of Enums

adjust it to demonstrate the issue that you had. support Support I managed to reproduce the issue

Activation Issue

for retrieving the meta model you access also a local embedded database. If not, we will try to reproduce it by

Wrong data stored in date only fileds

and can easily be reproduced . Here are the values used to set the fields before adding the objects (in

100% CPU when using multiple BETWEEN

Andonov We have to reproduce this in order to understand the bug and fix it. Could you share

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

application and instructions how to reproduce the problem it could help in providing a solution in

Cascading merge() leading to "Attempt to persist a reference to a non managed instance" error

" reproduces the error: public final class ObjectDbCascadingMergeTest {   public void

Attempt to open a non existing file '/tmp/objectdb_xxxx/SortQueryItr_6.mrg'

Hi, I came across an error - but i have not been able to create a simple reproducible case - the error does not happen often and does not happen always -  Let me explain: 1/ I run 5 java applications at the same time on one machine - each application is using an ODB file (each one is using

Query performance in general

Hi ObjectDB team, we are currently investigating performance issues that affect some of our customers. Unfortunately, we are not yet able to reproduce issues in a test case, so we rely on reports and log files from customers. During internal analysis and discussions, we had some general questions

Java 6/7 Performance Comparison

, but have tried all the versions back to 2.5.3 cojan_duffy Andrew David Duffy We couldn't reproduce

exception during online backup

Wozniak Thank you for your report. I will try to reproduce it by a test that uses online backup

Out of memory

the same order as in our software that lead to Exception. I can't however reproduce this part of exception

NullPointerException while setting a new property value

, it's not easy to reproduce it in the small scale for a test case. We got also another report from

Database Inconsistency or corruption

easy because we have a quite complex environment. It is not easy to reproduce the problem. I started

Trouble bug on explorer

Kadir BASOL Could you please provide a demo odb file + instructions how to reproduce the problem in

Schema migration - long to String

types. I will try to reproduce this one more time and I will try to migrate schema with removing index

Is there any restriction when using fetch=FetchType.LAZY ?

Hi, I came across a weird behavior when using fetch=FetchType.LAZY in a complex code. However I am  unable to reproduce the behavior in a simple code. The behavior is like below: 1. When I am using in object declaration @OneToMany(fetch=FetchType.EAGER, cascade = CascadeType.ALL) private

Empty query results after JAR creation

to report the same issue. I've created a small test case (attached zip file) with a sample DB to reproduce

Failure after ObjectDB 2.4.5_07 upgrade from 2.4.4_06

also if returning to 2.4.4_06 solves the problem. If the problem can be reproduced by a test case

Lazy loading does not work - crud takes long

a minimal Java console test case (see these instructions ) that reproduces this situation. support Support

"Problem" with cross join

test reproduces the problem - its fails with version 2.0.4 and seems to work well with 2.0.4_01

ArrayIndexOutOfBoundsException: -1

further information.   thumbripper Richard Szurgot Thank you very much for this useful test. It also reproduces

Page cache File handling produced an java.io.IOException: Negative seek offset

that reproduces the exception it is still possible that the new build will not solve the issue. support

Server out of memory exceptions

another out of memory exception on the server. I haven't been able to reproduce it consistently though as it worked

Blocked operation leads to a deadlock

one side of the deadlock. If this issue can be reproduced then a partial thread dump of all the relevant

Database access error , Doctor hanging on trying to repair, production shutdown at our biggest customer

again we may be in a position to reproduce the problem by running the recorded transactions. support

JPA Composite Key make Object Db throws "Unexpected exception (Error 990)"

be reproduced with a simple ( not embedded Id ) key with an enum type. Here is the code : package test

Removed entities can be found by query in the same transaction

that we should keep. Unfortunately we couldn't reproduce this issue yet or understand what may cause it. support Support Some

An entityManager.flush() with many entities is not possible

have not found a simple example to reproduce this exception. The entity model of the flushed JPA

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

is the culprit.) INSTRUCTIONS TO REPRODUCE PROBLEM The entities (mostly Element or Element subclass objects

Unexpected Internal Exception

? support Support This issue is closed due to inability to reproduce the problem. It should be reopened if new information becomes available. support Support

InternalException when using MEMBER OF on a large list in a query

with the Doctor. - no Problem. I reproduced the exception by execute the Query in the explorer

Schema-Update: Deactivation of automatic entity class removing and introduction of a new class remove in the schema config

.java:716) at removedSubClass.UpdateDB.main(UpdateDB.java:27) We tried to reproduce the issue

Negative snapshot user count

and sometimes NullPointerException when the snapshot is released while it is still in use. I could reproduce both problems

References to objects of missing obsolete entity classes

of deleting classes using the Explorer, so it may be related. We cannot reproduce the exceptions

EOFException

;suspicious activity. support Support The stack trace reflects a bug that was reproduced and fixed using the test in issue #625 . support Support

Error on commit

. Anyway, since the problem is solved and there is no way to reproduce it now I will close the issue

Page #9 entry 0 (key 'bjjl') has 75 extra bytes / Unexpected last index ID: -119 (expected -116)

to reproduce the database creation process. Do you know how to create a new database

Internal exception on flush

Support The stack trace at #2 reflects a bug that was reproduced and fixed using the test in issue #625

InternalException during EntityManager.find()

. Do you have a way to reproduce the issue and check the new build?   support Support

preUpdate-methods are called when there is no change

. But it still shows the unexpected behavior. To reproduce just run the "EntryPoint" class.  

NullPointerException: Cannot invoke "com.objectdb.o.RFV.S()" because "" is null

Using @Index for fields and combine this with sorting the query throws an NullPointerException. This code reproduces the error: public class NullTest {     @Entity     @Indices({         @Index(members = {"children

unexpected exception - in query

could reproduce the exception in the attached test. Please check the new build (2.0.4_02) that should fix

ClassCastException in Tuple.get

, I assumed that issue is trivial to reproduce and that's why I did not attach the sample code