[
https://issues.apache.org/jira/browse/JAMES-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974862#action_12974862
]
Norman Maurer edited comment on JAMES-1154 at 12/24/10 3:32 AM:
----------------------------------------------------------------
Does this only happen with Mailets that alter the message body or do you see
the same issue with Mailets that just alter the headers (like AddHeader) ?
The smtpserver does queue the mail to activemq after receiving it. From there
it get dequeued via the JamesMailSpooler and dispatched to
CamelCompositeProcessor. The CamelCompositeProcessor then dispatch the mail to
one of its CamelMailetProcessor's depending on the Mail.getState() String. So
the smtpserver and the rest is complete decoupled..
was (Author: norman):
DOE
> changes to message content not persisted (timing issue?)
> --------------------------------------------------------
>
> Key: JAMES-1154
> URL: https://issues.apache.org/jira/browse/JAMES-1154
> Project: JAMES Server
> Issue Type: Bug
> Affects Versions: Trunk
> Environment: Windows 7, JDK1.6, Eclipse Helios
> Reporter: Andrew Tomlinson
>
> AddFooter (or any mailer that changes the content) is not working
> consistently.
> Logging confirms that the content is being updated but the message received
> through POP (or IMAP) is the original content.
> It seems to be a timing issue.
> If I debug and add a breakpoint on attachFooter and wait on that breakpoint
> for the smtp connection to close then it works OK.
> A working log might look like this - note the delay after the smtp connection
> closes and the local delivery.
> <code>
> DEBUG 16:41:59,533 | james.smtpserver | ID=629808856 executing james message
> handler org.apache.james.smtpserver.sendmailhand...@13a45c84
> DEBUG 16:41:59,533 | james.smtpserver | ID=629808856 sending mail
> INFO 16:41:59,541 | james.smtpserver | ID=629808856 Successfully spooled
> mail Mail1293140519532-40d17952-a80b-45f9-b14d-49da390a682d from
> [email protected] on 192.168.1.101 for [[email protected]]
> DEBUG 16:41:59,541 | james.smtpserver | ID=629808856 executing hook
> org.apache.james.protocols.smtp.core.log.hookresultlog...@3324298d
> DEBUG 16:41:59,541 | james.smtpserver | ID=629808856
> org.apache.james.smtpserver.SendMailHandler: result=1 (OK)
> DEBUG 16:41:59,550 | james.mailetcontainer | Call MailProcessor root
> DEBUG 16:41:59,555 | james.mailetcontainer | Call MailProcessor transport
> DEBUG 16:42:02,045 | james.smtpserver | ID=629808856
> org.apache.james.protocols.smtp.core.SMTPCommandDispatcherLineHandler
> received: QUIT
> DEBUG 16:42:05,049 | james.smtpserver | ID=629808856 Lookup command handler
> for command: QUIT
> DEBUG 16:42:05,050 | james.smtpserver | ID=629808856
> org.apache.james.protocols.smtp.core.QuitCmdHandler: 221 [2.0.0 192.168.1.101
> Service closing transmission channel]
> INFO 16:42:05,051 | james.smtpserver | ID=629808856 Connection closed for
> Excelsis.frameworks.local (192.168.1.101)
> DEBUG 16:42:05,052 | james.smtpserver | ID=629808856
> org.apache.james.protocols.smtp.core.SMTPCommandDispatcherLineHandler
> disconnect=false
> INFO 16:42:11,719 | james.mailetcontainer | Local delivered mail
> Mail1293140519532-40d17952-a80b-45f9-b14d-49da390a682d sucessfully from
> [email protected] to [email protected]
> DEBUG 16:42:11,720 | james.mailetcontainer | End of mailetcontainerroot
> reached
> </code>
> However if I remove the breakpoint it just does not work. This is regardless
> of message mime-type or content
> Now the log is like this.
> <code
> DEBUG 17:07:42,017 | james.smtpserver | ID=78749786 sending mail
> INFO 17:07:42,025 | james.smtpserver | ID=78749786 Successfully spooled mail
> Mail1293142062015-23af9e15-65ed-4a5c-855c-88986f57d2b3 from
> [email protected] on 192.168.1.101 for [[email protected]]
> DEBUG 17:07:42,026 | james.smtpserver | ID=78749786 executing hook
> org.apache.james.protocols.smtp.core.log.hookresultlog...@3324298d
> DEBUG 17:07:42,026 | james.smtpserver | ID=78749786
> org.apache.james.smtpserver.SendMailHandler: result=1 (OK)
> DEBUG 17:07:42,032 | james.mailetcontainer | Call MailProcessor root
> DEBUG 17:07:42,038 | james.mailetcontainer | Call MailProcessor transport
> INFO 17:07:42,099 | james.mailetcontainer | Local delivered mail
> Mail1293142062015-23af9e15-65ed-4a5c-855c-88986f57d2b3 sucessfully from
> [email protected] to [email protected]
> DEBUG 17:07:42,100 | james.mailetcontainer | End of mailetcontainerroot
> reached
> DEBUG 17:07:44,529 | james.smtpserver | ID=78749786
> org.apache.james.protocols.smtp.core.SMTPCommandDispatcherLineHandler
> received: QUIT
> DEBUG 17:07:44,529 | james.smtpserver | ID=78749786 Lookup command handler
> for command: QUIT
> DEBUG 17:07:44,529 | james.smtpserver | ID=78749786
> org.apache.james.protocols.smtp.core.QuitCmdHandler: 221 [2.0.0 192.168.1.101
> Service closing transmission channel]
> INFO 17:07:44,530 | james.smtpserver | ID=78749786 Connection closed for
> Excelsis.frameworks.local (192.168.1.101)
> DEBUG 17:07:44,530 | james.smtpserver | ID=78749786
> org.apache.james.protocols.smtp.core.SMTPCommandDispatcherLineHandler
> disconnect=false
> </code>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
