[ 
http://issues.apache.org/jira/browse/JAMES-466?page=comments#action_12375120 ] 

Stefano Bagnara commented on JAMES-466:
---------------------------------------

The baos log is not useful: it is a ByteArray so we can safely say we know its 
correct size.

I this we should find how you have the same "mail.name" logged twice with 
different sizes.

We know that RemoteDelivery with a configured gateway store the mail with no 
changes to the name in the ougoing spool. So the 2 logs could be related to the 
store in the main spool and the following store in the outgoing spool. What I 
still don't understand is why the size is totally different.

Maybe you have a few mailets in between (from the root processor to the 
RemoteDelivery mailet) that completely change the mail content. Can you check 
this?

You should also add the size logging to the setBinaryStream called in 
JDBCMailRepository:668. This code is called when the message is updated in the 
spool (every time it is moved to a different processor, for example).


> 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]

Reply via email to