For JAMES-474 and JAMES-419 I already know what the problem is, and I
left them open because I would like to find a workaround or another
clean solution to not disable the 2 features/optimizations.
For JAMES-466 maybe the problem is related to the message size: the main
difference between the old code and the new one is that the new one have
to know the exact message stream size before writing it to db and when
the size is incorrect the exception is the one you reported. It could
also be a synchronization issue, or maybe some random but in the
connector/J streaming code. Can you add a try/catch to the
JDBCMailRepository.store method and log as much as you can about the
message being processed and the calculated size?
Stefano
Norman Maurer wrote:
Just see it.. I will have a closer look in the code to maybe help with
these if i can..
bye
Am Samstag, den 15.04.2006, 16:50 +0200 schrieb Stefano Bagnara:
Norman Maurer wrote:
Any plans when alpha 2 will be released ?
bye
IMHO we have 3 show stoppers (I just updated JIRA priorities):
http://issues.apache.org/jira/browse/JAMES-466
JAMES-466 - java.sql.SQLException: Error reading from InputStream
java.io.IOException in current trunk
http://issues.apache.org/jira/browse/JAMES-474
JAMES-474 - NullPointerException and bodymessage lost with weird
configurations in message spooling
http://issues.apache.org/jira/browse/JAMES-419
JAMES-419 - NPE during 8bit conversion of non-mime messages (I
experienced related problems in 7bit to 8bit and 8bit to 7bit conversions).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
