Hi,
I am using James 2.0a3 with JDK 1.3.1 on W2K machine.
I am experiencing a memory leak in my application. During my
troubleshooting I have finally removed all my mailets in order to test
James alone. The memory leak persists!
This is my scenario:
- I have a load generator that sends 10 mail/second. Mails have
different sizes, with an average of 11Kb.
- On the James size, I have a mailet that prints the JVM total and free
memory (in Mb) every 100 messages. Here you have my spoolmanager
configuration and the results that I get:
<spoolmanager>
<threads>1</threads>
<mailetpackages>
<mailetpackage>org.apache.james.transport.mailets</mailetpackage>
<mailetpackage>test</mailetpackage>
</mailetpackages>
<matcherpackages>
<matcherpackage>org.apache.james.transport.matchers</matcherpackage>
</matcherpackages>
<processor name="root">
<mailet match="All" class="MemoryPrinter"/>
<mailet match="All" class="Null"/>
</processor>
</spoolmanager>
Mail # Total memory Free memory
0 2.5820312 0.5600738
100 5.6132812 1.6391296
200 9.0234375 2.3683395
300 15.128906 5.4931946
400 15.128906 3.0394592
500 25.488281 10.329994
600 25.488281 7.8969116
700 25.488281 3.9112778
800 25.488281 1.5132217
900 42.125 16.21582
1000 42.125 12.281708
1100 42.125 10.111511
1200 42.125 7.9458237
1300 42.125 3.9470978
1400 42.125 1.725914
1500 63.75 23.18071
1600 63.75 19.276215
1700 63.75 17.146133
1800 63.75 14.976295
1900 63.75 11.164001
2000 63.75 9.04203
2100 63.75 7.0878906
2200 63.75 4.38665
James crashes in less than 4min with an OutOfMemoryError. JVM options
that increase heap size would only make this happen a little bit later
:-(
Has anyone experienced this before? Any suggestions about a better JVM
or a different James version? May this come from Avalon?
Regards,
Diego
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
