Try increasing the memory for your program. Consult the -X options of java. (java -X).
The lack of crash detail might be caused by insufficient memory.
You might want to consider a queued architecture (as in a limited number of threads) - build up a queue for each of these threads for computationally expensive operations. It's better that switching from one thread to the other (I mean JVM's thread switching).
Main Topics
Browse All Topics





by: blackhyperdamagePosted on 2003-05-08 at 18:44:01ID: 8492885
That would be envitable. I've tried TripleDES (i am developing smart cards) and although i did not experienced a JVM crash doing so, it significantly slowed the machine. Try halting all the processes for a while to allow forced garbage collection - System.gc() or better limit the # of threads (I suspect you have more that 70 threads) also try to conserve system resources as much as possible. (I have to admit I am almost tempted to implement it in C because of the speed)