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

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

Thank you for the tests, unfortunately I'm not able to reproduce it in a test.
Can you change the throwException() method of MessageInputStream adding 
printStackTrace() for the exception caught?

    private void throwException() throws IOException {
        try {
            if (wrapped == null) {
                throw new IOException("wrapped stream does not exists anymore");
            } else if (caughtException instanceof IOException) {
--->                caughtException.printStackTrace();
                throw (IOException) caughtException;
            } else {
--->                caughtException.printStackTrace();
                throw new IOException("Exception caugth in worker thread 
"+caughtException.getMessage()) {
                    /**
                     * @see java.lang.Throwable#getCause()
                     */
                    public Throwable getCause() {
                        return caughtException;
                    }
                };
            }
        } finally {
            caughtException = null;
            wrapped = null;
        }
    }

The jdbc driver ate the stacktrace at "ServerPreparedStatement.storeStream".

The problem is in the new pipe code. It is used only with messages greater than 
4KB: can you check if you get this error for EVERY message greater than 4kb or 
only few of them? What mysql server version are you using?

I see that the last exception is from the ToRepository and not from the 
RemoteDelivery: this is good because we now know (almost for sure) that the 
problem is in the store code and not somewhere else.

> 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

>  Environment: java 1.5, mysql-connector-java-3.0.17-ga-bin.jar
>     Reporter: Norman Maurer
>     Assignee: Stefano Bagnara

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