[ http://issues.apache.org/jira/browse/JAMES-466?page=comments#action_12376698 ]
Stefano Bagnara commented on JAMES-466: --------------------------------------- Just applied a patch to set the default behaviour to the old one (use FULL in memory ByteArray instead of small streaming buffer). Adding a "<inMemorySizeLimit>4096</inMemorySizeLimit> " as a child of <repository><config> element for JDBCMail and JDBCSpool reenable streaming for messages larger than 4KB. I also applied a patch to the MimeMessage size calculator that could be the real cause of the issue (I have written this weeks ago and forgot to commit, so I always tested with this version, maybe this was the real fix). Norman, can you get the latest trunk, add an inMemorySizeLimit really small (1 byte) and tell me wether the exception is there or finally gone? > java.sql.SQLException: Error reading from InputStream java.io.IOException in > current trunk > ------------------------------------------------------------------------------------------ > > Key: JAMES-466 > URL: http://issues.apache.org/jira/browse/JAMES-466 > Project: James > Type: Bug > Components: MailStore & MailRepository > Versions: 2.3.0a1 > Environment: java 1.5, mysql-connector-java-3.0.17-ga-bin.jar > Reporter: Norman Maurer > Assignee: Stefano Bagnara > Priority: Blocker > Attachments: MailRepostitory.patch, james-bug2.txt > > After upgrading to latest trunk i notice this exception about 8 times today: > 01/04/06 21:52:53 ERROR spoolmanager: Exception in processor <transport> > javax.mail.MessagingException: Exception caught while storing mail Container: > ; > nested exception is: > java.sql.SQLException: Error reading from InputStream > java.io.IOException > at > org.apache.james.mailrepository.JDBCMailRepository.store(JDBCMailRepository.java:755) > at > org.apache.james.mailrepository.JDBCSpoolRepository.store(JDBCSpoolRepository.java:236) > at > org.apache.james.transport.mailets.RemoteDelivery.service(RemoteDelivery.java:1001) > at > org.apache.james.transport.LinearProcessor.service(LinearProcessor.java:414) > at > org.apache.james.transport.JamesSpoolManager.process(JamesSpoolManager.java:397) > at > org.apache.james.transport.JamesSpoolManager.run(JamesSpoolManager.java:306) > at java.lang.Thread.run(Thread.java:595) > 01/04/06 21:52:53 ERROR spoolmanager: An error occurred processing > Mail1143921172623-45 through transport > 01/04/06 21:52:53 ERROR spoolmanager: Result was error > Whats the Problem ? Should i upgrade the mysql-connector ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
