Stefano Bagnara wrote: > 4 days ago we released James 2.3.0RC4 and we already collected 3 bugs > and fixed them:
> JAMES-625 - an empty mbox will cause an error at pop3 login > https://issues.apache.org/jira/browse/JAMES-625 Apparently, hardly anyone is using mbox this way, else we'd have had a bug report. If we release it, who would test it (other than us)? But then again, what's the risk? > > JAMES-644 - FileRegexMatcher possibly leaks minor memory on startup > > https://issues.apache.org/jira/browse/JAMES-644 Worth fixing, but I agree that it is minor. > JAMES-649 - error "OutOfMemoryError: JAVA HEAP SPACE" in connections log > file when doing a POP TOP for 4000 messages > https://issues.apache.org/jira/browse/JAMES-649 This one seems the only reason for RC5. And it would get a workout from everyone who tests the RC. I suppose RC5 would be OK. I'd like to see us post it by Monday, and plan to release 2.3 next weekend, if there are no further problems. Regarding the memory leak, I'll take time over the next couple of days to see if I can isolate the error. Looking at the code for dnsjava, I don't see any separate Cache in the lookup code other than for DClass.IN. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
