Re: sloader OutOfMemoryError
What are the commands you are using when initialinzing the service ?
The error that the log you posted shows a Java out of memory error.
It could just be that there is some log cleanup process in the background and the size of the logs ro the DB has grown over time so Java now needs more memory to perform the same functions. I would try zeroing out any logs and also look at the amount of memory i am providing to Java.
The amount of memory thati s provided to Java can be modified both on initial server startup using the -U switch in the autoexec.bat file. This switch will pre-allocate to the USER Address space more of the memory that is available on the server. You can also change the load line in Java with the -XMS and -XMX switches. this will give you a min and a max. We have also found lately that there is a Swap file for memory that is created and that Java can use this too ;-)). Type swap at the server console and then "help swap" to get the commands to manipulate it. We reset the swap to another volume than sys: , and we expand it out with a min and max command so that again it is pre-allocated out to a couple of GIG.
If Java runs out of regular memory and you get short term allocation issues Java will try to dump everything out to the Swap. As long as you have the swap min size big enough to cope with the dump from Java then you will not lose the Java thread and the system will recover.
Hope this helps
Jules;-))
|
Threaded Mode
