[jira] [Commented] (IMAP-363) Unable to read mails using Lotus Notes client
[ https://issues.apache.org/jira/browse/IMAP-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250558#comment-13250558 ] Norman Maurer commented on IMAP-363: It seems like your PassportIMAPAuthenticator class has a bug: DEBUG 15:45:59,160 | james.imapserver | ID=1878360884 Error while processing imap request java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(Unknown Source) at com.datacert.james.PassportIMAPAuthenticator.isAuthentic(PassportIMAPAuthenticator.java:17) at org.apache.james.mailbox.store.StoreMailboxManager.login(StoreMailboxManager.java:228) at org.apache.james.mailbox.store.StoreMailboxManager.login(StoreMailboxManager.java:236) at org.apache.james.imap.processor.AbstractAuthProcessor.doAuth(AbstractAuthProcessor.java:56) at org.apache.james.imap.processor.LoginProcessor.doProcess(LoginProcessor.java:53) at org.apache.james.imap.processor.LoginProcessor.doProcess(LoginProcessor.java:36) at org.apache.james.imap.processor.AbstractMailboxProcessor.doProcess(AbstractMailboxProcessor.java:90) at org.apache.james.imap.processor.AbstractMailboxProcessor.process(AbstractMailboxProcessor.java:79) at org.apache.james.imap.processor.AbstractMailboxProcessor.doProcess(AbstractMailboxProcessor.java:73) at org.apache.james.imap.processor.AbstractMailboxProcessor.doProcess(AbstractMailboxProcessor.java:56) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:55) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imap.processor.base.AbstractChainedProcessor.process(AbstractChainedProcessor.java:57) at org.apache.james.imapserver.netty.ImapChannelUpstreamHandler.messageReceived(ImapChannelUpstreamHandler.java:175) at org.jboss.netty.handler.stream.ChunkedWri
[jira] [Commented] (IMAP-351) ACL Support
[ https://issues.apache.org/jira/browse/IMAP-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195536#comment-13195536 ] Norman Maurer commented on IMAP-351: I merged the patch into trunk. Thanks again for this work its really a massive patch :) > ACL Support > --- > > Key: IMAP-351 > URL: https://issues.apache.org/jira/browse/IMAP-351 > Project: JAMES Imap > Issue Type: New Feature > Components: JCR Mailbox, JPA Mailbox, Mailbox, Maildir Mailbox, > Parser, Processor, Protocol >Affects Versions: 0.3 >Reporter: Jochen Gazda > Labels: ACL, IMAP > Fix For: 0.3 > > Attachments: IMAP-GETACL.txt, ImapGetACLTest.java > > Original Estimate: 672h > Remaining Estimate: 672h > > Support for RFC 4314 IMAP4 Access Control List (ACL) Extension -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (IMAP-351) ACL Support
[ https://issues.apache.org/jira/browse/IMAP-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194014#comment-13194014 ] Norman Maurer commented on IMAP-351: I noticed there is an author tag which includes a name like "Peter ...". Who is he ? Can he also comment here and give us his ok to include the code ? Just to be save... > ACL Support > --- > > Key: IMAP-351 > URL: https://issues.apache.org/jira/browse/IMAP-351 > Project: JAMES Imap > Issue Type: New Feature > Components: JCR Mailbox, JPA Mailbox, Mailbox, Maildir Mailbox, > Parser, Processor, Protocol >Affects Versions: 0.3 >Reporter: Jochen Gazda > Labels: ACL, IMAP > Fix For: 0.3 > > Attachments: IMAP-GETACL.txt, ImapGetACLTest.java > > Original Estimate: 672h > Remaining Estimate: 672h > > Support for RFC 4314 IMAP4 Access Control List (ACL) Extension -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JSIEVE-80) Add the ability to advertise the available Sieve extensions
[ https://issues.apache.org/jira/browse/JSIEVE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193692#comment-13193692 ] Norman Maurer commented on JSIEVE-80: - @Steve: You are right, I was just short in time and wanted to raise it before I forget ;) I will take care of creating the issue later.. > Add the ability to advertise the available Sieve extensions > --- > > Key: JSIEVE-80 > URL: https://issues.apache.org/jira/browse/JSIEVE-80 > Project: JAMES jSieve > Issue Type: Improvement > Components: JSieve (Main) >Affects Versions: 0.5 >Reporter: Steve Brewin >Assignee: Steve Brewin > Fix For: 0.5 > > > Add a new method to SieveFactory, List getExtensions(), to answer the > Sieve extensions implemented by jSieve. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JSIEVE-80) Add the ability to advertise the available Sieve extensions
[ https://issues.apache.org/jira/browse/JSIEVE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193299#comment-13193299 ] Norman Maurer commented on JSIEVE-80: - Maybe Set getExtensions() would be better ? > Add the ability to advertise the available Sieve extensions > --- > > Key: JSIEVE-80 > URL: https://issues.apache.org/jira/browse/JSIEVE-80 > Project: JAMES jSieve > Issue Type: Improvement > Components: JSieve (Main) >Affects Versions: 0.5 >Reporter: Steve Brewin >Assignee: Steve Brewin > Fix For: 0.5 > > > Add a new method to SieveFactory, List getExtensions(), to answer the > Sieve extensions implemented by jSieve. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1360) Use protocols 1.6.0-RC2-SNAPSHOT
[ https://issues.apache.org/jira/browse/JAMES-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181899#comment-13181899 ] Norman Maurer commented on JAMES-1360: -- I will have a look later today... > Use protocols 1.6.0-RC2-SNAPSHOT > > > Key: JAMES-1360 > URL: https://issues.apache.org/jira/browse/JAMES-1360 > Project: JAMES Server > Issue Type: New Feature >Affects Versions: Trunk >Reporter: Eric Charles >Assignee: Eric Charles > Fix For: 3.0-beta4 > > > There are a bunch of API changes between protocols-1.6-beta3 and > protocols-1.6.0-RC2-SNAPSHOT. > We need to update server code (mainly pop3/imap/smtp server projects) to > align to the current protocols implementation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (PROTOCOLS-76) Remove dependency on slf4j
[ https://issues.apache.org/jira/browse/PROTOCOLS-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176210#comment-13176210 ] Norman Maurer commented on PROTOCOLS-76: I need to adjust server code to use PROTOCOLS 1.6.0-RC1. I will do this later. The problem with java.util.Logger is that it suxx in so many ways :( > Remove dependency on slf4j > -- > > Key: PROTOCOLS-76 > URL: https://issues.apache.org/jira/browse/PROTOCOLS-76 > Project: JAMES Protocols > Issue Type: Task > Components: api >Affects Versions: 1.6.0-RC1 >Reporter: Norman Maurer >Assignee: Norman Maurer > Fix For: 1.6.0 > > > We should remove the dependency on slf4j as a no-dependency api is kind of > sexy. We should just use our own Logger interface and then provide an adapter > in the netty module -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (PROTOCOLS-73) Move imap code into protocols
[ https://issues.apache.org/jira/browse/PROTOCOLS-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175847#comment-13175847 ] Norman Maurer commented on PROTOCOLS-73: I will do the development in trunk. When we need a new release before I'm done, we can still exclude the module. > Move imap code into protocols > - > > Key: PROTOCOLS-73 > URL: https://issues.apache.org/jira/browse/PROTOCOLS-73 > Project: JAMES Protocols > Issue Type: New Feature > Components: imap >Affects Versions: 1.6.0-RC1 >Reporter: Norman Maurer >Assignee: Norman Maurer > Fix For: 2.0.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (PROTOCOLS-76) Remove dependency on slf4j
[ https://issues.apache.org/jira/browse/PROTOCOLS-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175810#comment-13175810 ] Norman Maurer commented on PROTOCOLS-76: I know this section but I don't agree ;) In our implementation (james-server) we will still use slf4j and so provide the "adapter" class. > Remove dependency on slf4j > -- > > Key: PROTOCOLS-76 > URL: https://issues.apache.org/jira/browse/PROTOCOLS-76 > Project: JAMES Protocols > Issue Type: Task > Components: api >Affects Versions: 1.6.0-RC1 >Reporter: Norman Maurer >Assignee: Norman Maurer > Fix For: 1.6.0 > > > We should remove the dependency on slf4j as a no-dependency api is kind of > sexy. We should just use our own Logger interface and then provide an adapter > in the netty module -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JSIEVE-79) Implement a mechanism for users to manage their Sieve scripts via SMTP
[ https://issues.apache.org/jira/browse/JSIEVE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175466#comment-13175466 ] Norman Maurer commented on JSIEVE-79: - I think it would make more sense to implement a sievemanager directly in PROTOCOLS. https://issues.apache.org/jira/browse/PROTOCOLS-68 > Implement a mechanism for users to manage their Sieve scripts via SMTP > -- > > Key: JSIEVE-79 > URL: https://issues.apache.org/jira/browse/JSIEVE-79 > Project: JAMES jSieve > Issue Type: Improvement >Reporter: Steve Brewin >Priority: Minor > > The ability to do this safely requires the security of an authenticated SMTP > session, but if this exists why not use it to allow users to manage their > Sieve scripts by mail? > Simple get and put operations should be sufficient. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JSIEVE-79) Implement a mechanism for users to manage their Sieve scripts via SMTP
[ https://issues.apache.org/jira/browse/JSIEVE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175467#comment-13175467 ] Norman Maurer commented on JSIEVE-79: - I think it would make more sense to implement a sievemanager directly in PROTOCOLS. https://issues.apache.org/jira/browse/PROTOCOLS-68 > Implement a mechanism for users to manage their Sieve scripts via SMTP > -- > > Key: JSIEVE-79 > URL: https://issues.apache.org/jira/browse/JSIEVE-79 > Project: JAMES jSieve > Issue Type: Improvement >Reporter: Steve Brewin >Priority: Minor > > The ability to do this safely requires the security of an authenticated SMTP > session, but if this exists why not use it to allow users to manage their > Sieve scripts by mail? > Simple get and put operations should be sufficient. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (PROTOCOLS-21) Document protocols web site for 1.4 release
[ https://issues.apache.org/jira/browse/PROTOCOLS-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173235#comment-13173235 ] Norman Maurer commented on PROTOCOLS-21: @eric what about this ? > Document protocols web site for 1.4 release > --- > > Key: PROTOCOLS-21 > URL: https://issues.apache.org/jira/browse/PROTOCOLS-21 > Project: JAMES Protocols > Issue Type: Improvement >Reporter: Eric Charles >Assignee: Eric Charles > > Document protocols web site for 1.4 release -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (PROTOCOLS-46) HashedWheelTimer get not stopped on AbstractAsyncServer.unbind()
[ https://issues.apache.org/jira/browse/PROTOCOLS-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139395#comment-13139395 ] Norman Maurer commented on PROTOCOLS-46: This leads to leaking resources > HashedWheelTimer get not stopped on AbstractAsyncServer.unbind() > > > Key: PROTOCOLS-46 > URL: https://issues.apache.org/jira/browse/PROTOCOLS-46 > Project: JAMES Protocols > Issue Type: Bug >Affects Versions: 1.6-beta2 >Reporter: Norman Maurer >Assignee: Norman Maurer > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (HUPA-80) Use slf4j as log facade
[ https://issues.apache.org/jira/browse/HUPA-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123394#comment-13123394 ] Norman Maurer commented on HUPA-80: --- Huh... I never saw such problems here. Can you please open a issue in JAMES project and attach more details ? > Use slf4j as log facade > --- > > Key: HUPA-80 > URL: https://issues.apache.org/jira/browse/HUPA-80 > Project: JAMES Hupa > Issue Type: Task >Affects Versions: 0.1 >Reporter: Felix Knecht > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1327) FileSystemBlobStrategy#getFile(ActiveMQBlobMessage) is not thread safe (throws "java.io.IOException: Unable to create directory")
[
https://issues.apache.org/jira/browse/JAMES-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122788#comment-13122788
]
Norman Maurer commented on JAMES-1327:
--
What about creating a patch file... We love contributions :)
> FileSystemBlobStrategy#getFile(ActiveMQBlobMessage) is not thread safe
> (throws "java.io.IOException: Unable to create directory")
> -
>
> Key: JAMES-1327
> URL: https://issues.apache.org/jira/browse/JAMES-1327
> Project: JAMES Server
> Issue Type: Bug
> Components: Queue
>Affects Versions: 3.0-beta3
> Environment: At least Windows and Linux.
>Reporter: Michael Herrmann
>
> Consider
> org.apache.james.queue.activemq.FileSystemBlobStrategy#getFile(ActiveMQBlobMessage):
> protected File getFile(ActiveMQBlobMessage message) throws JMSException,
> IOException {
> ...
> // check if we need to create the queue folder
> if (queueF.exists() == false) {
> if (!queueF.mkdirs()) {
> throw new IOException("Unable to create directory " +
> queueF.getAbsolutePath());
> }
> }
> ...
> }
> Suppose this method is called from two threads. If both threads get past the
> condition
> if (queueF.exists() == false),
> then the first one will create queueF. For the second, queueF.mkdirs() will
> then return false, which leads to an IOException even though everything is
> fine. I think the condition should be replaced by
> if (!queueF.mkdirs() && !queueF.exists()).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1317) Mail spooled but not processed
[ https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121777#comment-13121777 ] Norman Maurer commented on JAMES-1317: -- Sure... just send it to my email > Mail spooled but not processed > -- > > Key: JAMES-1317 > URL: https://issues.apache.org/jira/browse/JAMES-1317 > Project: JAMES Server > Issue Type: Bug > Components: SpoolManager & Processors >Affects Versions: 3.0-M1, 3.0-M2, 3.0-beta3 >Reporter: Raju Buchi >Priority: Critical > Fix For: 3.0-beta4 > > Attachments: Dump.txt, Dump2.txt, > james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, > james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, jstack.zip, > logs.zip, logs.zip > > > Mails sent to James server are spooled but they are not processed and sent > out. > The issue is similar to the one faced by Zach. > The server seems to be working fine for a few hours or few days, but some > time all the mails are spooled but they will not be processed and sent out. > Restarted the server several times and some time a few of the mails will be > processed and all the others are lost. > As Norman suggested I have took a jstack trace. > Please let me how we can resolve this issue > Thanks > - Raju -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1317) Mail spooled but not processed
[ https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121133#comment-13121133 ] Norman Maurer commented on JAMES-1317: -- Imwonder if we can write a unit test that reproduce the issue. > Mail spooled but not processed > -- > > Key: JAMES-1317 > URL: https://issues.apache.org/jira/browse/JAMES-1317 > Project: JAMES Server > Issue Type: Bug > Components: SpoolManager & Processors >Affects Versions: 3.0-M1, 3.0-M2, 3.0-beta3 >Reporter: Raju Buchi >Priority: Critical > Fix For: 3.0-beta4 > > Attachments: Dump.txt, Dump2.txt, > james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, > james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, jstack.zip, > logs.zip, logs.zip > > > Mails sent to James server are spooled but they are not processed and sent > out. > The issue is similar to the one faced by Zach. > The server seems to be working fine for a few hours or few days, but some > time all the mails are spooled but they will not be processed and sent out. > Restarted the server several times and some time a few of the mails will be > processed and all the others are lost. > As Norman suggested I have took a jstack trace. > Please let me how we can resolve this issue > Thanks > - Raju -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1317) Mail spooled but not processed
[ https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120863#comment-13120863 ] Norman Maurer commented on JAMES-1317: -- Let me know your findings > Mail spooled but not processed > -- > > Key: JAMES-1317 > URL: https://issues.apache.org/jira/browse/JAMES-1317 > Project: JAMES Server > Issue Type: Bug > Components: SpoolManager & Processors >Affects Versions: 3.0-M1, 3.0-M2, 3.0-beta3 >Reporter: Raju Buchi >Priority: Critical > Fix For: 3.0-beta4 > > Attachments: Dump.txt, Dump2.txt, > james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, > james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, jstack.zip, > logs.zip, logs.zip > > > Mails sent to James server are spooled but they are not processed and sent > out. > The issue is similar to the one faced by Zach. > The server seems to be working fine for a few hours or few days, but some > time all the mails are spooled but they will not be processed and sent out. > Restarted the server several times and some time a few of the mails will be > processed and all the others are lost. > As Norman suggested I have took a jstack trace. > Please let me how we can resolve this issue > Thanks > - Raju -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1317) Mail spooled but not processed
[ https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120354#comment-13120354 ] Norman Maurer commented on JAMES-1317: -- For me it looks like all jdbc connections are in use.. What were the OS again ? > Mail spooled but not processed > -- > > Key: JAMES-1317 > URL: https://issues.apache.org/jira/browse/JAMES-1317 > Project: JAMES Server > Issue Type: Bug > Components: SpoolManager & Processors >Affects Versions: 3.0-M1, 3.0-M2, 3.0-beta3 >Reporter: Raju Buchi >Priority: Critical > Fix For: 3.0-beta4 > > Attachments: Dump.txt, Dump2.txt, > james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, > james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, jstack.zip, > logs.zip, logs.zip > > > Mails sent to James server are spooled but they are not processed and sent > out. > The issue is similar to the one faced by Zach. > The server seems to be working fine for a few hours or few days, but some > time all the mails are spooled but they will not be processed and sent out. > Restarted the server several times and some time a few of the mails will be > processed and all the others are lost. > As Norman suggested I have took a jstack trace. > Please let me how we can resolve this issue > Thanks > - Raju -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1317) Mail spooled but not processed
[ https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120050#comment-13120050 ] Norman Maurer commented on JAMES-1317: -- What db are you using ? > Mail spooled but not processed > -- > > Key: JAMES-1317 > URL: https://issues.apache.org/jira/browse/JAMES-1317 > Project: JAMES Server > Issue Type: Bug > Components: SpoolManager & Processors >Affects Versions: 3.0-M1, 3.0-M2, 3.0-beta3 >Reporter: Raju Buchi >Priority: Critical > Fix For: 3.0-beta4 > > Attachments: Dump.txt, Dump2.txt, > james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, > james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, jstack.zip, > logs.zip, logs.zip > > > Mails sent to James server are spooled but they are not processed and sent > out. > The issue is similar to the one faced by Zach. > The server seems to be working fine for a few hours or few days, but some > time all the mails are spooled but they will not be processed and sent out. > Restarted the server several times and some time a few of the mails will be > processed and all the others are lost. > As Norman suggested I have took a jstack trace. > Please let me how we can resolve this issue > Thanks > - Raju -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1317) Mail spooled but not processed
[ https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120010#comment-13120010 ] Norman Maurer commented on JAMES-1317: -- Wh000t! I will cleanup the fix and commit later... > Mail spooled but not processed > -- > > Key: JAMES-1317 > URL: https://issues.apache.org/jira/browse/JAMES-1317 > Project: JAMES Server > Issue Type: Bug > Components: SpoolManager & Processors >Affects Versions: 3.0-M1, 3.0-M2, 3.0-beta3 >Reporter: Raju Buchi >Priority: Critical > Fix For: 3.0-beta4 > > Attachments: Dump.txt, > james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, > james-server-mailetcontainer-camel-3.0-beta4-SNAPSHOT.jar, jstack.zip, > logs.zip > > > Mails sent to James server are spooled but they are not processed and sent > out. > The issue is similar to the one faced by Zach. > The server seems to be working fine for a few hours or few days, but some > time all the mails are spooled but they will not be processed and sent out. > Restarted the server several times and some time a few of the mails will be > processed and all the others are lost. > As Norman suggested I have took a jstack trace. > Please let me how we can resolve this issue > Thanks > - Raju -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1317) Mail spooled but not processed
[ https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119493#comment-13119493 ] Norman Maurer commented on JAMES-1317: -- A.. sorry I think I may be wrong on the "has nothing todo with the problem". I think if you not call "mail.getMessage().saveChanges();" It will get hit by the Mailet again and again and so may end up in a infinity loop. Can you try to add the "saveChanges();" and see if it makes any difference ? > Mail spooled but not processed > -- > > Key: JAMES-1317 > URL: https://issues.apache.org/jira/browse/JAMES-1317 > Project: JAMES Server > Issue Type: Bug > Components: SpoolManager & Processors >Affects Versions: 3.0-M1, 3.0-M2, 3.0-beta3 >Reporter: Raju Buchi >Priority: Critical > Fix For: 3.0-beta4 > > Attachments: Dump.txt, jstack.zip, logs.zip > > > Mails sent to James server are spooled but they are not processed and sent > out. > The issue is similar to the one faced by Zach. > The server seems to be working fine for a few hours or few days, but some > time all the mails are spooled but they will not be processed and sent out. > Restarted the server several times and some time a few of the mails will be > processed and all the others are lost. > As Norman suggested I have took a jstack trace. > Please let me how we can resolve this issue > Thanks > - Raju -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1317) Mail spooled but not processed
[ https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119476#comment-13119476 ] Norman Maurer commented on JAMES-1317: -- @Michael, BTW, you need to call MimeMessage.saveChanges() after you mess with the headers (like change Mail From: and RCPT TO). This has nothing todo with the problem but I just wanted to let you know.. > Mail spooled but not processed > -- > > Key: JAMES-1317 > URL: https://issues.apache.org/jira/browse/JAMES-1317 > Project: JAMES Server > Issue Type: Bug > Components: SpoolManager & Processors >Affects Versions: 3.0-M1, 3.0-M2, 3.0-beta3 >Reporter: Raju Buchi >Priority: Critical > Fix For: 3.0-beta4 > > Attachments: Dump.txt, jstack.zip, logs.zip > > > Mails sent to James server are spooled but they are not processed and sent > out. > The issue is similar to the one faced by Zach. > The server seems to be working fine for a few hours or few days, but some > time all the mails are spooled but they will not be processed and sent out. > Restarted the server several times and some time a few of the mails will be > processed and all the others are lost. > As Norman suggested I have took a jstack trace. > Please let me how we can resolve this issue > Thanks > - Raju -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1317) Mail spooled but not processed
[ https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119442#comment-13119442 ] Norman Maurer commented on JAMES-1317: -- Hi Michael, what OS you are running JAMES on ? > Mail spooled but not processed > -- > > Key: JAMES-1317 > URL: https://issues.apache.org/jira/browse/JAMES-1317 > Project: JAMES Server > Issue Type: Bug > Components: SpoolManager & Processors >Affects Versions: 3.0-M1, 3.0-M2, 3.0-beta3 >Reporter: Raju Buchi >Priority: Critical > Fix For: 3.0-beta4 > > Attachments: Dump.txt, jstack.zip, logs.zip > > > Mails sent to James server are spooled but they are not processed and sent > out. > The issue is similar to the one faced by Zach. > The server seems to be working fine for a few hours or few days, but some > time all the mails are spooled but they will not be processed and sent out. > Restarted the server several times and some time a few of the mails will be > processed and all the others are lost. > As Norman suggested I have took a jstack trace. > Please let me how we can resolve this issue > Thanks > - Raju -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1317) Mail spooled but not processed
[ https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119389#comment-13119389 ] Norman Maurer commented on JAMES-1317: -- I will review the thread-dump and logs later today and come back to you > Mail spooled but not processed > -- > > Key: JAMES-1317 > URL: https://issues.apache.org/jira/browse/JAMES-1317 > Project: JAMES Server > Issue Type: Bug > Components: SpoolManager & Processors >Affects Versions: 3.0-M1, 3.0-M2, 3.0-beta3 >Reporter: Raju Buchi >Priority: Critical > Fix For: 3.0-beta4 > > Attachments: Dump.txt, jstack.zip, logs.zip > > > Mails sent to James server are spooled but they are not processed and sent > out. > The issue is similar to the one faced by Zach. > The server seems to be working fine for a few hours or few days, but some > time all the mails are spooled but they will not be processed and sent out. > Restarted the server several times and some time a few of the mails will be > processed and all the others are lost. > As Norman suggested I have took a jstack trace. > Please let me how we can resolve this issue > Thanks > - Raju -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (MAILBOX-141) Do not synchronize on objects that may be reused
[ https://issues.apache.org/jira/browse/MAILBOX-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117453#comment-13117453 ] Norman Maurer commented on MAILBOX-141: --- What about this: http://svn.apache.org/viewvc?rev=1177375&view=rev ? > Do not synchronize on objects that may be reused > > > Key: MAILBOX-141 > URL: https://issues.apache.org/jira/browse/MAILBOX-141 > Project: James Mailbox > Issue Type: Bug > Components: store >Affects Versions: 0.4 >Reporter: Felix Knecht >Priority: Critical > > public Iterator search has a synchronization on the Boolean 'done' > https://builds.apache.org/view/G-L/view/James/job/mailbox-site/site/apache-james-mailbox-store/findbugs.html#org.apache.james.mailbox.store.search.LazyMessageSearchIndex > See > http://findbugs.sourceforge.net/bugDescriptions.html#DL_SYNCHRONIZATION_ON_BOOLEAN > https://www.securecoding.cert.org/confluence/display/java/LCK01-J.+Do+not+synchronize+on+objects+that+may+be+reused -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1317) Mail spooled but not processed
[ https://issues.apache.org/jira/browse/JAMES-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117445#comment-13117445 ] Norman Maurer commented on JAMES-1317: -- I wonder if there are still some issues when using activemq for the queue as Zach is using FileMailQueueFactory. Anyway please provide a thread-dump while you see the problems and attach it here so we can have a deeper look > Mail spooled but not processed > -- > > Key: JAMES-1317 > URL: https://issues.apache.org/jira/browse/JAMES-1317 > Project: JAMES Server > Issue Type: Bug > Components: SpoolManager & Processors >Affects Versions: 3.0-M1, 3.0-M2, 3.0-beta3 >Reporter: Raju Buchi >Priority: Critical > Fix For: 3.0-beta4 > > Attachments: jstack.zip > > > Mails sent to James server are spooled but they are not processed and sent > out. > The issue is similar to the one faced by Zach. > The server seems to be working fine for a few hours or few days, but some > time all the mails are spooled but they will not be processed and sent out. > Restarted the server several times and some time a few of the mails will be > processed and all the others are lost. > As Norman suggested I have took a jstack trace. > Please let me how we can resolve this issue > Thanks > - Raju -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
