We are successfully passing 50 megabyte messages around with James. We had to set the
spool manager to one thread to keep from processing 2 large messages at once, which
would typically trigger a JVM out of memory error.
If you have a dedicated server with lots of memory, you may be able to
what is causing the memory load.
--- Noel
-Original 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
-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 attached files
I'm trying to upgrade from James 2.03 to James 2.1.2 on a windows 2000 box. I started
using the Sun 1.3.1.05 jvm and am now using the 1.4.0.01 jvm.
When I add our custom mailet and matcher to the config.xml file, I get a class not
found exception when James tries to load my mailet. I've
I was able to resolve this, and the new wiki helped, but it was Chris Mean's message
http://archives.apache.org/eyebrowse/ReadMsg?listId=21msgNo=4975
that opened my eyes. I was just adding my custom jar files to the apps/james.sar file
using winzip. Winzip was storing the files without a
I'm a bit of a newbie, so bare with me...
I'm running James 2.03a as a service using alexandria with the Sun 1.3.1.05 JVM and am
having problems with messages with large attachments never getting processed in spool.
I am also using the file system for spool rather than a database. I have
