Al Caponi wrote:
> spoolmanager log file: No log for the past few days
> although emails were coming in.
> Connections log: Filled with ERROR connections:
> Error handling connection java.lang.OutOfMemoryError
Which version of JAMES, and after how long?
> the messages in the spool folder simply disappeared and
> didn't go to their respective inboxes.
> Upon further investigation, I found that some of the inboxes
> (which contained hundreds of messages) were completely empty.
I've not seen that behavior with JAMES, even after OOME. Which version?
What type of repository? There is nothing in JAMES that will delete
existing messages that way, *except* if someone is using a file-based
repository, and has removed one of the file pairs. Someone did that
recently, not realizing that the *Object* and *Stream* files are in pairs,
and accidentally deleted everything.
> I encountered a major problem on our production server with James 2.2.0
> (File repository)
Is that still the configuration used above? What was the "major problem"?
> <!-- Number of spool threads -->
> <threads> 100 </threads>
Are you providing enough memory to JAMES to handle that? That's a LOT of
spool threads.
> <max-connections>0</max-connections>
> For each of the 4 services - pop3, pop3s, smtp, smtps:
> <connectionLimit>200</connectionLimit>
> There are 4 thread-groups defined for each service.
> All have the same settings as the following (except
> the name):
> <max-threads>500</max-threads>
Uh ... why?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
