svn commit: r930337 [1/3] - in /james/server/trunk/spoolmanager/src/main/java/org/apache/james/transport: camel/ mailets/

Author: norman Date: Fri Apr 2 17:58:03 2010 New Revision: 930337 URL: http://svn.apache.org/viewvc?rev=930337view=rev Log: Replace tabs with spaces.. not code changes Modified:

svn commit: r930337 [3/3] - in /james/server/trunk/spoolmanager/src/main/java/org/apache/james/transport: camel/ mailets/

Modified: james/server/trunk/spoolmanager/src/main/java/org/apache/james/transport/mailets/ActiveMQRemoteDelivery.java URL:

Re: OutOfMemory exception

nop. OutOfMemoryError is back. I will double check my server, jdk and environment config, but other java processes are running on the same machine without problem. I will also have a stress scenario on my local dev PC that runs fine and after, I will rerun it on my production server. Dump

Re: OutOfMemory exception

Hi Eric so at least the files not leak anymore, unfortunaly this was the less critical problem. About the errors in pop3server I will have a look and see what could cause this. I'm 100 % sure it's not related to the OOM. Any more infos related to the OOM are welcome. Bye Norman 2010/4/2, Eric

Re: OutOfMemory exception

Hi Eric, I forgot to mention that one cause of the OOM could be the current usage of InMemoryMail. At the moment James load the whole MimeMessage into memory while processing the camel routes. This is really a bad practice in terms of performance and could maybe cause a OOM if you processing many