hi
i am running James 2.1.3 (Win 2k - Sun Java 1.4.x), using the file
system as mail store. Having set-up a single user, i send a 100MB email
which produces an out of memory exception on the command line. No other
log entries can be found.
- What are your experiences with large emails (can it
> i am running James 2.1.3 (Win 2k - Sun Java 1.4.x), using the file
> system as mail store. Having set-up a single user, i send a 100MB
> email which produces an out of memory exception on the command
> line. No other log entries can be found.
Turn on DEBUG for all targets in SAR-INF/environment.
st
Subject: RE: 100MB email produces an out of memory exception
> i am running James 2.1.3 (Win 2k - Sun Java 1.4.x), using the file
> system as mail store. Having set-up a single user, i send a 100MB
> email which produces an out of memory exception on the command
> line. No other lo
Message-
From: Horsfall, Brian [mailto:[EMAIL PROTECTED]
Sent: Monday, June 23, 2003 13:21
To: James Users List
Subject: RE: 100MB email produces an out of memory exception
We are successfully passing 50 megabyte messages around with James. We had
to set the spool manager to one thread to
Users List
Subject: RE: 100MB email produces an out of memory exception
Brian,
Thanks for the report. That is good to know, and helpful. :-)
But James really should not be loading the entire message content into
memory unless some matcher or mailet is asking for it, so it would be good
to
-
From: Horsfall, Brian [mailto:[EMAIL PROTECTED]
Sent: 23 June 2003 21:51
To: James Users List
Subject: RE: 100MB email produces an out of memory exception
Noel,
You are correct. Our mailet is our problem with memory usage.
Our Mailet uses byte arrays to handle attached files. Byte arrays requir
give.
Lindsay
-Original Message-
From: Horsfall, Brian [mailto:[EMAIL PROTECTED]
Sent: 23 June 2003 21:51
To: James Users List
Subject: RE: 100MB email produces an out of memory exception
Noel,
You are correct. Our mailet is our problem with memory usage.
Our Mailet uses byte arrays to handle
> When I've seen the OutOfMemoryException it's when using just the standard
> mailets.
If you can give us an idea of which one(s) that might be helpful. Auditing
the package for code that loads the message into memory is a side-project
that someone might want to pickup.
--- Noel
--
Horsfall, Brian wrote:
We never had a problem with james handling large messages, but we really only use the hostis matcher and our custom mailet.
We are using the IBM 1.3.1.05 JVM with a min heap size of 128 megabytes and a maximum heap size of 256 megabytes.
Added to Wiki.
--
Serge Knystautas
P
2003 23:24
To: James Users List; [EMAIL PROTECTED]
Subject: RE: 100MB email produces an out of memory exception
> When I've seen the OutOfMemoryException it's when using just the standard
> mailets.
If you can give us an idea of which one(s) that might be helpful. Auditing
the p
Lindsey,
Unfortunately:
-Xrunhprof:cpu=samples,file=log.txt,depth=10
doesn't profile the heap. You profiled the CPU. :-) What you want to use
is something like:
-Xrunhprof:heap=sites,depth=10
which would give us the heap information.
I had a suspicion, and thought that it might be a side
ers List; [EMAIL PROTECTED]
Subject: RE: 100MB email produces an out of memory exception
Lindsey,
Unfortunately:
-Xrunhprof:cpu=samples,file=log.txt,depth=10
doesn't profile the heap. You profiled the CPU. :-) What you want to use
is something like:
-Xrunhprof:heap=sites,depth=10
wh
On Thu, Jun 26, 2003 at 11:13:56AM +0100, Lindsay Smith wrote:
> Sorry about that, I repeated the test with about a 14Meg attachment with:
> -Xrunhprof:heap=sites,file=log.txt,depth=10
I think it would be nice if there's a mailet that can do split/join for
out/incoming messages. I believe, the sp
13 matches
Mail list logo
