| 2:25:05 PM PDT - Wed, Jun 5th 2013 |
|
Hi John,
I've never seen this before on any of our systems. The simplest fix though would be if the memory allocated with the "-Xmx" argument to the java command (for the java virtual machine that's created for the ActiveMQ messaging server) could be bumped up to resolve it. That argument is set in the activemq package startup script rather than from something directly in ECCE. But you should be able to edit it and restart the ECCE server and see if it makes a difference.
If you cd to the top-level ECCE server install directory, do a "cd activemq/bin". Then edit the "activemq" file and search for "-Xmx". You'll see it set to "512M". You could just double it to "1G" or go beyond that even to say "2G". Make sure you stop the ecce server though before trying to restart it. Also confirm it is running with the amount of memory you expect before starting the ECCE client GUI by doing another "ps" command for the java process. I'm not sure at all if this will help, but seems like the best thing to try.
Gary
|