About byte

51-60 of 103Refresh
Forum
2

Custom Classloader: Issues with the Enhancer Agent

ClassNotFoundException { javaClass = getGeneratedClass(name); if(javaClass != null) { byte[] bytes = javaClass.getBytes(); return defineClass(name, bytes, 0, bytes.length
Forum
2

Replicated cluster recovery

=admin   and thread stack dump: SocketInputStream.socketRead0(FileDescriptor, byte[], int, int, int) line: not available [native method] SocketInputStream.read(byte[], int, int) line: 129 BufferedInputStream.fill() line: 218 BufferedInputStream.read1(byte[], int, int) line: 258
Forum
2

@Lob @Basic(fetch = FetchType.LAZY) is loaded when it's not needed

Hello. I have a class Thing that contains OneToMany list of classes Photo. Photo contains  @Lob @Basic(fetch = FetchType.LAZY) private byte[] content; And after some queries with Thing ... eagerly. Consider replacing byte[] with a wrapper entity (e.g. Data) that will contain the byte
Forum
2

High memory consumption even after close() of EntityManagerFactory

which the execution of multiple queries increasingly byte array were generated (about 1.5 GB) which from GC ... 400 to 100 MB. But, the 100 MB byte array are still not released. The option objectdb.temp.avoid-page ... " threshold = "1mb" /> is the byte array only 3MB. I think that's OK. But at threshold = "64mb
Forum
2

NegativeArraySizeException on commiting a transaction

of the byte[] on which objectDB operates is above 1GB, so I am guessing that my entity ... something about that byte[] with an int which is overflowing if the byte[] grows over 1GB ? Your observation
Forum
2

Pre-detach loading: retrieval by navigation not working in if statement

see anything wrong in the byte code. I will examine your links. Aside: you asked: > Why are using an entity class ... Java compiler optimization, i.e. the byte code indeed looks fine, but it is not what is really ... ? Please post relevant byte code after enhancement. > Have you tried build time enhancement instead
Forum
1

500Mb ObjectDb database opening issue

()) {         NetworkInterface ni = (NetworkInterface)e.nextElement();         byte[] hardwareAddress = ni ... (); byte[] hardwareAddress = ni.getHardwareAddress(); } } catch
Issue
1

[ObjectDB 2.3.7_25] Unexpected exception (Error 990)

instances, apparently in their salt byte[] array. There was a change in the way byte[] arrays
Issue
1

InternalException - error reading field from "queue" database

it can be a string or a byte[]. In this particular database it should always be a byte[] and the db
Issue
1

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

. If possible, try to avoid primary keys longer than 32 bytes (in the test they seem to be 36 bytes). Thanks