T
TheMadDBA
Guest
To clarify what others are saying and to add my two cents.... There is no difference between local process memory allocation between a client server connection and a shared memory connection. I don't know of any bugs that cause local memory allocation issues with shared memory connections. If you are running the same R-code in the same way the client will react the same way. If you were truly hitting a 32 bit limit with the appserver process it would die and generate a core file. Use the following kill command to generate a protrace file (does not actually kill the process) kill -SIGUSR1 PID Use these KBs to help you determine if/where a leak is actually happening... knowledgebase.progress.com/.../P133306 knowledgebase.progress.com/.../P124514
Continue reading...
Continue reading...