Hi Eric,
this sounds promising Looking forward for your next report.
Bye
Norman
2010/4/2, Eric Charles :
> James survived the night.
> 300MB (exactly the same as when it started).
> No m64 file in tmp.
>
> I will post another update this evening.
>
> Tks,
>
> Eric
>
>
> On 04/01/2010 07:06 P
An automated nightly build of JAMES has been posted to
http://people.apache.org/builds/james/nightly/
Any unit test errors from the build should be reported below:
-
Author: norman
Date: Fri Apr 2 17:53:57 2010
New Revision: 930335
URL: http://svn.apache.org/viewvc?rev=930335&view=rev
Log:
null the byte array just to be sure the memory is really cleared
Modified:
james/server/trunk/spoolmanager/src/main/java/org/apache/james/transport/camel/InMemoryMail
Author: norman
Date: Fri Apr 2 17:58:03 2010
New Revision: 930337
URL: http://svn.apache.org/viewvc?rev=930337&view=rev
Log:
Replace tabs with spaces.. not code changes
Modified:
james/server/trunk/spoolmanager/src/main/java/org/apache/james/transport/camel/ActiveMQProcessorRouteBuilder.jav
Modified:
james/server/trunk/spoolmanager/src/main/java/org/apache/james/transport/mailets/ActiveMQRemoteDelivery.java
URL:
http://svn.apache.org/viewvc/james/server/trunk/spoolmanager/src/main/java/org/apache/james/transport/mailets/ActiveMQRemoteDelivery.java?rev=930337&r1=930336&r2=930337&view
Author: norman
Date: Fri Apr 2 18:05:58 2010
New Revision: 930341
URL: http://svn.apache.org/viewvc?rev=930341&view=rev
Log:
cleanup...
Removed:
james/server/trunk/mailets/src/test/java/org/apache/james/transport/mailets/
Modified:
james/server/trunk/spring-deployment/src/main/java/org/
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 anal
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 C
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
