About max

71-80 of 124Refresh
Issue
2

Service terminated silently (crashed?)...is there any way to cause a crash dump?

you should increase the value in the server configuration, e.g. max="1000000" /> Starting 2.6.5 the client gets an exception but the server continues to work as expected and max
Issue
2

A bug in the JDOQL processor in recent versions of ObjectDB

There seems to be a bug in the JDOQL processor in recent versions of ObjectDB. I've uploaded a "laptop" example to demonstrate the problem. The query in Test1.main should return "ThinkMachine MAX SX ... ) correctly return "ThinkMachine MAX SX 20". Regards. Thank you for this report. Please try build 2.6.5
Forum
2

Activation Issue

="true" sync="false" path="." max="128mb" /> max-threads="10
Issue
2

ArrayIndexOutOfBoundException

cache="64mb" max-threads="10" /> The problem occurs ... " max-threads="10" synchronized="true" /> When synchronized is enabled, all operations
Issue
2

Sort of very large objects - out of memory

" /> max="128mb" /> max
Issue
2

Threaded Test - Failed to commit transaction: Unexpected internal exception

wouldve thought the max data I'm holding should be around 20mb (5 consumers * 5 producers * 2mb) and when the consumers alone are running this should drop to a max of around 10mb (5 consumers * 2mb
Forum
2

Wrong select results

" />   max="128mb" />       max-threads="8
Forum
2

Inserted entities with strings as keys and indices needs more and more ram memory in comparing to primitive integers as keys and indices

, but not more and more memory. And if the max heap memory is big enough then the solution works ... when you run the program with a smaller max heap size?   If I reduce indeed the RAM to 1 GB the example runs
Forum
1

Can I Disable the Creation of the "log" Directory?

-history size="0" user="false" password="false" /> max="8mb" stdout="false" stderr
Issue
1

cannot delete objects after crash (see issue 2283)

="false" mode: max="128mb" /> In this mode, commit