You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by "Pao, Vanessa" <vp...@harris.com> on 2011/05/24 22:21:36 UTC
Connection Aborted exception in james-server.log
Hi all,
I am using James 3 (james-server-container-spring-3.0-M3-20110401.133250-93-bin.zip) and SquirrelMail 1.4.21 on a Windows 2008 R2 machine. I have James and SquirrelMail configured for SMTP with TLS and IMAP with TLS.
I notice when I have log4j.logger.james.smtpserver=DEBUG in log4j.properties and I try to send emails with or without attachments, I see the following in james-server.log:
INFO 16:04:14,364 | james.smtpserver | ID=1002379024 Successfully spooled mail Mail1306267454200-d428f133-fc33-4ff8-a33e-c6b794af95e4 from admin1@mail.com on 127.0.0.1 for [admin2@mail.com]
DEBUG 16:04:14,364 | james.smtpserver | ID=1002379024 executing hook org.apache.james.protocols.smtp.core.log.HookResultLogger@c9bf922
DEBUG 16:04:14,364 | james.smtpserver | ID=1002379024 org.apache.james.smtpserver.SendMailHandler: result=1 (OK)
DEBUG 16:04:14,365 | james.smtpserver | ID=1002379024 executing hook org.apache.james.smtpserver.jmx.HookResultJMXMonitor@54012da5
DEBUG 16:04:14,370 | james.smtpserver | ID=1002379024 org.apache.james.protocols.smtp.core.SMTPCommandDispatcherLineHandler received: QUIT
DEBUG 16:04:14,370 | james.smtpserver | ID=1002379024 Lookup command handler for command: QUIT
DEBUG 16:04:14,371 | james.smtpserver | ID=1002379024 org.apache.james.protocols.smtp.core.QuitCmdHandler: 221 [2.0.0 xxx.xxx.xxx.xxx Service closing transmission channel]
DEBUG 16:04:14,387 | james.smtpserver | Unable to process request
java.io.IOException: An established connection was aborted by the software in your host machine
at sun.nio.ch.SocketDispatcher.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:33)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
at sun.nio.ch.IOUtil.write(IOUtil.java:60)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
at org.jboss.netty.channel.socket.nio.SocketSendBufferPool$PooledSendBuffer.transferTo(SocketSendBufferPool.java:239)
at org.jboss.netty.channel.socket.nio.NioWorker.write0(NioWorker.java:469)
at org.jboss.netty.channel.socket.nio.NioWorker.writeFromUserCode(NioWorker.java:387)
at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:137)
at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:76)
at org.jboss.netty.channel.Channels.write(Channels.java:632)
at org.jboss.netty.channel.Channels.write(Channels.java:593)
at org.jboss.netty.handler.ssl.SslHandler.wrapNonAppData(SslHandler.java:803)
at org.jboss.netty.handler.ssl.SslHandler.closeOutboundAndChannel(SslHandler.java:1045)
at org.jboss.netty.handler.ssl.SslHandler.handleDownstream(SslHandler.java:409)
at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:60)
at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:114)
at org.jboss.netty.channel.Channels.close(Channels.java:720)
at org.jboss.netty.channel.AbstractChannel.close(AbstractChannel.java:208)
at org.apache.james.protocols.impl.AbstractSession.writeResponse(AbstractSession.java:156)
at org.apache.james.protocols.api.AbstractCommandDispatcher.onLine(AbstractCommandDispatcher.java:161)
at org.apache.james.protocols.impl.AbstractChannelUpstreamHandler.messageReceived(AbstractChannelUpstreamHandler.java:122)
at org.jboss.netty.handler.timeout.IdleStateHandler.messageReceived(IdleStateHandler.java:276)
at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:148)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)
at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)
at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349)
at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:280)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:200)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
The email always seems to be delivered without issues. The exception itself does not seem to cause any problems for an end user. I wouldn't have seen this exception if I didn't happen to turn on debugging. But it gnaws at me now that I know it happens. Has anyone experienced anything like this? Perhaps I have the wrong configuration somewhere...
Thanks,
Vanessa Pao
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: Connection Aborted exception in james-server.log
Posted by "Pao, Vanessa" <vp...@harris.com>.
Hi there,
If you mean a tutorial for integrating SquirrelMail with Apache James, I did not use one nor do I know if one exists. I followed general online instructions for installing SquirrelMail on a web server. Once SM was running, I played around with its configurations in a file called config.php. In this file, I told SM to point to the IP and port for Apache James, and whether to use TLS or not. One gotcha I found in config.php:
the variable $imapServerAddress needs to be set to 'localhost' or 'machine_name.yourdomain.com'. SquirrelMail won't retrieve e-mails if this is set to '127.0.0.1'.
the variable $smtpServerAddress needs to be set to '127.0.0.1'. SquirrelMail won't send e-mails if set to 'localhost' or 'machine_name.yourdomain.com'.
Vanessa Pao
-----Original Message-----
From: Daniel Tan [mailto:pufferfish@hotmail.com]
Sent: Wednesday, May 25, 2011 10:53 AM
To: James Users List
Subject: Re: Connection Aborted exception in james-server.log
hey there, though i can't help you with your query, is squirrelmail working well on your system? i didn't know squirrelmail can work.
it would be helpful if you could point me to the tutorial.
On 25-May-2011, at 4:21 AM, Pao, Vanessa wrote:
> Hi all,
> I am using James 3 (james-server-container-spring-3.0-M3-20110401.133250-93-bin.zip) and SquirrelMail 1.4.21 on a Windows 2008 R2 machine. I have James and SquirrelMail configured for SMTP with TLS and IMAP with TLS.
> I notice when I have log4j.logger.james.smtpserver=DEBUG in log4j.properties and I try to send emails with or without attachments, I see the following in james-server.log:
> INFO 16:04:14,364 | james.smtpserver | ID=1002379024 Successfully spooled mail Mail1306267454200-d428f133-fc33-4ff8-a33e-c6b794af95e4 from admin1@mail.com on 127.0.0.1 for [admin2@mail.com]
> DEBUG 16:04:14,364 | james.smtpserver | ID=1002379024 executing hook org.apache.james.protocols.smtp.core.log.HookResultLogger@c9bf922
> DEBUG 16:04:14,364 | james.smtpserver | ID=1002379024 org.apache.james.smtpserver.SendMailHandler: result=1 (OK)
> DEBUG 16:04:14,365 | james.smtpserver | ID=1002379024 executing hook org.apache.james.smtpserver.jmx.HookResultJMXMonitor@54012da5
> DEBUG 16:04:14,370 | james.smtpserver | ID=1002379024 org.apache.james.protocols.smtp.core.SMTPCommandDispatcherLineHandler received: QUIT
> DEBUG 16:04:14,370 | james.smtpserver | ID=1002379024 Lookup command handler for command: QUIT
> DEBUG 16:04:14,371 | james.smtpserver | ID=1002379024 org.apache.james.protocols.smtp.core.QuitCmdHandler: 221 [2.0.0 xxx.xxx.xxx.xxx Service closing transmission channel]
> DEBUG 16:04:14,387 | james.smtpserver | Unable to process request
> java.io.IOException: An established connection was aborted by the software in your host machine
> at sun.nio.ch.SocketDispatcher.write0(Native Method)
> at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:33)
> at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
> at sun.nio.ch.IOUtil.write(IOUtil.java:60)
> at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
> at org.jboss.netty.channel.socket.nio.SocketSendBufferPool$PooledSendBuffer.transferTo(SocketSendBufferPool.java:239)
> at org.jboss.netty.channel.socket.nio.NioWorker.write0(NioWorker.java:469)
> at org.jboss.netty.channel.socket.nio.NioWorker.writeFromUserCode(NioWorker.java:387)
> at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:137)
> at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:76)
> at org.jboss.netty.channel.Channels.write(Channels.java:632)
> at org.jboss.netty.channel.Channels.write(Channels.java:593)
> at org.jboss.netty.handler.ssl.SslHandler.wrapNonAppData(SslHandler.java:803)
> at org.jboss.netty.handler.ssl.SslHandler.closeOutboundAndChannel(SslHandler.java:1045)
> at org.jboss.netty.handler.ssl.SslHandler.handleDownstream(SslHandler.java:409)
> at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:60)
> at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:114)
> at org.jboss.netty.channel.Channels.close(Channels.java:720)
> at org.jboss.netty.channel.AbstractChannel.close(AbstractChannel.java:208)
> at org.apache.james.protocols.impl.AbstractSession.writeResponse(AbstractSession.java:156)
> at org.apache.james.protocols.api.AbstractCommandDispatcher.onLine(AbstractCommandDispatcher.java:161)
> at org.apache.james.protocols.impl.AbstractChannelUpstreamHandler.messageReceived(AbstractChannelUpstreamHandler.java:122)
> at org.jboss.netty.handler.timeout.IdleStateHandler.messageReceived(IdleStateHandler.java:276)
> at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:148)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349)
> at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:280)
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:200)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
>
> The email always seems to be delivered without issues. The exception itself does not seem to cause any problems for an end user. I wouldn't have seen this exception if I didn't happen to turn on debugging. But it gnaws at me now that I know it happens. Has anyone experienced anything like this? Perhaps I have the wrong configuration somewhere...
> Thanks,
> Vanessa Pao
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Connection Aborted exception in james-server.log
Posted by Daniel Tan <pu...@hotmail.com>.
hey there, though i can't help you with your query, is squirrelmail working well on your system? i didn't know squirrelmail can work.
it would be helpful if you could point me to the tutorial.
On 25-May-2011, at 4:21 AM, Pao, Vanessa wrote:
> Hi all,
> I am using James 3 (james-server-container-spring-3.0-M3-20110401.133250-93-bin.zip) and SquirrelMail 1.4.21 on a Windows 2008 R2 machine. I have James and SquirrelMail configured for SMTP with TLS and IMAP with TLS.
> I notice when I have log4j.logger.james.smtpserver=DEBUG in log4j.properties and I try to send emails with or without attachments, I see the following in james-server.log:
> INFO 16:04:14,364 | james.smtpserver | ID=1002379024 Successfully spooled mail Mail1306267454200-d428f133-fc33-4ff8-a33e-c6b794af95e4 from admin1@mail.com on 127.0.0.1 for [admin2@mail.com]
> DEBUG 16:04:14,364 | james.smtpserver | ID=1002379024 executing hook org.apache.james.protocols.smtp.core.log.HookResultLogger@c9bf922
> DEBUG 16:04:14,364 | james.smtpserver | ID=1002379024 org.apache.james.smtpserver.SendMailHandler: result=1 (OK)
> DEBUG 16:04:14,365 | james.smtpserver | ID=1002379024 executing hook org.apache.james.smtpserver.jmx.HookResultJMXMonitor@54012da5
> DEBUG 16:04:14,370 | james.smtpserver | ID=1002379024 org.apache.james.protocols.smtp.core.SMTPCommandDispatcherLineHandler received: QUIT
> DEBUG 16:04:14,370 | james.smtpserver | ID=1002379024 Lookup command handler for command: QUIT
> DEBUG 16:04:14,371 | james.smtpserver | ID=1002379024 org.apache.james.protocols.smtp.core.QuitCmdHandler: 221 [2.0.0 xxx.xxx.xxx.xxx Service closing transmission channel]
> DEBUG 16:04:14,387 | james.smtpserver | Unable to process request
> java.io.IOException: An established connection was aborted by the software in your host machine
> at sun.nio.ch.SocketDispatcher.write0(Native Method)
> at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:33)
> at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
> at sun.nio.ch.IOUtil.write(IOUtil.java:60)
> at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
> at org.jboss.netty.channel.socket.nio.SocketSendBufferPool$PooledSendBuffer.transferTo(SocketSendBufferPool.java:239)
> at org.jboss.netty.channel.socket.nio.NioWorker.write0(NioWorker.java:469)
> at org.jboss.netty.channel.socket.nio.NioWorker.writeFromUserCode(NioWorker.java:387)
> at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:137)
> at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:76)
> at org.jboss.netty.channel.Channels.write(Channels.java:632)
> at org.jboss.netty.channel.Channels.write(Channels.java:593)
> at org.jboss.netty.handler.ssl.SslHandler.wrapNonAppData(SslHandler.java:803)
> at org.jboss.netty.handler.ssl.SslHandler.closeOutboundAndChannel(SslHandler.java:1045)
> at org.jboss.netty.handler.ssl.SslHandler.handleDownstream(SslHandler.java:409)
> at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:60)
> at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:114)
> at org.jboss.netty.channel.Channels.close(Channels.java:720)
> at org.jboss.netty.channel.AbstractChannel.close(AbstractChannel.java:208)
> at org.apache.james.protocols.impl.AbstractSession.writeResponse(AbstractSession.java:156)
> at org.apache.james.protocols.api.AbstractCommandDispatcher.onLine(AbstractCommandDispatcher.java:161)
> at org.apache.james.protocols.impl.AbstractChannelUpstreamHandler.messageReceived(AbstractChannelUpstreamHandler.java:122)
> at org.jboss.netty.handler.timeout.IdleStateHandler.messageReceived(IdleStateHandler.java:276)
> at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:148)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349)
> at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:280)
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:200)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
>
> The email always seems to be delivered without issues. The exception itself does not seem to cause any problems for an end user. I wouldn't have seen this exception if I didn't happen to turn on debugging. But it gnaws at me now that I know it happens. Has anyone experienced anything like this? Perhaps I have the wrong configuration somewhere...
> Thanks,
> Vanessa Pao
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org