Internal Website Search

that reproduce the problem it might be very difficult to explore the problem and fix it. If you have more information on this issue it may help. support Support I will work on creating a reproducible case. FastModel Ben Schreiber

with objectdb-2.6.3_04. webel Dr Darren Kelly The following test is an attempt to reproduce ... ); The run again without error on persistence. webel Dr Darren Kelly In my main web app I reproduced

, but could not reproduce the problem. The following works WITHOUT storing the test in a temporary variable ... (not compile-time) are correct and reproducible . I am using the JAD decompiler to investigate

). But this behaviour doesn't always happens. In my test case, i can't reproduce the issue, it only happen in ... on left joined attribute, i haven't succeed to reproduce the issue. Support, can you confirm

to reproduce the reported problem, but not exception is thrown: import javax.persistence.*; @Entity ... in reproducing it. Please change the attached program so generate the exception or provide a database

I have a class that is persisting a Entity that holds remarks and a time. Then when I query for the latest remark I get a internal error when the remark is larger than 1966 chars. Here is a test class and entity that reproduces the problem on my system. @Entity @Table(name = "TestEntity", schema

change that included @Id fields. This situation of mixed ID types can be easily reproduced by

.NoResultException ex) {    return -1;   } } I will attempt to reproduce this in

for both the client and the server. Try to reproduce the exception. Check the client and server log files for errors and exception stack traces. support Support

; evil850209 Chris This exception can be reproduced by the following simple console application (i.e

/more information.   Kevin Kevin Pfaff Okay, I created a little test project which reproduces the error

a sample case that reproduces the exception (you may attach the database and the code to a support

) - the exception could be easily reproduced : import javax.persistence.*; public final class Test {   

that demonstrates the problem (since it seems to be  reproducible ). support Support

') The interesting thing is I can't reproduce this in the simple test project I have supplied for other bugs

" : "BAB_grayOnlineGlossaries"); } Could you please explain how to reproduce the exact situation using

this format will be very helpful. support Support I could reproduce the problem with this test case

and couldn't reproduce the problem: package com.objectdb.test.bug; import javax.persistence.*; public final

-8262105 . If you can provide exact details how to reproduce the exception (including version of Java

reproduce the exception, since normally the client registers types with the server before

the stack trace usually doesn't help, so please prepare a heap dump. support Support Hi, I've reproduced

about the data stored in the database when entity classes are not in the classpath? If I can reproduce

after time or the internal structure does not match anymore. Unfortunately I cannot reproduce the error

I don't know how to reproduce this error, because I don't know what exactly did trigger it, but I thought that it might help if I report it. It's maybe because I removed 2 Integer fields from an Entity class. After restarting ObjectDB server, it didn't appear anymore. [ObjectDB 2.5.3] Unexpected

you for the fast response. I can reproduce this problem also with EE Version 2.6.2.b01. I just tried 2.6.2.b03

it - (full reproducible code here - just run it) Thanks  EKK   package DBbug; import java.io.Serializable

(this is what the unit test is setup testing at the mo). To reproduce the error, try replacing the annotation at line

post it occurred to me try ORDER BY with a field that is not part of any index. I can reproduce

of this problem? We can not reproduce this problem in a small example. It appears only in

I'm trying to persist an Entity containing a HashMap. It stores the data in the database OK, but the map is always empty when I get the entity out of the database again. I've reproduced this problem in a simple variation of the Guestbook tutorial: Guest class: ===================== @Entity public

. Unfortunately, we can not reproduce this with a small example until now. Sometimes it works. btc_es BTC

you for your report but unfortunately we cannot reproduce it (e.g. deleting the first row in a table ... Support We currenty cannot reproduce this as well. At the time it happend at two different machines

, though. If you can give me a hint as to what would internally cause this, I'll try to reproduce it. Carl   ... found a very simple reproducible case that produces the exception every time:     javax

database for reproduce this issue from your side. Have a nice playing 8-) Harman Alexander Golyshkin

BTC EmbeddedSystems Thank you for this report. We could reproduce the exception with the following

with this issue is that we cannot reproduce it and cannot understand the cause. If you will be able

)? If not, is it possible to reproduce it using coresystemdb.rar from November 2019

to reproduce : import javax.jdo.PersistenceManager; import javax.jdo.PersistenceManagerFactory; import

).   JFK John Francis The following test case reproduces the exception. It may be thrown

addition, please notice that this attempt to fix the problem was done without the ability to reproduce

found a way for you to reproduce the crash. If you open the attached db with the explorer and run

snippets which should reproduce the problem. public class Locale extends BaseEntity { ... @Embedded

= loaded; } I don't have time to offer an isolated test case, but I found the result reproducible

been able to reproduce this exception. (which is good, I suppose!) Around the time it occurred

. Could you please check if you can reproduce the problem with a clean database by throwing an exception from PrePersist

on your production server. It records all the transactions, so playing them later may reproduce the issue and enable

? Could you upload the database in which this query fails? support Support This issue will be closed as non reproducible . support Support

/tynamo/trunk/tapestry-jpa-seedentity kaosko Kalle Korhonen Thank you for your report. I could reproduce

again. Of course, if you find a way to reproduce index corruption it may be of a great help. support Support

same parent class.   Marta Maruta M Sedlakova We succeeded in reproducing the problem and hope