Danny,
Sorry, I should have been clearer. I said it was a known issue, I didn't
say that everything was fixed. :-)
I believe THAT particular symptom comes from the scheduler/watchdog issue,
which has been documented since Spring. The flood of messages creates a
huge number of scheduler entries, which persist for several minutes before
being released by the scheduler. The message traffic outstrips the rate at
which obsolete scheduler entries are released. This is why the new watchdog
code was proposed, designed and implemented.
Other memory leaks from 2.0a3 were fixed in 2.1-CVS, which is why I jad
asked if Diego would try the current code, so that we can see the impact of
those other changes. And when we get the watchdog change into the code, we
can get a third set of data points. I also believe that there are certain
areas where we can improve memory performance with object pooling.
--- Noel
-----Original Message-----
From: Danny Angus [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 11, 2002 13:46
To: James Users List
Subject: RE: James memory leak
I get this too from recent cvs, 100 threads delivering 100 1k mails, Jmeas
chokes at around mail 1200, after a couple of minutes.
d.
> -----Original Message-----
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]]
> Sent: 11 October 2002 16:46
> To: James Users List; [EMAIL PROTECTED]
> Subject: RE: James memory leak
>
>
> Known issue. Please try the 2.1 code, and let us know what you see.
>
> --- Noel
>
> -----Original Message-----
> From: Diego Castillo [mailto:[EMAIL PROTECTED]]
> Sent: Friday, October 11, 2002 9:29
> To: [EMAIL PROTECTED]
> Cc: Diego Castillo, INEXBEE
> Subject: James memory leak
>
>
> 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]>
