Wish i know how to fix it.. has been on my "need to fix this asap" list for a while.
I am using some custom matchers and mailets.. so i have always thought that it may be something i did that was causing some weirdness in routing messages..
Cj
Cesar Bonadio wrote:
Hello
We are using james version 2.1.2 and after 5 days the server logs the following message in james-spool
30/12/03 00:51:46 ERROR spoolmanager: Exception in JamesSpoolManager.run null java.lang.OutOfMemoryError 30/12/03 00:51:48 ERROR spoolmanager: Exception in JamesSpoolManager.run null java.lang.OutOfMemoryError 30/12/03 00:51:51 ERROR spoolmanager: Exception in JamesSpoolManager.run null java.lang.OutOfMemoryError
If we restart the server everything goes fine but after 5 days I get those messages and the server stop processing messages in the spool, the smtp works fine but it only puts messages in the spool and the messages stay there. The maximum message size is set to 15000 and there was a message this large in the spool, but after I restart the message was processed correctly with no errors.
Any idea of parameter that I could change?
java version "1.4.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)
Running on a Linux with RedHat 7 with 1Gig of memory
Another thing I notice is that when this happens the CPU load goes UP and if I list the processes I see the java process "thread" eating a lot of CPU
Thanks for any help
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Corey A. Johnson Creative Network Innovations http://www.cniweb.net/ 1-800-CNi-5547 ** 1-321-259-1984
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
