[jira] [Updated] (MAILBOX-223) ACL interfaces refactor
[ https://issues.apache.org/jira/browse/MAILBOX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler updated MAILBOX-223: -- Attachment: 0002-MAILBOX-223-Remove-MaildirMailbox-use-SimpleMailbox-.patch 0001-MAILBOX-223-Update-API-so-that-ACL-operation-are-acc.patch patches generated from github PR. ACL interfaces refactor --- Key: MAILBOX-223 URL: https://issues.apache.org/jira/browse/MAILBOX-223 Project: James Mailbox Issue Type: Improvement Reporter: Tellier Benoit Attachments: 0001-MAILBOX-223-Update-API-so-that-ACL-operation-are-acc.patch, 0002-MAILBOX-223-Remove-MaildirMailbox-use-SimpleMailbox-.patch ACL management should be delegated to mailbox manager. Updating ACL should be done in the MailboxMapper to allow implementation specific operations. We should not overwrite the SimpleMailbox Bean to achieve our goals. Currently available implementation should not have changed behavior. Hence Maildir implementation need to be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (MAILBOX-222) Use java 8 for Cassandra Backend
[ https://issues.apache.org/jira/browse/MAILBOX-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler updated MAILBOX-222: -- Attachment: 0001-MAILBOX-222-disable-build-of-cassandra-module-when-j.patch Patch generated from github PR Use java 8 for Cassandra Backend Key: MAILBOX-222 URL: https://issues.apache.org/jira/browse/MAILBOX-222 Project: James Mailbox Issue Type: Improvement Reporter: Matthieu Baechler Priority: Minor Fix For: 0.6 Attachments: 0001-MAILBOX-222-disable-build-of-cassandra-module-when-j.patch Cassandra backend will use jdk8. We must require java 8 to compile it but just ignore this module when using java 8 to prevent build from breaking in this configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (MAILBOX-221) Make sure we use Java-6-only API
[ https://issues.apache.org/jira/browse/MAILBOX-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler updated MAILBOX-221: -- Attachment: 0001-MAILBOX-221-enforce-use-of-jdk-6-at-build-time.patch Patch generated from the github PR Make sure we use Java-6-only API Key: MAILBOX-221 URL: https://issues.apache.org/jira/browse/MAILBOX-221 Project: James Mailbox Issue Type: Improvement Reporter: Matthieu Baechler Priority: Minor Fix For: 0.6 Attachments: 0001-MAILBOX-221-enforce-use-of-jdk-6-at-build-time.patch Java compiler is not able to detect the use of non-java-6 API when compiled with Java 7 or Java 8. It only detects language-level features. However, there's a maven plugin that can check this. It's very valuable in a context of heterogeneous modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Comment Edited] (MAILBOX-223) ACL interfaces refactor
[
https://issues.apache.org/jira/browse/MAILBOX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513054#comment-14513054
]
Matthieu Baechler edited comment on MAILBOX-223 at 4/26/15 2:35 PM:
You can't just check the first patch then the second as the second uses parts
of the first.
To apply the patches, you can simply run {code}git am 000{1,2}* {code}
I've just checked here and it seems ok.
was (Author: matthieub):
You can't just check the first patch then the second as the second uses parts
of the first.
To apply the patches, you can simply run git am 000{1,2}*
I've just checked here and it seems ok.
ACL interfaces refactor
---
Key: MAILBOX-223
URL: https://issues.apache.org/jira/browse/MAILBOX-223
Project: James Mailbox
Issue Type: Improvement
Reporter: Tellier Benoit
Attachments:
0001-MAILBOX-223-Update-API-so-that-ACL-operation-are-acc.patch,
0002-MAILBOX-223-Remove-MaildirMailbox-use-SimpleMailbox-.patch
ACL management should be delegated to mailbox manager.
Updating ACL should be done in the MailboxMapper to allow implementation
specific operations. We should not overwrite the SimpleMailbox Bean to
achieve our goals.
Currently available implementation should not have changed behavior. Hence
Maildir implementation need to be updated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (MAILBOX-223) ACL interfaces refactor
[
https://issues.apache.org/jira/browse/MAILBOX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513054#comment-14513054
]
Matthieu Baechler commented on MAILBOX-223:
---
You can't just check the first patch then the second as the second uses parts
of the first.
To apply the patches, you can simply run git am 000{1,2}*
I've just checked here and it seems ok.
ACL interfaces refactor
---
Key: MAILBOX-223
URL: https://issues.apache.org/jira/browse/MAILBOX-223
Project: James Mailbox
Issue Type: Improvement
Reporter: Tellier Benoit
Attachments:
0001-MAILBOX-223-Update-API-so-that-ACL-operation-are-acc.patch,
0002-MAILBOX-223-Remove-MaildirMailbox-use-SimpleMailbox-.patch
ACL management should be delegated to mailbox manager.
Updating ACL should be done in the MailboxMapper to allow implementation
specific operations. We should not overwrite the SimpleMailbox Bean to
achieve our goals.
Currently available implementation should not have changed behavior. Hence
Maildir implementation need to be updated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1522) Running james 3.0beta5 fails due to unsatisfied dependencies
[ https://issues.apache.org/jira/browse/JAMES-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507147#comment-14507147 ] Matthieu Baechler commented on JAMES-1522: -- Could you please give us your configuration files ? Running james 3.0beta5 fails due to unsatisfied dependencies Key: JAMES-1522 URL: https://issues.apache.org/jira/browse/JAMES-1522 Project: James Server Issue Type: Bug Components: Build System, James Core Affects Versions: Trunk Reporter: Lee Hanxue Labels: build Fix For: 3.0.0-beta5 When starting James server after a clean build, this is the error that is produced: WARN 00:48:07,605 | org.springframework.beans.factory.support.DisposableBeanAdapter | Invocation of destroy method failed on bean with name 'entityManagerFactory': openjpa-2.2.1-r422266:1396819 nonfatal user error org.apache.openjpa.persistence.InvalidStateException: This operation failed for some instances. See the nested exceptions array for details. Exception in thread main org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'mailprocessor' defined in class path resource [META-INF/spring/mailetcontainer-context.xml]: Unsatisfied dependency expressed through bean property 'mailetContext': : Error creating bean with name 'mailetcontext' defined in class path resource [META-INF/spring/mailetcontainer-context.xml]: Initialization of bean failed; nested exception is org.springframework.beans.FatalBeanException: Unable to execute lifecycle method on beanmailetcontext; nested exception is openjpa-2.2.1-r422266:1396819 nonfatal user error org.apache.openjpa.persistence.InvalidStateException: This operation cannot be performed while a Transaction is active.; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mailetcontext' defined in class path resource [META-INF/spring/mailetcontainer-context.xml]: Initialization of bean failed; nested exception is org.springframework.beans.FatalBeanException: Unable to execute lifecycle method on beanmailetcontext; nested exception is openjpa-2.2.1-r422266:1396819 nonfatal user error org.apache.openjpa.persistence.InvalidStateException: This operation cannot be performed while a Transaction is active. at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireByType(AbstractAutowireCapableBeanFactory.java:1199) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1091) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:609) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:469) at org.springframework.context.support.ClassPathXmlApplicationContext.init(ClassPathXmlApplicationContext.java:139) at org.springframework.context.support.ClassPathXmlApplicationContext.init(ClassPathXmlApplicationContext.java:93) at org.apache.james.container.spring.context.JamesServerApplicationContext.init(JamesServerApplicationContext.java:39) at org.apache.james.app.spring.JamesAppSpringMain.init(JamesAppSpringMain.java:61) at org.apache.james.app.spring.JamesAppSpringMain.main(JamesAppSpringMain.java:42) Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mailetcontext' defined in class path resource [META-INF/spring/mailetcontainer-context.xml]: Initialization of bean failed; nested exception is org.springframework.beans.FatalBeanException: Unable to execute lifecycle method on beanmailetcontext; nested exception is
[jira] [Created] (JAMES-1571) james-project breaks apache-mime4j build
Matthieu Baechler created JAMES-1571: Summary: james-project breaks apache-mime4j build Key: JAMES-1571 URL: https://issues.apache.org/jira/browse/JAMES-1571 Project: James Server Issue Type: Bug Components: Build System Reporter: Matthieu Baechler When upgrading james-mime4j 0.7.2 to james-project 1.8.2, maven tries to create some jars for projects with packaging=pom. This is related to changes introduced by JAMES-1465. We should either rework JAMES-1465 or change maven-jar-plugin configuration in james-mime4j projects. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (MAILBOX-223) ACL interfaces refactor
[ https://issues.apache.org/jira/browse/MAILBOX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler updated MAILBOX-223: -- Attachment: (was: 0001-MAILBOX-223-Update-API-so-that-ACL-operation-are-acc.patch) ACL interfaces refactor --- Key: MAILBOX-223 URL: https://issues.apache.org/jira/browse/MAILBOX-223 Project: James Mailbox Issue Type: Improvement Reporter: Tellier Benoit Assignee: Eric Charles Fix For: 0.6 Attachments: 0001-MAILBOX-223-Update-API-so-that-ACL-operation-are-acc.patch ACL management should be delegated to mailbox manager. Updating ACL should be done in the MailboxMapper to allow implementation specific operations. We should not overwrite the SimpleMailbox Bean to achieve our goals. Currently available implementation should not have changed behavior. Hence Maildir implementation need to be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (MAILBOX-223) ACL interfaces refactor
[ https://issues.apache.org/jira/browse/MAILBOX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler updated MAILBOX-223: -- Attachment: (was: 0002-MAILBOX-223-Remove-MaildirMailbox-use-SimpleMailbox-.patch) ACL interfaces refactor --- Key: MAILBOX-223 URL: https://issues.apache.org/jira/browse/MAILBOX-223 Project: James Mailbox Issue Type: Improvement Reporter: Tellier Benoit Assignee: Eric Charles Fix For: 0.6 Attachments: 0001-MAILBOX-223-Update-API-so-that-ACL-operation-are-acc.patch ACL management should be delegated to mailbox manager. Updating ACL should be done in the MailboxMapper to allow implementation specific operations. We should not overwrite the SimpleMailbox Bean to achieve our goals. Currently available implementation should not have changed behavior. Hence Maildir implementation need to be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JSIEVE-97) James JSieve should use latest version of other James subprojects
Matthieu Baechler created JSIEVE-97: --- Summary: James JSieve should use latest version of other James subprojects Key: JSIEVE-97 URL: https://issues.apache.org/jira/browse/JSIEVE-97 Project: James jSieve Issue Type: Task Components: MultiModule Reporter: Matthieu Baechler Fix For: 0.6 It should depend on james-project 1.8.3-SNAPSHOT and mime4j 0.8 to use only up-to-date component. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JSIEVE-97) James JSieve should use latest version of other James subprojects
[ https://issues.apache.org/jira/browse/JSIEVE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler updated JSIEVE-97: Attachment: 0001-JWC-111-Updating-parent-project.patch This patch update dependencies and fix a call to mime4j. James JSieve should use latest version of other James subprojects - Key: JSIEVE-97 URL: https://issues.apache.org/jira/browse/JSIEVE-97 Project: James jSieve Issue Type: Task Components: MultiModule Reporter: Matthieu Baechler Fix For: 0.6 Attachments: 0001-JWC-111-Updating-parent-project.patch It should depend on james-project 1.8.3-SNAPSHOT and mime4j 0.8 to use only up-to-date component. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (MAILBOX-223) ACL interfaces refactor
[ https://issues.apache.org/jira/browse/MAILBOX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler updated MAILBOX-223: -- Attachment: 0001-MAILBOX-223-Update-API-so-that-ACL-operation-are-acc.patch This patch is a merge of previous patches. ACL interfaces refactor --- Key: MAILBOX-223 URL: https://issues.apache.org/jira/browse/MAILBOX-223 Project: James Mailbox Issue Type: Improvement Reporter: Tellier Benoit Attachments: 0001-MAILBOX-223-Update-API-so-that-ACL-operation-are-acc.patch, 0001-MAILBOX-223-Update-API-so-that-ACL-operation-are-acc.patch, 0002-MAILBOX-223-Remove-MaildirMailbox-use-SimpleMailbox-.patch ACL management should be delegated to mailbox manager. Updating ACL should be done in the MailboxMapper to allow implementation specific operations. We should not overwrite the SimpleMailbox Bean to achieve our goals. Currently available implementation should not have changed behavior. Hence Maildir implementation need to be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MPT-12) Run MTP test suite on Cassandra backend
Matthieu Baechler created MPT-12: Summary: Run MTP test suite on Cassandra backend Key: MPT-12 URL: https://issues.apache.org/jira/browse/MPT-12 Project: James MPT Issue Type: Improvement Reporter: Matthieu Baechler We would like to check that James over cassandra pass all mpt tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (MAILBOX-223) ACL interfaces refactor
[ https://issues.apache.org/jira/browse/MAILBOX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517822#comment-14517822 ] Matthieu Baechler commented on MAILBOX-223: --- It should be removed. ACL interfaces refactor --- Key: MAILBOX-223 URL: https://issues.apache.org/jira/browse/MAILBOX-223 Project: James Mailbox Issue Type: Improvement Reporter: Tellier Benoit Assignee: Eric Charles Fix For: 0.6 Attachments: 0001-MAILBOX-223-Update-API-so-that-ACL-operation-are-acc.patch ACL management should be delegated to mailbox manager. Updating ACL should be done in the MailboxMapper to allow implementation specific operations. We should not overwrite the SimpleMailbox Bean to achieve our goals. Currently available implementation should not have changed behavior. Hence Maildir implementation need to be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (MAILBOX-230) Mailbox should use latest version of other James subprojects
[ https://issues.apache.org/jira/browse/MAILBOX-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14539984#comment-14539984 ] Matthieu Baechler commented on MAILBOX-230: --- Eric, could you please merge these patches ? It's a blocker for us. Mailbox should use latest version of other James subprojects Key: MAILBOX-230 URL: https://issues.apache.org/jira/browse/MAILBOX-230 Project: James Mailbox Issue Type: Improvement Reporter: Antoine Duprat Fix For: 0.6 Attachments: 0001-JWC-111-update-james-related-projects-to-SNAPSHOT-ve.patch, 0002-JWC-111-update-mime4j-to-0.8.0-SNAPSHOT.patch We want an integration tool that builds the entire James project in its latest version. To do that, each james project needs to use the latest version of all other James subprojects. In JDKIM, this means : - Update mailet version - Update james-project version - Update mime4j version -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-385) Allow to prevent weak ciphers when using useTLS
[ https://issues.apache.org/jira/browse/JAMES-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483365#comment-14483365 ] Matthieu Baechler commented on JAMES-385: - Does this ticket still need work ? Allow to prevent weak ciphers when using useTLS - Key: JAMES-385 URL: https://issues.apache.org/jira/browse/JAMES-385 Project: James Server Issue Type: Bug Components: SMTPServer Affects Versions: 2.2.0, 2.3.0, 2.3.1, 2.3.2, 3.0-M1, 3.0-M2 Environment: Linux, jdk 1.4 Reporter: Ralf Hauser Assignee: Eric Charles Priority: Critical Fix For: 3.0-beta3, 3.0.0-beta5 Attachments: Cornerstone.patch.zip http://james.apache.org/usingTLS_2_1.html and http://wiki.apache.org/james/UsingSSL explain how to setup a pop3s etc. describe how to secure a client connection to James. openssl s_client -connect pops.mydom.com:995 -cipher EXPORT illustrates that this is possible with james. One might argue that a decent client will never ask the server to negotiate a weak cipher. But an attacker (man-in-the-middle) could remove stronger ciphers from the client's offered cipher list, and then break the weak cipher and e.g. obtain the user password to later hijack the account. Please amend the documentation how prevent this from happening by forcing james to only negotiate sessions with 128+ bit session key strength -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-236) Strong type for Mailbox Message ids
Matthieu Baechler created MAILBOX-236: - Summary: Strong type for Mailbox Message ids Key: MAILBOX-236 URL: https://issues.apache.org/jira/browse/MAILBOX-236 Project: James Mailbox Issue Type: Improvement Reporter: Matthieu Baechler I'd like to bring something that bothers me : whenever you get an Id from a Message or a Mailbox, you can only call Object methods. It makes some code rely on toString() call in case of serialization. If you put aside some special types, toString is not supposed to return a stable and meaningful value. I'd like to make Message and Mailbox use a bounded parameters. This parameter would extend an Id interface, and this interface could have a serialize method. Comments welcome (and patch is coming soon) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (MAILBOX-236) Strong type for Mailbox id
[ https://issues.apache.org/jira/browse/MAILBOX-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler updated MAILBOX-236: -- Description: I'd like to bring something that bothers me : whenever you get an Id from a Mailbox, you can only call Object methods. It makes some code rely on toString() call in case of serialization. If you put aside some special types, toString is not supposed to return a stable and meaningful value. I'd like to make Message and Mailbox use a bounded parameters. This parameter would extend an Id interface, and this interface could have a serialize method. Comments welcome (and patch is coming soon) was: I'd like to bring something that bothers me : whenever you get an Id from a Message or a Mailbox, you can only call Object methods. It makes some code rely on toString() call in case of serialization. If you put aside some special types, toString is not supposed to return a stable and meaningful value. I'd like to make Message and Mailbox use a bounded parameters. This parameter would extend an Id interface, and this interface could have a serialize method. Comments welcome (and patch is coming soon) Summary: Strong type for Mailbox id (was: Strong type for Mailbox Message ids) Strong type for Mailbox id -- Key: MAILBOX-236 URL: https://issues.apache.org/jira/browse/MAILBOX-236 Project: James Mailbox Issue Type: Improvement Reporter: Matthieu Baechler I'd like to bring something that bothers me : whenever you get an Id from a Mailbox, you can only call Object methods. It makes some code rely on toString() call in case of serialization. If you put aside some special types, toString is not supposed to return a stable and meaningful value. I'd like to make Message and Mailbox use a bounded parameters. This parameter would extend an Id interface, and this interface could have a serialize method. Comments welcome (and patch is coming soon) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1588) Create a project to centralize Cassandra tools
[ https://issues.apache.org/jira/browse/JAMES-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14653259#comment-14653259 ] Matthieu Baechler commented on JAMES-1588: -- In Cassandra case, it's technical things like : cassandra java driver, extensions to this driver, libraries we use to write tests (like cassandra-unit that allows to start an embedded cassandra using a JUnit @Rule), Session factory and tables creation tools. Create a project to centralize Cassandra tools -- Key: JAMES-1588 URL: https://issues.apache.org/jira/browse/JAMES-1588 Project: James Server Issue Type: Improvement Reporter: Tellier Benoit As we are starting to develop data tools based on Cassandra, we realized we would use tools we defined for the Cassandra mailbox. But : - We don't want a dependency to the cassandra mailbox in our data-cassandra module - We do not want to duplicate information. Hence we prefer introducing a new module, that centralize tools needed by modules relying on Cassandra ( for now the Cassandra mailbox, and the data-cassandra module, Cassandra MPT module ). As we think this can be a common need to several backend implementation, we want to create a dedicated project for centralizing back-end tools, that will be calles james-backends. Each back-end ( eg : cassandra, jpa, hbase, etc ... ) will create its submodule in it and will use it in other places (MPT, Mailbox, james (server) ). Let us now if you have any feedback on this proposal. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1588) Create a project to centralize Cassandra tools
[ https://issues.apache.org/jira/browse/JAMES-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14653268#comment-14653268 ] Matthieu Baechler commented on JAMES-1588: -- Are you thinking to put this backends module at the same level as server, mailbox...? Exactly I proposed the same kind of module some time ago, but we decided to not follow that way. Looking back , it sound like this would not have been the best thing to do (release management...). You are right one this point : it makes building James even more difficult. But duplicating libraries doesn't seems a good idea neither. The other way would be to merge all james modules in one structure to make a single release. This may be worth to start a discussion on the maliling list. Thank you very much to bring this subject to discussion : we are struggling for months to find a good workflow to work on James. The split repositories is a hell to manage, you can see our james-parent repository (https://github.com/linagora/james-parent) where we aggregate git repositories with git submodule. But everything is much harder that way and if we start a discussion on the mailing list about repositories merge, I will be happy to push my arguments there. Create a project to centralize Cassandra tools -- Key: JAMES-1588 URL: https://issues.apache.org/jira/browse/JAMES-1588 Project: James Server Issue Type: Improvement Reporter: Tellier Benoit As we are starting to develop data tools based on Cassandra, we realized we would use tools we defined for the Cassandra mailbox. But : - We don't want a dependency to the cassandra mailbox in our data-cassandra module - We do not want to duplicate information. Hence we prefer introducing a new module, that centralize tools needed by modules relying on Cassandra ( for now the Cassandra mailbox, and the data-cassandra module, Cassandra MPT module ). As we think this can be a common need to several backend implementation, we want to create a dedicated project for centralizing back-end tools, that will be calles james-backends. Each back-end ( eg : cassandra, jpa, hbase, etc ... ) will create its submodule in it and will use it in other places (MPT, Mailbox, james (server) ). Let us now if you have any feedback on this proposal. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1586) Write a compliant Cassandra User Repository
[ https://issues.apache.org/jira/browse/JAMES-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652288#comment-14652288 ] Matthieu Baechler commented on JAMES-1586: -- Hi Eric, My old https://github.com/mbaechler/james/commits/cassandra branch contains user/domain/rtt storage in cassandra and ends with an unrelated guice commit. It's a just a base for JAMES-1586 and JAMES-1587 You can have a look at what we done here : https://github.com/linagora/james/pull/4. It's not pushed to Apache repository yet because we have to clean up our branches and open new PRs. About reusing mailbox cassandra infrastructure, it actually JAMES-1588 : we need to share the cassandra session between repositories, reuse the table creation code and that kind of tools. Nothing in the cassandra backend project contains any business logic, just technical stuff. Do you think it's ok ? Write a compliant Cassandra User Repository --- Key: JAMES-1586 URL: https://issues.apache.org/jira/browse/JAMES-1586 Project: James Server Issue Type: New Feature Reporter: Matthieu Baechler To complete the Cassandra backend, we should write a User Repository on top of Cassandra. There's already some code there : https://github.com/mbaechler/james/commits/cassandra but it can't be integrated as is, it needs some refactoring to use mailbox Cassandra infrastructure. Once done, we should update the spring configuration to deploy this repository and make sure integration tests on a deployed james still works. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1593) James Spooler performance issue
[ https://issues.apache.org/jira/browse/JAMES-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640052#comment-14640052 ] Matthieu Baechler commented on JAMES-1593: -- I agree James shouldn't use something broken by default. Can you provide us with a test case that triggers this bug ? James Spooler performance issue --- Key: JAMES-1593 URL: https://issues.apache.org/jira/browse/JAMES-1593 Project: James Server Issue Type: Bug Components: SMTPServer Affects Versions: 3.0-beta4 Environment: Linux , CentOS release 6.6 (Final), Reporter: Mehdi Salarkia Labels: newbie, performance We have a mail system based on Apache james and we are experiencing some performance issues . The current implementation of Apache james has a dependency on Apache Geronimo for mime and mail processing and it seems there is an issue at-least in the version geronimo-javamail_1.4_mail package . It seems like the javax.mail.internet.MimeMessage.getEncoding() method never finishes and when I look at the cpu and I profiled the application it shows this method has a high cpu consumtion, here is a jstack of what was happening at the time: spooler-1 daemon prio=10 tid=0x2b3ee9a5 nid=0x57b4 runnable [0x2b3e8388d000] java.lang.Thread.State: RUNNABLE at javax.mail.internet.MimeMessage.getEncoding(MimeMessage.java:751) at org.apache.james.core.MimeMessageUtil.writeMessageBodyTo(MimeMessageUtil.java:135) at org.apache.james.core.MimeMessageWrapper.writeTo(MimeMessageWrapper.java:338) - locked 0x00060ceef588 (a org.apache.james.core.MimeMessageWrapper) at org.apache.james.mailrepository.file.FileMailRepository.internalStore(FileMailRepository.java:203) at org.apache.james.mailrepository.lib.AbstractMailRepository.store(AbstractMailRepository.java:98) at org.apache.james.transport.mailets.ToRepository.service(ToRepository.java:91) at org.apache.james.mailetcontainer.impl.camel.CamelProcessor.process(CamelProcessor.java:65) at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:334) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:220) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:81) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at
[jira] [Commented] (JAMES-1593) James Spooler performance issue
[ https://issues.apache.org/jira/browse/JAMES-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638334#comment-14638334 ] Matthieu Baechler commented on JAMES-1593: -- geronimo-javamail is supposed to be API compatible with javax.mail. If you have a look at mailbox/pom.xml, you can see that there's a profile to compile with geronimo (the default being using javax.mail). You could use the same trick to make it possible to choose the javamail implementation in other modules in order to try javax.mail for your actual problem. James Spooler performance issue --- Key: JAMES-1593 URL: https://issues.apache.org/jira/browse/JAMES-1593 Project: James Server Issue Type: Bug Components: SMTPServer Affects Versions: 3.0-beta4 Environment: Linux , CentOS release 6.6 (Final), Reporter: Mehdi Salarkia Labels: newbie, performance We have a mail system based on Apache james and we are experiencing some performance issues . The current implementation of Apache james has a dependency on Apache Geronimo for mime and mail processing and it seems there is an issue at-least in the version geronimo-javamail_1.4_mail package . It seems like the javax.mail.internet.MimeMessage.getEncoding() method never finishes and when I look at the cpu and I profiled the application it shows this method has a high cpu consumtion, here is a jstack of what was happening at the time: spooler-1 daemon prio=10 tid=0x2b3ee9a5 nid=0x57b4 runnable [0x2b3e8388d000] java.lang.Thread.State: RUNNABLE at javax.mail.internet.MimeMessage.getEncoding(MimeMessage.java:751) at org.apache.james.core.MimeMessageUtil.writeMessageBodyTo(MimeMessageUtil.java:135) at org.apache.james.core.MimeMessageWrapper.writeTo(MimeMessageWrapper.java:338) - locked 0x00060ceef588 (a org.apache.james.core.MimeMessageWrapper) at org.apache.james.mailrepository.file.FileMailRepository.internalStore(FileMailRepository.java:203) at org.apache.james.mailrepository.lib.AbstractMailRepository.store(AbstractMailRepository.java:98) at org.apache.james.transport.mailets.ToRepository.service(ToRepository.java:91) at org.apache.james.mailetcontainer.impl.camel.CamelProcessor.process(CamelProcessor.java:65) at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:334) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:220) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:81) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at
[jira] [Created] (JAMES-1586) Write a compliant Cassandra User Repository
Matthieu Baechler created JAMES-1586: Summary: Write a compliant Cassandra User Repository Key: JAMES-1586 URL: https://issues.apache.org/jira/browse/JAMES-1586 Project: James Server Issue Type: New Feature Reporter: Matthieu Baechler To complete the Cassandra backend, we should write a User Repository on top of Cassandra. There's already some code there : https://github.com/mbaechler/james/commits/cassandra but it can't be integrated as is, it needs some refactoring to use mailbox Cassandra infrastructure. Once done, we should update the spring configuration to deploy this repository and make sure integration tests on a deployed james still works. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1603) cli should not depend on james-server-spring
Matthieu Baechler created JAMES-1603: Summary: cli should not depend on james-server-spring Key: JAMES-1603 URL: https://issues.apache.org/jira/browse/JAMES-1603 Project: James Server Issue Type: Bug Components: CLI Reporter: Matthieu Baechler cli depends on james-server-spring to access MailboxCopierManagementMBean interface. It's probably a simple mistake to fix, MBeans are usually into data-api module, we should have to move MailboxCopierManagementMBean to data-api too. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1624) karaf build failure on james trunk on mvn package
[ https://issues.apache.org/jira/browse/JAMES-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler closed JAMES-1624. Resolution: Fixed merged > karaf build failure on james trunk on mvn package > - > > Key: JAMES-1624 > URL: https://issues.apache.org/jira/browse/JAMES-1624 > Project: James Server > Issue Type: Bug > Components: Build System >Affects Versions: Trunk, 3.0.0-beta5 > Environment: ➜ james-trunk uname -a > Darwin wdx-me 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT > 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64 > ➜ james-trunk java -version > java version "1.7.0_17" > Java(TM) SE Runtime Environment (build 1.7.0_17-b02) > Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode) > ➜ james-trunk mvn -v > Apache Maven 3.0.3 (r1075438; 2011-03-01 01:31:09+0800) > Maven home: /usr/share/maven > Java version: 1.7.0_17, vendor: Oracle Corporation > Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac" > ➜ james-trunk svn info > Path: . > Working Copy Root Path: /Users/wdx/art/open/james/james-trunk > URL: http://svn.apache.org/repos/asf/james/server/trunk > Repository Root: http://svn.apache.org/repos/asf > Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 > Revision: 1487220 > Node Kind: directory > Schedule: normal > Last Changed Author: eric > Last Changed Rev: 1476802 > Last Changed Date: 2013-04-29 01:23:37 +0800 (一, 29 4 2013) >Reporter: Matthieu Baechler > Fix For: Trunk, 3.0.0-beta5 > > > $ mvn clean package -X -DskipTests=true > .. > .. > [INFO] Apache James :: Server SUCCESS [2.266s] > [INFO] Apache James :: Server :: Data :: API SUCCESS [2.375s] > [INFO] Apache James :: Server :: Lifecycle API ... SUCCESS [0.987s] > [INFO] Apache James :: Server :: Filesystem API .. SUCCESS [1.124s] > [INFO] Apache James :: Server :: Mailetcontainer API . SUCCESS [0.701s] > [INFO] Apache James :: Server :: Common Utilities SUCCESS [1.575s] > [INFO] Apache James :: Server :: Protocols Library ... SUCCESS [1.181s] > [INFO] Apache James :: Server :: Core SUCCESS [1.092s] > [INFO] Apache James :: Server :: Container Spring SUCCESS [2.466s] > [INFO] Apache James :: Server :: Client .. SUCCESS [1.088s] > [INFO] Apache James :: Server :: DNS Service :: API .. SUCCESS [0.363s] > [INFO] Apache James :: Server :: DNS Service :: Library .. SUCCESS [0.638s] > [INFO] Apache James :: Server :: Mail Queue :: API ... SUCCESS [0.497s] > [INFO] Apache James :: Server :: Mailetcontainer Camel ... SUCCESS [1.471s] > [INFO] Apache James :: Server :: Mailbox Adapter . SUCCESS [0.658s] > [INFO] Apache James :: Server :: DNS Service :: Implementation SUCCESS > [0.480s] > [INFO] Apache James :: Server :: Data :: Library . SUCCESS [0.974s] > [INFO] Apache James :: Server :: Data :: LDAP Implementation SUCCESS [0.483s] > [INFO] Apache James :: Server :: SMTP SUCCESS [1.684s] > [INFO] Apache James :: Server :: IMAP SUCCESS [0.641s] > [INFO] Apache James :: Server :: LMTP SUCCESS [0.811s] > [INFO] Apache James :: Server :: POP3 SUCCESS [0.829s] > [INFO] Apache James :: Server :: FetchMail ... SUCCESS [0.632s] > [INFO] Apache James :: Server :: Mail Queue :: File .. SUCCESS [0.519s] > [INFO] Apache James :: Server :: Mail Queue :: JMS ... SUCCESS [0.964s] > [INFO] Apache James :: Server :: Mail Queue :: ActiveMQ .. SUCCESS [0.898s] > [INFO] Apache James :: Server :: Mailets . SUCCESS [1.878s] > [INFO] Apache James :: Server :: Data :: File Persistence SUCCESS [0.719s] > [INFO] Apache James :: Server :: Data :: JPA Persistence . SUCCESS [1.664s] > [INFO] Apache James :: Server :: Data :: JDBC Persistence SUCCESS [1.177s] > [INFO] Apache James :: Server :: Data :: HBase Persistence SUCCESS [3.562s] > [INFO] Apache James :: Server :: Data :: JCR Persistence . SUCCESS [1.035s] > [INFO] Apache James :: Server :: App . SUCCESS [9.655s] > [INFO] Apache James :: Karaf :: Features . SUCCESS [0.342s] > [INFO] Apache James :: Karaf :: James Server . FAILURE [7.591s] > [INFO] Apache James :: Karaf :: Integration tests SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 57.322s > [INFO] Finished at: Wed May 29
[jira] [Commented] (MPT-34) MPT tests requires docker to be installed
[ https://issues.apache.org/jira/browse/MPT-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978491#comment-14978491 ] Matthieu Baechler commented on MPT-34: -- Would you agree to put it in a profile and disable it if DOCKER_HOST env is not set ? > MPT tests requires docker to be installed > - > > Key: MPT-34 > URL: https://issues.apache.org/jira/browse/MPT-34 > Project: James MPT > Issue Type: Bug >Reporter: Tellier Benoit > Attachments: james-cyrus.log > > > On trunk, MPT::Cyrus tests requires docker to be installed. Otherwise, tests > fails. > I think mpt/impl/cyrus tests should be disactivated unless you use a specific > profile. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1588) Create a project to centralize Cassandra tools
[ https://issues.apache.org/jira/browse/JAMES-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980501#comment-14980501 ] Matthieu Baechler commented on JAMES-1588: -- [~BTellier] can you close this ticket, it's now merged. > Create a project to centralize Cassandra tools > -- > > Key: JAMES-1588 > URL: https://issues.apache.org/jira/browse/JAMES-1588 > Project: James Server > Issue Type: Improvement >Reporter: Tellier Benoit > > As we are starting to develop data tools based on Cassandra, we realized we > would use tools we defined for the Cassandra mailbox. But : > - We don't want a dependency to the cassandra mailbox in our data-cassandra > module > - We do not want to duplicate information. > Hence we prefer introducing a new module, that centralize tools needed by > modules relying on Cassandra ( for now the Cassandra mailbox, and the > data-cassandra module, Cassandra MPT module ). > As we think this can be a common need to several backend implementation, we > want to create a dedicated project for centralizing back-end tools, that will > be calles james-backends. Each back-end ( eg : cassandra, jpa, hbase, etc ... > ) will create its submodule in it and will use it in other places (MPT, > Mailbox, james (server) ). > Let us now if you have any feedback on this proposal. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Comment Edited] (JAMES-1630) CDI deplyoment exeption for james WAR
[ https://issues.apache.org/jira/browse/JAMES-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980062#comment-14980062 ] Matthieu Baechler edited comment on JAMES-1630 at 10/29/15 8:52 AM: could you attach your spring configuration files ? was (Author: matthieub): could you attach your spring configuration files ? w > CDI deplyoment exeption for james WAR > - > > Key: JAMES-1630 > URL: https://issues.apache.org/jira/browse/JAMES-1630 > Project: James Server > Issue Type: Bug > Components: James Core, MailStore & MailRepository >Affects Versions: Trunk > Environment: JDK 1.8.65, Glassfish 4.1, Apache JAMES WAR from trunk >Reporter: Mario > > This is the stake trace note you have to build the project with -P > with-assembly to get the WAR file. > [2015-10-28T16:55:57.559+] [glassfish 4.1] [INFO] [] > [org.glassfish.admingui] [tid: _ThreadID=51 _ThreadName=admin-listener(2)] > [timeMillis: 1446051357559] [levelValue: 800] [[ > uploadFileName=james-server-app-3.0.0-beta5-SNAPSHOT.war]] > [2015-10-28T16:56:03.004+] [glassfish 4.1] [SEVERE] [NCLS-CORE-00026] > [javax.enterprise.system.core] [tid: _ThreadID=53 > _ThreadName=admin-listener(4)] [timeMillis: 1446051363004] [levelValue: 1000] > [[ > Exception during lifecycle processing > org.glassfish.deployment.common.DeploymentException: CDI deployment > failure:Exception List with 4 exceptions: > Exception 0 : > org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied > dependencies for type MailboxSessionMapperFactory with qualifiers @Default > at injection point [BackedAnnotatedParameter] Parameter 1 of > [BackedAnnotatedConstructor] @Inject public > org.apache.james.mailbox.store.quota.DefaultQuotaRootResolver(MailboxSessionMapperFactory) > at > org.apache.james.mailbox.store.quota.DefaultQuotaRootResolver.(DefaultQuotaRootResolver.java:0) > at > org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:370) > at > org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:291) > at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134) > at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:165) > at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:529) > at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:515) > at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:490) > at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:419) > at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:90) > at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:225) > at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131) > at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:328) > at > com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:496) > at > com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:219) > at > org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:491) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:539) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:535) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:360) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:534) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:565) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:557) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:360) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:556) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1464) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1300(CommandRunnerImpl.java:109) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1846) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1722) > at > org.glassfish.admin.rest.utils.ResourceUtil.runCommand(ResourceUtil.java:253) > at > org.glassfish.admin.rest.utils.ResourceUtil.runCommand(ResourceUtil.java:231) > at > org.glassfish.admin.rest.utils.ResourceUtil.runCommand(ResourceUtil.java:275) > at > org.glassfish.admin.rest.resources.TemplateListOfResource.createResource(TemplateListOfResource.java:133) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at >
[jira] [Commented] (JAMES-1630) CDI deplyoment exeption for james WAR
[ https://issues.apache.org/jira/browse/JAMES-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980062#comment-14980062 ] Matthieu Baechler commented on JAMES-1630: -- could you attach your spring configuration files ? w > CDI deplyoment exeption for james WAR > - > > Key: JAMES-1630 > URL: https://issues.apache.org/jira/browse/JAMES-1630 > Project: James Server > Issue Type: Bug > Components: James Core, MailStore & MailRepository >Affects Versions: Trunk > Environment: JDK 1.8.65, Glassfish 4.1, Apache JAMES WAR from trunk >Reporter: Mario > > This is the stake trace note you have to build the project with -P > with-assembly to get the WAR file. > [2015-10-28T16:55:57.559+] [glassfish 4.1] [INFO] [] > [org.glassfish.admingui] [tid: _ThreadID=51 _ThreadName=admin-listener(2)] > [timeMillis: 1446051357559] [levelValue: 800] [[ > uploadFileName=james-server-app-3.0.0-beta5-SNAPSHOT.war]] > [2015-10-28T16:56:03.004+] [glassfish 4.1] [SEVERE] [NCLS-CORE-00026] > [javax.enterprise.system.core] [tid: _ThreadID=53 > _ThreadName=admin-listener(4)] [timeMillis: 1446051363004] [levelValue: 1000] > [[ > Exception during lifecycle processing > org.glassfish.deployment.common.DeploymentException: CDI deployment > failure:Exception List with 4 exceptions: > Exception 0 : > org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied > dependencies for type MailboxSessionMapperFactory with qualifiers @Default > at injection point [BackedAnnotatedParameter] Parameter 1 of > [BackedAnnotatedConstructor] @Inject public > org.apache.james.mailbox.store.quota.DefaultQuotaRootResolver(MailboxSessionMapperFactory) > at > org.apache.james.mailbox.store.quota.DefaultQuotaRootResolver.(DefaultQuotaRootResolver.java:0) > at > org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:370) > at > org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:291) > at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134) > at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:165) > at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:529) > at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:515) > at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:490) > at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:419) > at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:90) > at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:225) > at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131) > at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:328) > at > com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:496) > at > com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:219) > at > org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:491) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:539) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:535) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:360) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:534) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:565) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:557) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:360) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:556) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1464) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1300(CommandRunnerImpl.java:109) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1846) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1722) > at > org.glassfish.admin.rest.utils.ResourceUtil.runCommand(ResourceUtil.java:253) > at > org.glassfish.admin.rest.utils.ResourceUtil.runCommand(ResourceUtil.java:231) > at > org.glassfish.admin.rest.utils.ResourceUtil.runCommand(ResourceUtil.java:275) > at > org.glassfish.admin.rest.resources.TemplateListOfResource.createResource(TemplateListOfResource.java:133) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at
[jira] [Created] (JAMES-1628) Provide some DockerFiles to have a standard environment to build and run James
Matthieu Baechler created JAMES-1628: Summary: Provide some DockerFiles to have a standard environment to build and run James Key: JAMES-1628 URL: https://issues.apache.org/jira/browse/JAMES-1628 Project: James Server Issue Type: Improvement Components: Build System Reporter: Matthieu Baechler By using docker to build and run James, it allows easy Quick Start (you just need docker) of James project. It also gives a reference environment for people to report problems. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (MAILBOX-77) Guice Mailbox Module
[ https://issues.apache.org/jira/browse/MAILBOX-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14974249#comment-14974249 ] Matthieu Baechler commented on MAILBOX-77: -- We did a guice mailbox module for cassandra. Actually, it doesn't make sense to write a module for Mailbox, you have to write one for each backend. I suggest, once you read JAMES-1626 (will come probably tomorrow in review), to close this ticket. We'll open tickets for every backends. > Guice Mailbox Module > > > Key: MAILBOX-77 > URL: https://issues.apache.org/jira/browse/MAILBOX-77 > Project: James Mailbox > Issue Type: New Feature >Reporter: Eric Charles >Assignee: Norman Maurer > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1479) Create a Guice module
[ https://issues.apache.org/jira/browse/JAMES-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14974140#comment-14974140 ] Matthieu Baechler commented on JAMES-1479: -- JAMES-1626 doesn't make all components guice-ready but most of them. > Create a Guice module > - > > Key: JAMES-1479 > URL: https://issues.apache.org/jira/browse/JAMES-1479 > Project: James Server > Issue Type: Improvement > Components: Deployment Modules >Affects Versions: 3.0.0-beta5 >Reporter: Eric Charles >Assignee: Eric Charles > > The guice module will allow to run the complete server with pure guice > injection. > It will also allow to embed any James component in any 3rd party Guice > application. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1477) Replace @Resource with @Inject where it can
[ https://issues.apache.org/jira/browse/JAMES-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14974237#comment-14974237 ] Matthieu Baechler commented on JAMES-1477: -- @Resource removal is actually done in JAMES-1626 but for Bayesian mailet (I actually have no idea how to test this). > Replace @Resource with @Inject where it can > --- > > Key: JAMES-1477 > URL: https://issues.apache.org/jira/browse/JAMES-1477 > Project: James Server > Issue Type: Sub-task >Reporter: Eric Charles >Assignee: Eric Charles > > This will allow also allow to work with different dependency injection > frameworks (spring, guice...). > See also JAMES-1237. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1628) Provide some DockerFiles to have a standard environment to build and run James
[ https://issues.apache.org/jira/browse/JAMES-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler closed JAMES-1628. Resolution: Fixed merged > Provide some DockerFiles to have a standard environment to build and run James > -- > > Key: JAMES-1628 > URL: https://issues.apache.org/jira/browse/JAMES-1628 > Project: James Server > Issue Type: Improvement > Components: Build System >Reporter: Matthieu Baechler > > By using docker to build and run James, it allows easy Quick Start (you just > need docker) of James project. > It also gives a reference environment for people to report problems. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1624) karaf build failure on james trunk on mvn package
[ https://issues.apache.org/jira/browse/JAMES-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14970600#comment-14970600 ] Matthieu Baechler commented on JAMES-1624: -- There something wrong in karaf distribution pom.xml, it tries to deploy artifacts from m2 repository even when running "package" goal, so artifacts are obviously not there. What about changing the phase to install ? (I'll open a PR for this but I need feedback) > karaf build failure on james trunk on mvn package > - > > Key: JAMES-1624 > URL: https://issues.apache.org/jira/browse/JAMES-1624 > Project: James Server > Issue Type: Bug > Components: Build System >Affects Versions: Trunk, 3.0.0-beta5 > Environment: ➜ james-trunk uname -a > Darwin wdx-me 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT > 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64 > ➜ james-trunk java -version > java version "1.7.0_17" > Java(TM) SE Runtime Environment (build 1.7.0_17-b02) > Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode) > ➜ james-trunk mvn -v > Apache Maven 3.0.3 (r1075438; 2011-03-01 01:31:09+0800) > Maven home: /usr/share/maven > Java version: 1.7.0_17, vendor: Oracle Corporation > Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac" > ➜ james-trunk svn info > Path: . > Working Copy Root Path: /Users/wdx/art/open/james/james-trunk > URL: http://svn.apache.org/repos/asf/james/server/trunk > Repository Root: http://svn.apache.org/repos/asf > Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 > Revision: 1487220 > Node Kind: directory > Schedule: normal > Last Changed Author: eric > Last Changed Rev: 1476802 > Last Changed Date: 2013-04-29 01:23:37 +0800 (一, 29 4 2013) >Reporter: Matthieu Baechler > Fix For: Trunk, 3.0.0-beta5 > > > $ mvn clean package -X -DskipTests=true > .. > .. > [INFO] Apache James :: Server SUCCESS [2.266s] > [INFO] Apache James :: Server :: Data :: API SUCCESS [2.375s] > [INFO] Apache James :: Server :: Lifecycle API ... SUCCESS [0.987s] > [INFO] Apache James :: Server :: Filesystem API .. SUCCESS [1.124s] > [INFO] Apache James :: Server :: Mailetcontainer API . SUCCESS [0.701s] > [INFO] Apache James :: Server :: Common Utilities SUCCESS [1.575s] > [INFO] Apache James :: Server :: Protocols Library ... SUCCESS [1.181s] > [INFO] Apache James :: Server :: Core SUCCESS [1.092s] > [INFO] Apache James :: Server :: Container Spring SUCCESS [2.466s] > [INFO] Apache James :: Server :: Client .. SUCCESS [1.088s] > [INFO] Apache James :: Server :: DNS Service :: API .. SUCCESS [0.363s] > [INFO] Apache James :: Server :: DNS Service :: Library .. SUCCESS [0.638s] > [INFO] Apache James :: Server :: Mail Queue :: API ... SUCCESS [0.497s] > [INFO] Apache James :: Server :: Mailetcontainer Camel ... SUCCESS [1.471s] > [INFO] Apache James :: Server :: Mailbox Adapter . SUCCESS [0.658s] > [INFO] Apache James :: Server :: DNS Service :: Implementation SUCCESS > [0.480s] > [INFO] Apache James :: Server :: Data :: Library . SUCCESS [0.974s] > [INFO] Apache James :: Server :: Data :: LDAP Implementation SUCCESS [0.483s] > [INFO] Apache James :: Server :: SMTP SUCCESS [1.684s] > [INFO] Apache James :: Server :: IMAP SUCCESS [0.641s] > [INFO] Apache James :: Server :: LMTP SUCCESS [0.811s] > [INFO] Apache James :: Server :: POP3 SUCCESS [0.829s] > [INFO] Apache James :: Server :: FetchMail ... SUCCESS [0.632s] > [INFO] Apache James :: Server :: Mail Queue :: File .. SUCCESS [0.519s] > [INFO] Apache James :: Server :: Mail Queue :: JMS ... SUCCESS [0.964s] > [INFO] Apache James :: Server :: Mail Queue :: ActiveMQ .. SUCCESS [0.898s] > [INFO] Apache James :: Server :: Mailets . SUCCESS [1.878s] > [INFO] Apache James :: Server :: Data :: File Persistence SUCCESS [0.719s] > [INFO] Apache James :: Server :: Data :: JPA Persistence . SUCCESS [1.664s] > [INFO] Apache James :: Server :: Data :: JDBC Persistence SUCCESS [1.177s] > [INFO] Apache James :: Server :: Data :: HBase Persistence SUCCESS [3.562s] > [INFO] Apache James :: Server :: Data :: JCR Persistence . SUCCESS [1.035s] > [INFO] Apache James :: Server :: App . SUCCESS [9.655s] > [INFO] Apache James :: Karaf :: Features . SUCCESS [0.342s] > [INFO] Apache James :: Karaf :: James Server . FAILURE [7.591s] > [INFO] Apache James :: Karaf :: Integration
[jira] [Comment Edited] (JAMES-1477) Replace @Resource with @Inject where it can
[ https://issues.apache.org/jira/browse/JAMES-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978174#comment-14978174 ] Matthieu Baechler edited comment on JAMES-1477 at 10/28/15 10:40 AM: - After struggling for some time, it looks like jsr 330 annotations are handled only when classpath scanning is enabled. [~e...@apache.org] do you see any problem activating classpath scanning on org.apache.james package ? was (Author: matthieub): After struggling for some time, it looks like jsr 330 annotation is handled only when classpath scanning is enabled. [~e...@apache.org] do you see any problem activating classpath scanning on org.apache.james package ? > Replace @Resource with @Inject where it can > --- > > Key: JAMES-1477 > URL: https://issues.apache.org/jira/browse/JAMES-1477 > Project: James Server > Issue Type: Sub-task >Reporter: Eric Charles >Assignee: Eric Charles > > This will allow also allow to work with different dependency injection > frameworks (spring, guice...). > See also JAMES-1237. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1640) Cant recive emails
[
https://issues.apache.org/jira/browse/JAMES-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006613#comment-15006613
]
Matthieu Baechler commented on JAMES-1640:
--
Hi Lukas,
The interesting part is
{code}Caused by: java.lang.NoSuchMethodError:
org.apache.james.mime4j.stream.MimeConfig: method ()V not found{code}
Could you list the jar on the classpath when you run james ?
> Cant recive emails
> --
>
> Key: JAMES-1640
> URL: https://issues.apache.org/jira/browse/JAMES-1640
> Project: James Server
> Issue Type: Bug
> Components: MailStore & MailRepository
>Affects Versions: 3.0.0-beta5
> Environment: Debian 8, Java 1.8.0_65
>Reporter: Lukas A
>
> When send a message from an other emailaccount like gmail. I'll get the
> following error:
> ERROR 22:46:13,893 | james.mailspooler | Exception processing mail while
> spooling Unable to process mail
> Mail1447537572407-c475eae9-9a54-484e-9567-1845df6ea235
> (org.apache.camel.CamelExecutionException: Exception occurred during
> execution on the exchange: Exchange[Message:
> org.apache.james.core.MailImpl@7c4938ba])
> javax.mail.MessagingException: Unable to process mail
> Mail1447537572407-c475eae9-9a54-484e-9567-1845df6ea235
> (org.apache.camel.CamelExecutionException: Exception occurred during
> execution on the exchange: Exchange[Message:
> org.apache.james.core.MailImpl@7c4938ba])
> at
> org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor.service(CamelMailetProcessor.java:65)
> at
> org.apache.james.mailetcontainer.lib.AbstractStateCompositeProcessor.service(AbstractStateCompositeProcessor.java:98)
> at
> org.apache.james.mailetcontainer.impl.JamesMailSpooler$1.run(JamesMailSpooler.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.camel.CamelExecutionException: Exception occurred
> during execution on the exchange: Exchange[Message:
> org.apache.james.core.MailImpl@7c4938ba]
> at
> org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1287)
> at
> org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:618)
> at
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:454)
> at
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:450)
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:126)
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:131)
> at
> org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor.service(CamelMailetProcessor.java:62)
> ... 5 more
> Caused by: javax.mail.MessagingException: Unable to process mail
> Mail1447537572407-c475eae9-9a54-484e-9567-1845df6ea235
> (org.apache.camel.CamelExecutionException: Exception occurred during
> execution on the exchange: Exchange[Message:
> org.apache.james.core.MailImpl@7c4938ba])
> at
> org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor.service(CamelMailetProcessor.java:65)
> at
> org.apache.james.mailetcontainer.lib.AbstractStateCompositeProcessor.service(AbstractStateCompositeProcessor.java:98)
> at
> org.apache.james.mailetcontainer.impl.JamesMailetContext.sendMail(JamesMailetContext.java:409)
> at
> org.apache.james.mailetcontainer.lib.AbstractStateMailetProcessor.toProcessor(AbstractStateMailetProcessor.java:160)
> at
> org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor.access$1000(CamelMailetProcessor.java:48)
> at
> org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor$MailetContainerRouteBuilder$StateChangedProcessor.process(CamelMailetProcessor.java:207)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
>
[jira] [Created] (PROTOCOLS-114) SMTP and POP3 tests randomly fail
Matthieu Baechler created PROTOCOLS-114: --- Summary: SMTP and POP3 tests randomly fail Key: PROTOCOLS-114 URL: https://issues.apache.org/jira/browse/PROTOCOLS-114 Project: James Protocols Issue Type: Bug Components: netty, pop3, smtp Reporter: Matthieu Baechler Assignee: Eric Charles There are several issues that make tests randomly fail : * sometimes, SMTP and/or POP tests lock * there's a randomly failing assertion in POP3 testsuite -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (PROTOCOLS-114) SMTP and POP3 tests randomly fail
[ https://issues.apache.org/jira/browse/PROTOCOLS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler closed PROTOCOLS-114. --- Resolution: Fixed > SMTP and POP3 tests randomly fail > - > > Key: PROTOCOLS-114 > URL: https://issues.apache.org/jira/browse/PROTOCOLS-114 > Project: James Protocols > Issue Type: Bug > Components: netty, pop3, smtp >Reporter: Matthieu Baechler >Assignee: Eric Charles > > There are several issues that make tests randomly fail : > * sometimes, SMTP and/or POP tests lock > * there's a randomly failing assertion in POP3 testsuite > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (PROTOCOLS-114) SMTP and POP3 tests randomly fail
[ https://issues.apache.org/jira/browse/PROTOCOLS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15008529#comment-15008529 ] Matthieu Baechler commented on PROTOCOLS-114: - merged > SMTP and POP3 tests randomly fail > - > > Key: PROTOCOLS-114 > URL: https://issues.apache.org/jira/browse/PROTOCOLS-114 > Project: James Protocols > Issue Type: Bug > Components: netty, pop3, smtp >Reporter: Matthieu Baechler >Assignee: Eric Charles > > There are several issues that make tests randomly fail : > * sometimes, SMTP and/or POP tests lock > * there's a randomly failing assertion in POP3 testsuite > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1641) MailQueue throws NullPointerException on start
Matthieu Baechler created JAMES-1641:
Summary: MailQueue throws NullPointerException on start
Key: JAMES-1641
URL: https://issues.apache.org/jira/browse/JAMES-1641
Project: James Server
Issue Type: Bug
Environment: using cassandra-guice launcher
Reporter: Matthieu Baechler
When launching cassandra-guice application, there are some exception like this
one :
{code}
Exception in thread "Remote delivery thread (0)" java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:459)
at
org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.java:741)
at java.lang.Thread.run(Thread.java:745)
{code}
The NPE comes from a call to domainList.getDefaultDomain()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1641) MailQueue throws NullPointerException on start
[
https://issues.apache.org/jira/browse/JAMES-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Baechler closed JAMES-1641.
Resolution: Fixed
merged
> MailQueue throws NullPointerException on start
> --
>
> Key: JAMES-1641
> URL: https://issues.apache.org/jira/browse/JAMES-1641
> Project: James Server
> Issue Type: Bug
> Environment: using cassandra-guice launcher
>Reporter: Matthieu Baechler
>
> When launching cassandra-guice application, there are some exception like
> this one :
> {code}
> Exception in thread "Remote delivery thread (0)"
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:459)
> at
> org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.java:741)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> The NPE comes from a call to domainList.getDefaultDomain()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (MAILBOX-259) Mailbox Listeners should be asynchronously called.
[ https://issues.apache.org/jira/browse/MAILBOX-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985214#comment-14985214 ] Matthieu Baechler commented on MAILBOX-259: --- As long as I can use the synchronous version, I'll be happy. The mixed approach looks fine too ! > Mailbox Listeners should be asynchronously called. > -- > > Key: MAILBOX-259 > URL: https://issues.apache.org/jira/browse/MAILBOX-259 > Project: James Mailbox > Issue Type: Improvement >Reporter: Tellier Benoit > > Event handling by Mailbox Listeners might take time. > For instance indexation, etc... > This time impact latencies. > What I propose is to have a ThreadPool executor dedicated to event handling, > and schedule tasks on it, then return before task completion. > I gonna implement it on top of MAILBOX-211 :-) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1599) HBase rewrite table implementation is not compatible
[
https://issues.apache.org/jira/browse/JAMES-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985240#comment-14985240
]
Matthieu Baechler commented on JAMES-1599:
--
could you close this ticket ?
> HBase rewrite table implementation is not compatible
>
>
> Key: JAMES-1599
> URL: https://issues.apache.org/jira/browse/JAMES-1599
> Project: James Server
> Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Antoine Duprat
> Labels: hbase, rewrite-table
> Fix For: Trunk
>
>
> HBase rewrite table implementation is not compatible, as _getAllMappings_
> does not return correct values.
> For example, when having the following mapping:
> - regex mapping for user "_user_" at domain "_localhost_": "_(.*)@localhost_"
> _getAllMappings_ method returns:
> {code}
> {test@localhost=[test@localhost]}
> {code}
> as *JPA* & *JDBC* implementations returns:
> {code}
> {test@localhost=[regex:(.*)@localhost]}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1594) Add rewrite table spec as cucumber tests
[ https://issues.apache.org/jira/browse/JAMES-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985233#comment-14985233 ] Matthieu Baechler commented on JAMES-1594: -- could you close this ticket ? It's now merged > Add rewrite table spec as cucumber tests > > > Key: JAMES-1594 > URL: https://issues.apache.org/jira/browse/JAMES-1594 > Project: James Server > Issue Type: Bug >Affects Versions: Trunk >Reporter: Antoine Duprat > Labels: rewrite-table > Fix For: Trunk > > > We would like to write specification on rewrite table, in order to have the > same behaviour on each backends. > A good way to achieve that is to write some tests, and so in the > [Gherkin|https://github.com/cucumber/cucumber/wiki/Gherkin] language. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1586) Write a compliant Cassandra User Repository
[ https://issues.apache.org/jira/browse/JAMES-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler closed JAMES-1586. Resolution: Fixed just merged > Write a compliant Cassandra User Repository > --- > > Key: JAMES-1586 > URL: https://issues.apache.org/jira/browse/JAMES-1586 > Project: James Server > Issue Type: New Feature >Reporter: Matthieu Baechler > > To complete the Cassandra backend, we should write a User Repository on top > of Cassandra. > There's already some code there : > https://github.com/mbaechler/james/commits/cassandra but it can't be > integrated as is, it needs some refactoring to use mailbox Cassandra > infrastructure. > Once done, we should update the spring configuration to deploy this > repository and make sure integration tests on a deployed james still works. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1586) Write a compliant Cassandra User Repository
[ https://issues.apache.org/jira/browse/JAMES-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985310#comment-14985310 ] Matthieu Baechler commented on JAMES-1586: -- We'll benchmark the whole james + cassandra server starting next year. I just merged this ticket, so I close this ticket. Feel free to open a issue about having performance testing. > Write a compliant Cassandra User Repository > --- > > Key: JAMES-1586 > URL: https://issues.apache.org/jira/browse/JAMES-1586 > Project: James Server > Issue Type: New Feature >Reporter: Matthieu Baechler > > To complete the Cassandra backend, we should write a User Repository on top > of Cassandra. > There's already some code there : > https://github.com/mbaechler/james/commits/cassandra but it can't be > integrated as is, it needs some refactoring to use mailbox Cassandra > infrastructure. > Once done, we should update the spring configuration to deploy this > repository and make sure integration tests on a deployed james still works. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1597) Wildcard mapping is not overriden by user address mapping
[ https://issues.apache.org/jira/browse/JAMES-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985236#comment-14985236 ] Matthieu Baechler commented on JAMES-1597: -- could you close this ticket ? > Wildcard mapping is not overriden by user address mapping > - > > Key: JAMES-1597 > URL: https://issues.apache.org/jira/browse/JAMES-1597 > Project: James Server > Issue Type: Bug >Affects Versions: Trunk >Reporter: Antoine Duprat > Labels: rewrite-table > Fix For: Trunk > > > Wildcard mapping is not overriden by user address mapping > For example, when having the two following mappings: > - address mapping for user "_test_" at domain "_localhost_": > "_mine@localhost_" > - wildcard mapping for domain "_localhost_": "_test@localhost_" > Getting the mappings for user "_test_" return "_test@localhost_" instead of > "_mine@localhost_". -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1595) Exception message is not well formatted when thrown by error mapping
[ https://issues.apache.org/jira/browse/JAMES-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985234#comment-14985234 ] Matthieu Baechler commented on JAMES-1595: -- could you close this ticket too ? > Exception message is not well formatted when thrown by error mapping > > > Key: JAMES-1595 > URL: https://issues.apache.org/jira/browse/JAMES-1595 > Project: James Server > Issue Type: Bug >Affects Versions: Trunk >Reporter: Antoine Duprat > Labels: rewrite-table > Fix For: Trunk > > > Exception message is not well formatted when thrown by error mapping. > For example, when having the two following mappings: > - error mapping for user "_test_" at domain "_localhost_": "_bounce!_" > - error mapping for user "_test_" at domain "_localhost_": "_error_" > throws a *ErrorMappingException* with messaage: "_bounce!;error:error_" > Other example, with mappings: > - error mapping for user "_test_" at domain "_localhost_": "_bounce!_" > - address mapping for user "_test_" at domain "_localhost_": > "_test@localhost_" > throws a *ErrorMappingException* with messaage: "_bounce!;test@localhost_" -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1596) Exception is not thrown when error mapping is not the first stored
[ https://issues.apache.org/jira/browse/JAMES-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985235#comment-14985235 ] Matthieu Baechler commented on JAMES-1596: -- could you close this ticket ? > Exception is not thrown when error mapping is not the first stored > -- > > Key: JAMES-1596 > URL: https://issues.apache.org/jira/browse/JAMES-1596 > Project: James Server > Issue Type: Bug >Affects Versions: Trunk >Reporter: Antoine Duprat > Labels: rewrite-table > Fix For: Trunk > > > Exception is not thrown when error mapping is not the first stored. > For example, when having the two following mappings: > - address mapping for user "_test_" at domain "_localhost_": > "_test@localhost_" > - error mapping for user "_test_" at domain "_localhost_": "_bounce!_" > Does not throw exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1630) CDI deplyoment exeption for james WAR
[ https://issues.apache.org/jira/browse/JAMES-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982648#comment-14982648 ] Matthieu Baechler commented on JAMES-1630: -- I didn't knew James supports CDI (or maybe it does by accident ?). We have to prevent CDI from resolving @Inject and let spring do the wiring. Maybe you can try with this solution from stackoverflow : http://stackoverflow.com/questions/30863889/disable-scanning-of-cdi-beans-in-war/30865190#30865190 > CDI deplyoment exeption for james WAR > - > > Key: JAMES-1630 > URL: https://issues.apache.org/jira/browse/JAMES-1630 > Project: James Server > Issue Type: Bug > Components: James Core, MailStore & MailRepository >Affects Versions: Trunk > Environment: JDK 1.8.65, Glassfish 4.1, Apache JAMES WAR from trunk >Reporter: Mario > Attachments: mailbox.xml, quota.xml > > > This is the stake trace note you have to build the project with -P > with-assembly to get the WAR file. > [2015-10-28T16:55:57.559+] [glassfish 4.1] [INFO] [] > [org.glassfish.admingui] [tid: _ThreadID=51 _ThreadName=admin-listener(2)] > [timeMillis: 1446051357559] [levelValue: 800] [[ > uploadFileName=james-server-app-3.0.0-beta5-SNAPSHOT.war]] > [2015-10-28T16:56:03.004+] [glassfish 4.1] [SEVERE] [NCLS-CORE-00026] > [javax.enterprise.system.core] [tid: _ThreadID=53 > _ThreadName=admin-listener(4)] [timeMillis: 1446051363004] [levelValue: 1000] > [[ > Exception during lifecycle processing > org.glassfish.deployment.common.DeploymentException: CDI deployment > failure:Exception List with 4 exceptions: > Exception 0 : > org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied > dependencies for type MailboxSessionMapperFactory with qualifiers @Default > at injection point [BackedAnnotatedParameter] Parameter 1 of > [BackedAnnotatedConstructor] @Inject public > org.apache.james.mailbox.store.quota.DefaultQuotaRootResolver(MailboxSessionMapperFactory) > at > org.apache.james.mailbox.store.quota.DefaultQuotaRootResolver.(DefaultQuotaRootResolver.java:0) > at > org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:370) > at > org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:291) > at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134) > at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:165) > at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:529) > at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:515) > at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:490) > at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:419) > at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:90) > at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:225) > at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131) > at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:328) > at > com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:496) > at > com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:219) > at > org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:491) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:539) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:535) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:360) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:534) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:565) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:557) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:360) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:556) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1464) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1300(CommandRunnerImpl.java:109) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1846) > at > com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1722) > at > org.glassfish.admin.rest.utils.ResourceUtil.runCommand(ResourceUtil.java:253) > at > org.glassfish.admin.rest.utils.ResourceUtil.runCommand(ResourceUtil.java:231) > at > org.glassfish.admin.rest.utils.ResourceUtil.runCommand(ResourceUtil.java:275) > at >
[jira] [Closed] (JAMES-1626) build a guice application for james with cassandra + elasticsearch
[ https://issues.apache.org/jira/browse/JAMES-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler closed JAMES-1626. Resolution: Fixed merged > build a guice application for james with cassandra + elasticsearch > -- > > Key: JAMES-1626 > URL: https://issues.apache.org/jira/browse/JAMES-1626 > Project: James Server > Issue Type: New Feature >Reporter: Matthieu Baechler > > I'd like to run a specific combination of backends using a Guice application. > This application would use cassandra backends when available (file backends > for others) and elasticsearch for search. > The produced artifact is supposed to be a simple runnable jar and it's > dependencies in a subdirectory. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1636) test failure on org.apache.james.user.cassandra.CassandraUsersRepositoryTest
Matthieu Baechler created JAMES-1636:
Summary: test failure on
org.apache.james.user.cassandra.CassandraUsersRepositoryTest
Key: JAMES-1636
URL: https://issues.apache.org/jira/browse/JAMES-1636
Project: James Server
Issue Type: Bug
Components: UsersStore & UsersRepository
Reporter: Matthieu Baechler
There's an issue on trunk with CassandraUsersRepositoryTest tests.
{code}
testUserAddRemoveCycle(org.apache.james.user.cassandra.CassandraUsersRepositoryTest)
Time elapsed: 3.597 sec <<< ERROR!
org.apache.james.user.api.UsersRepositoryException: Given Username needs to
contain a @domainpart
{code}
The testsuite doesn't check if virtualdomain is true or false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1636) test failure on org.apache.james.user.cassandra.CassandraUsersRepositoryTest
[
https://issues.apache.org/jira/browse/JAMES-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14989516#comment-14989516
]
Matthieu Baechler commented on JAMES-1636:
--
I'll fix that
> test failure on org.apache.james.user.cassandra.CassandraUsersRepositoryTest
>
>
> Key: JAMES-1636
> URL: https://issues.apache.org/jira/browse/JAMES-1636
> Project: James Server
> Issue Type: Bug
> Components: UsersStore & UsersRepository
>Reporter: Matthieu Baechler
>
> There's an issue on trunk with CassandraUsersRepositoryTest tests.
> {code}
> testUserAddRemoveCycle(org.apache.james.user.cassandra.CassandraUsersRepositoryTest)
> Time elapsed: 3.597 sec <<< ERROR!
> org.apache.james.user.api.UsersRepositoryException: Given Username needs to
> contain a @domainpart
> {code}
> The testsuite doesn't check if virtualdomain is true or false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1636) test failure on org.apache.james.user.cassandra.CassandraUsersRepositoryTest
[
https://issues.apache.org/jira/browse/JAMES-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Baechler closed JAMES-1636.
Resolution: Fixed
merged
> test failure on org.apache.james.user.cassandra.CassandraUsersRepositoryTest
>
>
> Key: JAMES-1636
> URL: https://issues.apache.org/jira/browse/JAMES-1636
> Project: James Server
> Issue Type: Bug
> Components: UsersStore & UsersRepository
>Reporter: Matthieu Baechler
>
> There's an issue on trunk with CassandraUsersRepositoryTest tests.
> {code}
> testUserAddRemoveCycle(org.apache.james.user.cassandra.CassandraUsersRepositoryTest)
> Time elapsed: 3.597 sec <<< ERROR!
> org.apache.james.user.api.UsersRepositoryException: Given Username needs to
> contain a @domainpart
> {code}
> The testsuite doesn't check if virtualdomain is true or false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1634) Slow Cassandra tests
[ https://issues.apache.org/jira/browse/JAMES-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14989133#comment-14989133 ] Matthieu Baechler commented on JAMES-1634: -- Hi Benoit, That would be great ... but it actually doesn't give us the expected speedup (almost same execution times) I just tried to have some figures about "how much" before talking about "how to". It's definitively not worth it. [~aduprat] you should make this ticket more specific and close it. > Slow Cassandra tests > > > Key: JAMES-1634 > URL: https://issues.apache.org/jira/browse/JAMES-1634 > Project: James Server > Issue Type: Bug >Reporter: Antoine Duprat > > Cassandra tests are slow, tables creation takes approximatively 25 seconds. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1477) Replace @Resource with @Inject where it can
[ https://issues.apache.org/jira/browse/JAMES-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14989092#comment-14989092 ] Matthieu Baechler commented on JAMES-1477: -- Ok, it's now commited, I think you can close this ticket. > Replace @Resource with @Inject where it can > --- > > Key: JAMES-1477 > URL: https://issues.apache.org/jira/browse/JAMES-1477 > Project: James Server > Issue Type: Sub-task >Reporter: Eric Charles >Assignee: Eric Charles > > This will allow also allow to work with different dependency injection > frameworks (spring, guice...). > See also JAMES-1237. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (MAILBOX-259) Mailbox Listeners should be asynchronously called.
[ https://issues.apache.org/jira/browse/MAILBOX-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984889#comment-14984889 ] Matthieu Baechler commented on MAILBOX-259: --- It's for sure a very dangerous thing to do as you have no idea what the consistency issues you are going to face. It's not a technical subject by rather a domain related one. > Mailbox Listeners should be asynchronously called. > -- > > Key: MAILBOX-259 > URL: https://issues.apache.org/jira/browse/MAILBOX-259 > Project: James Mailbox > Issue Type: Improvement >Reporter: Tellier Benoit > > Event handling by Mailbox Listeners might take time. > For instance indexation, etc... > This time impact latencies. > What I propose is to have a ThreadPool executor dedicated to event handling, > and schedule tasks on it, then return before task completion. > I gonna implement it on top of MAILBOX-211 :-) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1635) Can not run unit tests
[ https://issues.apache.org/jira/browse/JAMES-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14993335#comment-14993335 ] Matthieu Baechler commented on JAMES-1635: -- You didn't even give us the name of the failing test, it won't help much. We should never create tickets "unit tests are broken" because by definition, it's too broad : everytime something is broken, a unit test will be, and you could reopen this ticket. Please open on ticket by broken thing. > Can not run unit tests > -- > > Key: JAMES-1635 > URL: https://issues.apache.org/jira/browse/JAMES-1635 > Project: James Server > Issue Type: Bug >Affects Versions: Trunk >Reporter: Tellier Benoit > Fix For: Trunk > > > I got this exception, either in cassandra mailbox and Cassandra backend ; > For example : > initializeTypesShouldCreateTheTypes(org.apache.james.backends.cassandra.init.CassandraTypeProviderTest) > Time elapsed: 14.353 sec <<< FAILURE! > java.lang.AssertionError: Cassandra daemon did not start within timeout > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:130) > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:85) > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:64) > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:56) > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:52) > at > org.apache.james.backends.cassandra.CassandraCluster.(CassandraCluster.java:57) > at > org.apache.james.backends.cassandra.CassandraCluster.create(CassandraCluster.java:51) > at > org.apache.james.backends.cassandra.init.CassandraTypeProviderTest.setUp(CassandraTypeProviderTest.java:66) > I increased the max retry count of the Cassandra cluster but it does not > solve my problem. > It really slow down my worlflow... -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1635) Can not run unit tests
[ https://issues.apache.org/jira/browse/JAMES-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14993343#comment-14993343 ] Matthieu Baechler commented on JAMES-1635: -- > I spent ly last 3 days to try to run unit tests. Contributing to James is > really hard due to : > > Unit test stability > Time spent testing : more than one hour for me before getting this > error... I'm sorry to hear that, we experience the same thing here, it's probably that James code base needs more work to become more stable. unit test stability issues is often the symptom of product issues. I suggest you help us to tackle these issues. > Can not run unit tests > -- > > Key: JAMES-1635 > URL: https://issues.apache.org/jira/browse/JAMES-1635 > Project: James Server > Issue Type: Bug >Affects Versions: Trunk >Reporter: Tellier Benoit > Fix For: Trunk > > > I got this exception, either in cassandra mailbox and Cassandra backend ; > For example : > initializeTypesShouldCreateTheTypes(org.apache.james.backends.cassandra.init.CassandraTypeProviderTest) > Time elapsed: 14.353 sec <<< FAILURE! > java.lang.AssertionError: Cassandra daemon did not start within timeout > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:130) > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:85) > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:64) > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:56) > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:52) > at > org.apache.james.backends.cassandra.CassandraCluster.(CassandraCluster.java:57) > at > org.apache.james.backends.cassandra.CassandraCluster.create(CassandraCluster.java:51) > at > org.apache.james.backends.cassandra.init.CassandraTypeProviderTest.setUp(CassandraTypeProviderTest.java:66) > I increased the max retry count of the Cassandra cluster but it does not > solve my problem. > It really slow down my worlflow... -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (MPT-33) Support optional features when running mpt tests
[ https://issues.apache.org/jira/browse/MPT-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler closed MPT-33. Resolution: Fixed merged > Support optional features when running mpt tests > > > Key: MPT-33 > URL: https://issues.apache.org/jira/browse/MPT-33 > Project: James MPT > Issue Type: Improvement > Components: Main >Reporter: Matthieu Baechler > > MAILBOX-241 basically says : "I wrote some tests but it breaks on maildir > because maildir doesn't have namespace support". > I think this kind of feature set mismatch between backends is going to happen > as we move on with generic tests. > I propose to introduce feature conditioned tests in mpt to workaround this > kind of problems. > Come is coming soon. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (MPT-32) external-james should only run when JAMES_ADDRESS is defined
[ https://issues.apache.org/jira/browse/MPT-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler closed MPT-32. Resolution: Fixed merged > external-james should only run when JAMES_ADDRESS is defined > > > Key: MPT-32 > URL: https://issues.apache.org/jira/browse/MPT-32 > Project: James MPT > Issue Type: Bug > Components: Main >Reporter: Matthieu Baechler > > External-james should run against a freshly compile James to check basic > behaviour. It should not run unless JAMES_ADDRESS environnement entry is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (MPT-31) cyrus mpt tests are unreliable
[ https://issues.apache.org/jira/browse/MPT-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler closed MPT-31. Resolution: Fixed merged > cyrus mpt tests are unreliable > -- > > Key: MPT-31 > URL: https://issues.apache.org/jira/browse/MPT-31 > Project: James MPT > Issue Type: Bug > Components: Main >Reporter: Matthieu Baechler > > Cyrus tests are very time-sensitive : they run well with some timing between > container creation and container usage. > There's a loop to wait for service start but it seems broken. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1609) JMX unregister of queues : some queues are ignored.
[
https://issues.apache.org/jira/browse/JAMES-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14963433#comment-14963433
]
Matthieu Baechler commented on JAMES-1609:
--
[~BTellier] please close this JIRA, it's merged.
> JMX unregister of queues : some queues are ignored.
> ---
>
> Key: JAMES-1609
> URL: https://issues.apache.org/jira/browse/JAMES-1609
> Project: James Server
> Issue Type: Bug
> Components: Queue
>Affects Versions: Trunk
>Reporter: Tellier Benoit
> Fix For: Trunk
>
>
> The @PreDestoy method called look like this :
> ```
> for ( String mbean : mbeans) {
> unregister(mbean);
> mbeans.remove(mbean);
> }
> ```
> Causing mbeans being ignored and not unregistered.
> Solution is to simply not modify collection content while working on it and
> simply clear it outside the for loop.
> Acceptance criteria :
> - Being able to launch a James server, stop it and restart it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1603) cli should not depend on james-server-spring
[ https://issues.apache.org/jira/browse/JAMES-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler closed JAMES-1603. > cli should not depend on james-server-spring > > > Key: JAMES-1603 > URL: https://issues.apache.org/jira/browse/JAMES-1603 > Project: James Server > Issue Type: Bug > Components: CLI >Reporter: Matthieu Baechler > > cli depends on james-server-spring to access MailboxCopierManagementMBean > interface. > It's probably a simple mistake to fix, MBeans are usually into data-api > module, we should have to move MailboxCopierManagementMBean to data-api too. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MPT-32) external-james should only run when JAMES_ADDRESS is defined
Matthieu Baechler created MPT-32: Summary: external-james should only run when JAMES_ADDRESS is defined Key: MPT-32 URL: https://issues.apache.org/jira/browse/MPT-32 Project: James MPT Issue Type: Bug Components: Main Reporter: Matthieu Baechler External-james should run against a freshly compile James to check basic behaviour. It should not run unless JAMES_ADDRESS environnement entry is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (MPT-30) cyrus tests could use Java 8
[ https://issues.apache.org/jira/browse/MPT-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler closed MPT-30. Resolution: Fixed > cyrus tests could use Java 8 > > > Key: MPT-30 > URL: https://issues.apache.org/jira/browse/MPT-30 > Project: James MPT > Issue Type: Task > Components: Main >Reporter: Matthieu Baechler > > Cyrus tests are not part of James product and could be written using java 8. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (MPT-30) cyrus tests could use Java 8
[ https://issues.apache.org/jira/browse/MPT-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14958733#comment-14958733 ] Matthieu Baechler commented on MPT-30: -- merged > cyrus tests could use Java 8 > > > Key: MPT-30 > URL: https://issues.apache.org/jira/browse/MPT-30 > Project: James MPT > Issue Type: Task > Components: Main >Reporter: Matthieu Baechler > > Cyrus tests are not part of James product and could be written using java 8. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1625) app java 6 build fail on missing apache-james-mailbox-elasticsearch
[ https://issues.apache.org/jira/browse/JAMES-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler closed JAMES-1625. Resolution: Fixed merged > app java 6 build fail on missing apache-james-mailbox-elasticsearch > --- > > Key: JAMES-1625 > URL: https://issues.apache.org/jira/browse/JAMES-1625 > Project: James Server > Issue Type: Bug > Components: Build System >Reporter: Matthieu Baechler > > The build fail because apache-james-mailbox-elasticsearch artifact is not > built on java 6. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MPT-33) Support optional features when running mpt tests
Matthieu Baechler created MPT-33: Summary: Support optional features when running mpt tests Key: MPT-33 URL: https://issues.apache.org/jira/browse/MPT-33 Project: James MPT Issue Type: Improvement Components: Main Reporter: Matthieu Baechler MAILBOX-241 basically says : "I wrote some tests but it breaks on maildir because maildir doesn't have namespace support". I think this kind of feature set mismatch between backends is going to happen as we move on with generic tests. I propose to introduce feature conditioned tests in mpt to workaround this kind of problems. Come is coming soon. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1605) AbstractRecipientRewriteTable.mapAddress doesn't respect domainAlias ordering
[
https://issues.apache.org/jira/browse/JAMES-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Baechler closed JAMES-1605.
Resolution: Fixed
already merged
> AbstractRecipientRewriteTable.mapAddress doesn't respect domainAlias ordering
> -
>
> Key: JAMES-1605
> URL: https://issues.apache.org/jira/browse/JAMES-1605
> Project: James Server
> Issue Type: Bug
>Reporter: Matthieu Baechler
>
> This code snippet seems to tries to putting aliasdomain entries in front of
> the list while keeping entries original order.
>
> {code}
> while (mapIt.hasNext()) {
> int i = 0;
> String mapping = mapIt.next();
> if
> (mapping.startsWith(RecipientRewriteTable.ALIASDOMAIN_PREFIX)) {
> col.add(i, mapping);
> i++;
> } else {
> col.add(mapping);
> }
> }
> {code}
> I looks like no test covers this feature because it actually mess with
> aliasdomain ordering (the 'i' counter is reset for every loop)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1606) FileSystem implementation without Spring dependency
[ https://issues.apache.org/jira/browse/JAMES-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14965283#comment-14965283 ] Matthieu Baechler commented on JAMES-1606: -- could you close this ticket, i just merged it. > FileSystem implementation without Spring dependency > --- > > Key: JAMES-1606 > URL: https://issues.apache.org/jira/browse/JAMES-1606 > Project: James Server > Issue Type: Task > Components: James Core >Reporter: Raphaël Ouazana > > Using Guice for modules aggregation, we need an implementation of FileSystem > API without Spring. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (MAILBOX-256) Unit test failure on elasticsearch
[
https://issues.apache.org/jira/browse/MAILBOX-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14966686#comment-14966686
]
Matthieu Baechler commented on MAILBOX-256:
---
I ran test right after JAMES-1606 with java 7 and java 8 and everything was ok.
How do you run your tests ?
> Unit test failure on elasticsearch
> --
>
> Key: MAILBOX-256
> URL: https://issues.apache.org/jira/browse/MAILBOX-256
> Project: James Mailbox
> Issue Type: Bug
>Reporter: Tellier Benoit
>
> On trunk today, I realized test do not pass.
> Is that only me ?
> Here is the suffire report :
> ---
> Test set:
> org.apache.james.mailbox.elasticsearch.json.MessageToElasticSearchJsonTest
> ---
> Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.839 sec
> <<< FAILURE!
> spamEmailShouldBeWellConvertedToJsonWithApacheTika(org.apache.james.mailbox.elasticsearch.json.MessageToElasticSearchJsonTest)
> Time elapsed: 0.367 sec <<< FAILURE!
> java.lang.AssertionError: JSON documents are different:
> Array "attachments" has different content. Missing values
> [{"mediaType":"application","subtype":"vnd.oasis.opendocument.text","fileName":"toto.odt","fileExtension":"odt","contentDisposition":"attachment","fileMetadata":{"date":["2015-06-18T12:43:07.489893918"],"meta:paragraph-count":["1"],"meta:word-count":["7"],"Table-Count":["0"],"generator":["LibreOffice/4.4.3.2$Linux_X86_64
>
> LibreOffice_project/40m0$Build-2"],"Word-Count":["7"],"dcterms:created":["2015-06-18T12:41:25.197399866"],"dcterms:modified":["2015-06-18T12:43:07.489893918"],"Last-Modified":["2015-06-18T12:43:07.489893918"],"nbPara":["1"],"Last-Save-Date":["2015-06-18T12:43:07.489893918"],"meta:object-count":["0"],"meta:character-count":["47"],"Paragraph-Count":["1"],"nbImg":["0"],"meta:save-date":["2015-06-18T12:43:07.489893918"],"modified":["2015-06-18T12:43:07.489893918"],"Edit-Time":["PT1M42S"],"meta:image-count":["0"],"Image-Count":["0"],"nbCharacter":["47"],"nbObject":["0"],"nbPage":["1"],"Object-Count":["0"],"nbWord":["7"],"Content-Type":["application/vnd.oasis.opendocument.text"],"X-Parsed-By":["org.apache.tika.parser.DefaultParser","org.apache.tika.parser.odf.OpenDocumentParser"],"meta:creation-date":["2015-06-18T12:41:25.197399866"],"meta:table-count":["0"],"Creation-Date":["2015-06-18T12:41:25.197399866"],"xmpTPg:NPages":["1"],"resourceName":["toto.odt"],"Character
>
> Count":["47"],"editing-cycles":["2"],"Page-Count":["1"],"nbTab":["0"],"meta:page-count":["1"]},"headers":{"content-transfer-encoding":["base64"],"content-disposition":["attachment;
>
> filename=\"toto.odt\""],"content-type":["application/vnd.oasis.opendocument.text;
> name=\"toto.odt\""]},"textContent":"Awesome document provided for text
> extraction??!\n"}], extra values
> [{"mediaType":"application","subtype":"vnd.oasis.opendocument.text","fileName":"toto.odt","fileExtension":"odt","contentDisposition":"attachment","fileMetadata":{"date":["2015-06-18T12:43:07.489893918"],"meta:paragraph-count":["1"],"meta:word-count":["7"],"Table-Count":["0"],"generator":["LibreOffice/4.4.3.2$Linux_X86_64
>
> LibreOffice_project/40m0$Build-2"],"Word-Count":["7"],"dcterms:created":["2015-06-18T12:41:25.197399866"],"dcterms:modified":["2015-06-18T12:43:07.489893918"],"Last-Modified":["2015-06-18T12:43:07.489893918"],"nbPara":["1"],"Last-Save-Date":["2015-06-18T12:43:07.489893918"],"meta:object-count":["0"],"meta:character-count":["47"],"Paragraph-Count":["1"],"nbImg":["0"],"meta:save-date":["2015-06-18T12:43:07.489893918"],"modified":["2015-06-18T12:43:07.489893918"],"Edit-Time":["PT1M42S"],"meta:image-count":["0"],"Image-Count":["0"],"nbCharacter":["47"],"nbObject":["0"],"nbPage":["1"],"Object-Count":["0"],"nbWord":["7"],"Content-Type":["application/vnd.oasis.opendocument.text"],"X-Parsed-By":["org.apache.tika.parser.DefaultParser","org.apache.tika.parser.odf.OpenDocumentParser"],"meta:creation-date":["2015-06-18T12:41:25.197399866"],"meta:table-count":["0"],"Creation-Date":["2015-06-18T12:41:25.197399866"],"xmpTPg:NPages":["1"],"resourceName":["toto.odt"],"Character
>
> Count":["47"],"editing-cycles":["2"],"Page-Count":["1"],"nbTab":["0"],"meta:page-count":["1"]},"headers":{"content-transfer-encoding":["base64"],"content-disposition":["attachment;
>
> filename=\"toto.odt\""],"content-type":["application/vnd.oasis.opendocument.text;
> name=\"toto.odt\""]},"textContent":"Awesome document provided for text
> extraction?!\n"}]
> at
> net.javacrumbs.jsonunit.fluent.JsonFluentAssert.failWithMessage(JsonFluentAssert.java:183)
> at
> net.javacrumbs.jsonunit.fluent.JsonFluentAssert.isEqualTo(JsonFluentAssert.java:112)
> at
>
[jira] [Created] (MPT-30) cyrus tests could use Java 8
Matthieu Baechler created MPT-30: Summary: cyrus tests could use Java 8 Key: MPT-30 URL: https://issues.apache.org/jira/browse/MPT-30 Project: James MPT Issue Type: Task Components: Main Reporter: Matthieu Baechler Cyrus tests are not part of James product and could be written using java 8. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MPT-31) cyrus mpt tests are unreliable
Matthieu Baechler created MPT-31: Summary: cyrus mpt tests are unreliable Key: MPT-31 URL: https://issues.apache.org/jira/browse/MPT-31 Project: James MPT Issue Type: Bug Components: Main Reporter: Matthieu Baechler Cyrus tests are very time-sensitive : they run well with some timing between container creation and container usage. There's a loop to wait for service start but it seems broken. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1626) build a guice application for james with cassandra + elasticsearch
Matthieu Baechler created JAMES-1626: Summary: build a guice application for james with cassandra + elasticsearch Key: JAMES-1626 URL: https://issues.apache.org/jira/browse/JAMES-1626 Project: James Server Issue Type: New Feature Reporter: Matthieu Baechler I'd like to run a specific combination of backends using a Guice application. This application would use cassandra backends when available (file backends for others) and elasticsearch for search. The produced artifact is supposed to be a simple runnable jar and it's dependencies in a subdirectory. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (MPT-9) JPA tests are broken
[ https://issues.apache.org/jira/browse/MPT-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14966379#comment-14966379 ] Matthieu Baechler commented on MPT-9: - Could you check this on current trunk ? it works for me > JPA tests are broken > > > Key: MPT-9 > URL: https://issues.apache.org/jira/browse/MPT-9 > Project: James MPT > Issue Type: Bug >Reporter: Tellier Benoit > > The Host System fails to create the entity manager. > Here is the stack trace I get : > com.google.inject.CreationException: Guice creation errors: > 1) Error in custom provider, error> org.apache.openjpa.persistence.ArgumentException: This configuration > disallows runtime optimization, but the following listed types were not > enhanced at build time or at class load time with a javaagent: " > org.apache.james.mailbox.jpa.mail.model.JPAMailbox > org.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage > org.apache.james.mailbox.jpa.mail.model.JPAUserFlag > org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage > org.apache.james.mailbox.jpa.mail.model.JPAProperty > org.apache.james.mailbox.jpa.user.model.JPASubscription". > at > org.apache.james.mpt.imapmailbox.jpa.JpaMailboxTestModule.provideHostSystem(JpaMailboxTestModule.java:37) > at > org.apache.james.mpt.imapmailbox.jpa.JpaMailboxTestModule.provideHostSystem(JpaMailboxTestModule.java:37) > while locating org.apache.james.mpt.api.HostSystem > for field at > org.apache.james.mpt.imapmailbox.suite.AuthenticatedState.system(AuthenticatedState.java:37) > 1 error > at > com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435) > at > com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:175) > at > com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109) > at com.google.inject.Guice.createInjector(Guice.java:95) > at com.google.inject.Guice.createInjector(Guice.java:72) > at > org.apache.onami.test.OnamiRunner.createInjector(OnamiRunner.java:281) > at org.apache.onami.test.OnamiRunner.run(OnamiRunner.java:220) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.apache.onami.test.OnamiSuite.runChild(OnamiSuite.java:244) > at org.apache.onami.test.OnamiSuite.runChild(OnamiSuite.java:126) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.onami.test.OnamiSuite.run(OnamiSuite.java:207) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:78) > at > com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:212) > at > com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:68) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140) > Caused by: > org.apache.openjpa.persistence.ArgumentException: This configuration > disallows runtime optimization, but the following listed types were not > enhanced at build time or at class load time with a javaagent: " > org.apache.james.mailbox.jpa.mail.model.JPAMailbox > org.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage > org.apache.james.mailbox.jpa.mail.model.JPAUserFlag > org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage > org.apache.james.mailbox.jpa.mail.model.JPAProperty > org.apache.james.mailbox.jpa.user.model.JPASubscription". > at > org.apache.openjpa.enhance.ManagedClassSubclasser.prepareUnenhancedClasses(ManagedClassSubclasser.java:115) > at > org.apache.openjpa.kernel.AbstractBrokerFactory.loadPersistentTypes(AbstractBrokerFactory.java:314) > at > org.apache.openjpa.kernel.AbstractBrokerFactory.initializeBroker(AbstractBrokerFactory.java:238) > at > org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:212) > at > org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:156) > at > org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:227) > at >
[jira] [Created] (MAILBOX-255) AbstractSubscriptionManagerTest.user1ShouldBeAbleToSubscribeTwoMailbox should not enforce subscription ordering
Matthieu Baechler created MAILBOX-255:
-
Summary:
AbstractSubscriptionManagerTest.user1ShouldBeAbleToSubscribeTwoMailbox should
not enforce subscription ordering
Key: MAILBOX-255
URL: https://issues.apache.org/jira/browse/MAILBOX-255
Project: James Mailbox
Issue Type: Bug
Components: api
Reporter: Matthieu Baechler
today's trunk tests are broken :
{code}
Failed tests:
JCRSubscriptionManagerTest>AbstractSubscriptionManagerTest.user1ShouldBeAbleToSubscribeTwoMailbox:84
Actual and expected have the same elements but not in the same order, at index
0 actual element was:
<"test2">
whereas expected element was:
<"test1">
{code}
Actually, the test enforce mailboxes ordering that should not be needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1508) build failure on james trunk At revision 1487220
[ https://issues.apache.org/jira/browse/JAMES-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14954894#comment-14954894 ] Matthieu Baechler commented on JAMES-1508: -- I don't have rights to reopen this ticket but IMO it's still a bug : "mvn package" should not fail. I'll open a clone to track progress on this problem. > build failure on james trunk At revision 1487220 > > > Key: JAMES-1508 > URL: https://issues.apache.org/jira/browse/JAMES-1508 > Project: James Server > Issue Type: Bug > Components: Build System >Affects Versions: Trunk, 3.0.0-beta5 > Environment: ➜ james-trunk uname -a > Darwin wdx-me 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT > 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64 > ➜ james-trunk java -version > java version "1.7.0_17" > Java(TM) SE Runtime Environment (build 1.7.0_17-b02) > Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode) > ➜ james-trunk mvn -v > Apache Maven 3.0.3 (r1075438; 2011-03-01 01:31:09+0800) > Maven home: /usr/share/maven > Java version: 1.7.0_17, vendor: Oracle Corporation > Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac" > ➜ james-trunk svn info > Path: . > Working Copy Root Path: /Users/wdx/art/open/james/james-trunk > URL: http://svn.apache.org/repos/asf/james/server/trunk > Repository Root: http://svn.apache.org/repos/asf > Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 > Revision: 1487220 > Node Kind: directory > Schedule: normal > Last Changed Author: eric > Last Changed Rev: 1476802 > Last Changed Date: 2013-04-29 01:23:37 +0800 (一, 29 4 2013) >Reporter: dongxu > Fix For: Trunk, 3.0.0-beta5 > > > $ mvn clean package -X -DskipTests=true > .. > .. > [INFO] Apache James :: Server SUCCESS [2.266s] > [INFO] Apache James :: Server :: Data :: API SUCCESS [2.375s] > [INFO] Apache James :: Server :: Lifecycle API ... SUCCESS [0.987s] > [INFO] Apache James :: Server :: Filesystem API .. SUCCESS [1.124s] > [INFO] Apache James :: Server :: Mailetcontainer API . SUCCESS [0.701s] > [INFO] Apache James :: Server :: Common Utilities SUCCESS [1.575s] > [INFO] Apache James :: Server :: Protocols Library ... SUCCESS [1.181s] > [INFO] Apache James :: Server :: Core SUCCESS [1.092s] > [INFO] Apache James :: Server :: Container Spring SUCCESS [2.466s] > [INFO] Apache James :: Server :: Client .. SUCCESS [1.088s] > [INFO] Apache James :: Server :: DNS Service :: API .. SUCCESS [0.363s] > [INFO] Apache James :: Server :: DNS Service :: Library .. SUCCESS [0.638s] > [INFO] Apache James :: Server :: Mail Queue :: API ... SUCCESS [0.497s] > [INFO] Apache James :: Server :: Mailetcontainer Camel ... SUCCESS [1.471s] > [INFO] Apache James :: Server :: Mailbox Adapter . SUCCESS [0.658s] > [INFO] Apache James :: Server :: DNS Service :: Implementation SUCCESS > [0.480s] > [INFO] Apache James :: Server :: Data :: Library . SUCCESS [0.974s] > [INFO] Apache James :: Server :: Data :: LDAP Implementation SUCCESS [0.483s] > [INFO] Apache James :: Server :: SMTP SUCCESS [1.684s] > [INFO] Apache James :: Server :: IMAP SUCCESS [0.641s] > [INFO] Apache James :: Server :: LMTP SUCCESS [0.811s] > [INFO] Apache James :: Server :: POP3 SUCCESS [0.829s] > [INFO] Apache James :: Server :: FetchMail ... SUCCESS [0.632s] > [INFO] Apache James :: Server :: Mail Queue :: File .. SUCCESS [0.519s] > [INFO] Apache James :: Server :: Mail Queue :: JMS ... SUCCESS [0.964s] > [INFO] Apache James :: Server :: Mail Queue :: ActiveMQ .. SUCCESS [0.898s] > [INFO] Apache James :: Server :: Mailets . SUCCESS [1.878s] > [INFO] Apache James :: Server :: Data :: File Persistence SUCCESS [0.719s] > [INFO] Apache James :: Server :: Data :: JPA Persistence . SUCCESS [1.664s] > [INFO] Apache James :: Server :: Data :: JDBC Persistence SUCCESS [1.177s] > [INFO] Apache James :: Server :: Data :: HBase Persistence SUCCESS [3.562s] > [INFO] Apache James :: Server :: Data :: JCR Persistence . SUCCESS [1.035s] > [INFO] Apache James :: Server :: App . SUCCESS [9.655s] > [INFO] Apache James :: Karaf :: Features . SUCCESS [0.342s] > [INFO] Apache James :: Karaf :: James Server . FAILURE [7.591s] > [INFO] Apache James :: Karaf :: Integration tests SKIPPED > [INFO] > > [INFO] BUILD
[jira] [Created] (JAMES-1624) karaf build failure on james trunk on mvn package
Matthieu Baechler created JAMES-1624: Summary: karaf build failure on james trunk on mvn package Key: JAMES-1624 URL: https://issues.apache.org/jira/browse/JAMES-1624 Project: James Server Issue Type: Bug Components: Build System Affects Versions: Trunk, 3.0.0-beta5 Environment: ➜ james-trunk uname -a Darwin wdx-me 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64 ➜ james-trunk java -version java version "1.7.0_17" Java(TM) SE Runtime Environment (build 1.7.0_17-b02) Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode) ➜ james-trunk mvn -v Apache Maven 3.0.3 (r1075438; 2011-03-01 01:31:09+0800) Maven home: /usr/share/maven Java version: 1.7.0_17, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac" ➜ james-trunk svn info Path: . Working Copy Root Path: /Users/wdx/art/open/james/james-trunk URL: http://svn.apache.org/repos/asf/james/server/trunk Repository Root: http://svn.apache.org/repos/asf Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 1487220 Node Kind: directory Schedule: normal Last Changed Author: eric Last Changed Rev: 1476802 Last Changed Date: 2013-04-29 01:23:37 +0800 (一, 29 4 2013) Reporter: Matthieu Baechler Fix For: Trunk, 3.0.0-beta5 $ mvn clean package -X -DskipTests=true .. .. [INFO] Apache James :: Server SUCCESS [2.266s] [INFO] Apache James :: Server :: Data :: API SUCCESS [2.375s] [INFO] Apache James :: Server :: Lifecycle API ... SUCCESS [0.987s] [INFO] Apache James :: Server :: Filesystem API .. SUCCESS [1.124s] [INFO] Apache James :: Server :: Mailetcontainer API . SUCCESS [0.701s] [INFO] Apache James :: Server :: Common Utilities SUCCESS [1.575s] [INFO] Apache James :: Server :: Protocols Library ... SUCCESS [1.181s] [INFO] Apache James :: Server :: Core SUCCESS [1.092s] [INFO] Apache James :: Server :: Container Spring SUCCESS [2.466s] [INFO] Apache James :: Server :: Client .. SUCCESS [1.088s] [INFO] Apache James :: Server :: DNS Service :: API .. SUCCESS [0.363s] [INFO] Apache James :: Server :: DNS Service :: Library .. SUCCESS [0.638s] [INFO] Apache James :: Server :: Mail Queue :: API ... SUCCESS [0.497s] [INFO] Apache James :: Server :: Mailetcontainer Camel ... SUCCESS [1.471s] [INFO] Apache James :: Server :: Mailbox Adapter . SUCCESS [0.658s] [INFO] Apache James :: Server :: DNS Service :: Implementation SUCCESS [0.480s] [INFO] Apache James :: Server :: Data :: Library . SUCCESS [0.974s] [INFO] Apache James :: Server :: Data :: LDAP Implementation SUCCESS [0.483s] [INFO] Apache James :: Server :: SMTP SUCCESS [1.684s] [INFO] Apache James :: Server :: IMAP SUCCESS [0.641s] [INFO] Apache James :: Server :: LMTP SUCCESS [0.811s] [INFO] Apache James :: Server :: POP3 SUCCESS [0.829s] [INFO] Apache James :: Server :: FetchMail ... SUCCESS [0.632s] [INFO] Apache James :: Server :: Mail Queue :: File .. SUCCESS [0.519s] [INFO] Apache James :: Server :: Mail Queue :: JMS ... SUCCESS [0.964s] [INFO] Apache James :: Server :: Mail Queue :: ActiveMQ .. SUCCESS [0.898s] [INFO] Apache James :: Server :: Mailets . SUCCESS [1.878s] [INFO] Apache James :: Server :: Data :: File Persistence SUCCESS [0.719s] [INFO] Apache James :: Server :: Data :: JPA Persistence . SUCCESS [1.664s] [INFO] Apache James :: Server :: Data :: JDBC Persistence SUCCESS [1.177s] [INFO] Apache James :: Server :: Data :: HBase Persistence SUCCESS [3.562s] [INFO] Apache James :: Server :: Data :: JCR Persistence . SUCCESS [1.035s] [INFO] Apache James :: Server :: App . SUCCESS [9.655s] [INFO] Apache James :: Karaf :: Features . SUCCESS [0.342s] [INFO] Apache James :: Karaf :: James Server . FAILURE [7.591s] [INFO] Apache James :: Karaf :: Integration tests SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 57.322s [INFO] Finished at: Wed May 29 11:41:01 CST 2013 [INFO] Final Memory: 98M/465M [INFO] [ERROR] Failed to execute goal org.apache.karaf.tooling:features-maven-plugin:2.3.0:add-features-to-repo (add-features-to-repo) on project james-karaf-distribution: Error populating repository:
[jira] [Commented] (JAMES-1621) James server modules merge
[
https://issues.apache.org/jira/browse/JAMES-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14954994#comment-14954994
]
Matthieu Baechler commented on JAMES-1621:
--
If I put aside bugs, "svn co && mvn clean install" does the job.
The only thing left to do is to update james website.
> James server modules merge
> --
>
> Key: JAMES-1621
> URL: https://issues.apache.org/jira/browse/JAMES-1621
> Project: James Server
> Issue Type: Task
>Reporter: Matthieu Baechler
> Attachments: current.patch, mailbox.patch, mailet.patch, merge.patch,
> protocols.patch, server.patch
>
>
> To get the following tree into james-project module :
> {code}
> james-project
> | server
> | mailbox
> | mailet
> | mpt
> | protocols
> {code}
> do these commands in https://svn.apache.org/repos/asf/james/project/trunk :
> {code}
> svn mv http://svn.apache.org/repos/asf/james/server server
> svn mv http://svn.apache.org/repos/asf/james/mailbox mailbox
> svn mv http://svn.apache.org/repos/asf/james/mailet mailet
> svn mv http://svn.apache.org/repos/asf/james/mpt mpt
> svn mv http://svn.apache.org/repos/asf/james/protocols protocols
> {code}
> Then we have to update http://svn.apache.org/repos/asf/james/current
> svn:external property
> {code}
> svn propset svn:externals http://svn.apache.org/repos/asf/james/current
> {code}
> with the content :
> {code}
> hupa https://svn.apache.org/repos/asf/james/hupa/trunk
> jdkim https://svn.apache.org/repos/asf/james/jdkim/trunk
> jspf https://svn.apache.org/repos/asf/james/jspf/trunk
> mime4j https://svn.apache.org/repos/asf/james/mime4j/trunk
> postage https://svn.apache.org/repos/asf/james/postage/trunk
> jsieve https://svn.apache.org/repos/asf/james/jsieve/trunk
> project https://svn.apache.org/repos/asf/james/project/trunk
> skin https://svn.apache.org/repos/asf/james/skin/trunk
> {code}
> Then, to update the documentation and the "project" pom, you have to apply
> the attached patches and finally commit all this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1625) app java 6 build fail on missing apache-james-mailbox-elasticsearch
Matthieu Baechler created JAMES-1625: Summary: app java 6 build fail on missing apache-james-mailbox-elasticsearch Key: JAMES-1625 URL: https://issues.apache.org/jira/browse/JAMES-1625 Project: James Server Issue Type: Bug Components: Build System Reporter: Matthieu Baechler The build fail because apache-james-mailbox-elasticsearch artifact is not built on java 6. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MPT-29) ExternalSession.oneFromLine can lock forever
Matthieu Baechler created MPT-29: Summary: ExternalSession.oneFromLine can lock forever Key: MPT-29 URL: https://issues.apache.org/jira/browse/MPT-29 Project: James MPT Issue Type: Bug Components: Main Reporter: Matthieu Baechler ExternalSession.oneFromLine call read but doesn't handle -1 return value. It can lead to infinite loop trying to read from an terminated stream. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (MAILBOX-236) Strong type for Mailbox id
[ https://issues.apache.org/jira/browse/MAILBOX-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler closed MAILBOX-236. - Resolution: Fixed Strong type for Mailbox id -- Key: MAILBOX-236 URL: https://issues.apache.org/jira/browse/MAILBOX-236 Project: James Mailbox Issue Type: Improvement Reporter: Matthieu Baechler I'd like to bring something that bothers me : whenever you get an Id from a Mailbox, you can only call Object methods. It makes some code rely on toString() call in case of serialization. If you put aside some special types, toString is not supposed to return a stable and meaningful value. I'd like to make Message and Mailbox use a bounded parameters. This parameter would extend an Id interface, and this interface could have a serialize method. Comments welcome (and patch is coming soon) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1605) AbstractRecipientRewriteTable.mapAddress doesn't respect domainAlias ordering
Matthieu Baechler created JAMES-1605:
Summary: AbstractRecipientRewriteTable.mapAddress doesn't respect
domainAlias ordering
Key: JAMES-1605
URL: https://issues.apache.org/jira/browse/JAMES-1605
Project: James Server
Issue Type: Bug
Reporter: Matthieu Baechler
This code snippet seems to tries to putting aliasdomain entries in front of the
list while keeping entries original order.
{code}
while (mapIt.hasNext()) {
int i = 0;
String mapping = mapIt.next();
if
(mapping.startsWith(RecipientRewriteTable.ALIASDOMAIN_PREFIX)) {
col.add(i, mapping);
i++;
} else {
col.add(mapping);
}
}
{code}
I looks like no test covers this feature because it actually mess with
aliasdomain ordering (the 'i' counter is reset for every loop)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MPT-22) Some modules don't compile under java 6 because of required dependencies
Matthieu Baechler created MPT-22: Summary: Some modules don't compile under java 6 because of required dependencies Key: MPT-22 URL: https://issues.apache.org/jira/browse/MPT-22 Project: James MPT Issue Type: Bug Reporter: Matthieu Baechler Same issue as https://issues.apache.org/jira/browse/MAILBOX-247 but for mpt modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1607) Make MailboxCopierManagementMBean spring-independent
Matthieu Baechler created JAMES-1607: Summary: Make MailboxCopierManagementMBean spring-independent Key: JAMES-1607 URL: https://issues.apache.org/jira/browse/JAMES-1607 Project: James Server Issue Type: Improvement Components: JMX Reporter: Matthieu Baechler MailboxCopierManagementMBean features are very handy and should not have a hard dependency on spring. We could define a "BeanResolver" interface to allow some other injection framework to provide it. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-247) Mailbox doesn't build with Java 6 because of elasticsearch module
Matthieu Baechler created MAILBOX-247: - Summary: Mailbox doesn't build with Java 6 because of elasticsearch module Key: MAILBOX-247 URL: https://issues.apache.org/jira/browse/MAILBOX-247 Project: James Mailbox Issue Type: Bug Reporter: Matthieu Baechler elasticsearch module makes mailbox modules build fail because it depends on tika and tika is not built under Java 6. elasticsearch module should not depend on tika if java < 1.8 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (MAILBOX-247) Mailbox doesn't build with Java 6 because of elasticsearch module
[ https://issues.apache.org/jira/browse/MAILBOX-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler resolved MAILBOX-247. --- Resolution: Fixed Merged on trunk > Mailbox doesn't build with Java 6 because of elasticsearch module > - > > Key: MAILBOX-247 > URL: https://issues.apache.org/jira/browse/MAILBOX-247 > Project: James Mailbox > Issue Type: Bug >Reporter: Matthieu Baechler > > elasticsearch module makes mailbox modules build fail because it depends on > tika and tika is not built under Java 6. > elasticsearch module should not depend on tika if java < 1.8 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (MPT-22) Some modules don't compile under java 6 because of required dependencies
[ https://issues.apache.org/jira/browse/MPT-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler resolved MPT-22. -- Resolution: Fixed merged on trunk > Some modules don't compile under java 6 because of required dependencies > > > Key: MPT-22 > URL: https://issues.apache.org/jira/browse/MPT-22 > Project: James MPT > Issue Type: Bug >Reporter: Matthieu Baechler > > Same issue as https://issues.apache.org/jira/browse/MAILBOX-247 but for mpt > modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1603) cli should not depend on james-server-spring
[ https://issues.apache.org/jira/browse/JAMES-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790521#comment-14790521 ] Matthieu Baechler commented on JAMES-1603: -- Can someone merge this PR please (or comment it, of course) ? > cli should not depend on james-server-spring > > > Key: JAMES-1603 > URL: https://issues.apache.org/jira/browse/JAMES-1603 > Project: James Server > Issue Type: Bug > Components: CLI >Reporter: Matthieu Baechler > > cli depends on james-server-spring to access MailboxCopierManagementMBean > interface. > It's probably a simple mistake to fix, MBeans are usually into data-api > module, we should have to move MailboxCopierManagementMBean to data-api too. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-1610) CLI usage doesn't output command names
[
https://issues.apache.org/jira/browse/JAMES-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Baechler resolved JAMES-1610.
--
Resolution: Fixed
merged by benoit
> CLI usage doesn't output command names
> --
>
> Key: JAMES-1610
> URL: https://issues.apache.org/jira/browse/JAMES-1610
> Project: James Server
> Issue Type: Bug
> Components: CLI
>Reporter: Matthieu Baechler
>
> Current output :
> {code}
> usage: java org.apache.james.cli.ServerCmd --host
>
> -h,--hostnode hostname or ip address
> -p,--portremote jmx agent port number
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Should be :
> {code}
> usage: java org.apache.james.cli.ServerCmd --host
>
> -h,--hostnode hostname or ip address
> -p,--portremote jmx agent port number
> adduser
> removeuser
> listusers
> adddomain
> removedomain
> containsdomain
> listdomains
> listmappings
> listuserdomainmappings
> addaddressmapping
> removeaddressmapping
> addregexmapping
> removeregexmapping
> setpassword
> copymailbox
> deleteusermailboxes
> createmailbox
> listusermailboxes
> deletemailbox
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-1603) cli should not depend on james-server-spring
[ https://issues.apache.org/jira/browse/JAMES-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler resolved JAMES-1603. -- Resolution: Fixed merged > cli should not depend on james-server-spring > > > Key: JAMES-1603 > URL: https://issues.apache.org/jira/browse/JAMES-1603 > Project: James Server > Issue Type: Bug > Components: CLI >Reporter: Matthieu Baechler > > cli depends on james-server-spring to access MailboxCopierManagementMBean > interface. > It's probably a simple mistake to fix, MBeans are usually into data-api > module, we should have to move MailboxCopierManagementMBean to data-api too. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1607) Make MailboxCopierManagementMBean spring-independent
[ https://issues.apache.org/jira/browse/JAMES-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791689#comment-14791689 ] Matthieu Baechler commented on JAMES-1607: -- be careful, this PR comes with https://github.com/apache/james/pull/5 > Make MailboxCopierManagementMBean spring-independent > > > Key: JAMES-1607 > URL: https://issues.apache.org/jira/browse/JAMES-1607 > Project: James Server > Issue Type: Improvement > Components: JMX >Reporter: Matthieu Baechler > > MailboxCopierManagementMBean features are very handy and should not have a > hard dependency on spring. > We could define a "BeanResolver" interface to allow some other injection > framework to provide it. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1593) James Spooler performance issue
[ https://issues.apache.org/jira/browse/JAMES-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791823#comment-14791823 ] Matthieu Baechler commented on JAMES-1593: -- Unfortunately, switching to oracle javamail implementation (even upgrading to 1.5.4) breaks an existing test (see git commit 51d652939828bafd6dcb724d89c8bf9348a2137c ) I think we have to choose between : 1. fix geronimo 2. use oracle javamail and change to failing test (that seems less important than an infinite locking) Someone has another idea ? > James Spooler performance issue > --- > > Key: JAMES-1593 > URL: https://issues.apache.org/jira/browse/JAMES-1593 > Project: James Server > Issue Type: Bug > Components: SMTPServer >Affects Versions: 3.0-beta4 > Environment: Linux , CentOS release 6.6 (Final), >Reporter: Mehdi Salarkia > Labels: newbie, performance > Attachments: 0001-JAMES-1593-unit-test-to-show-geronimo-bug.patch, > problem_1.eml > > > We have a mail system based on Apache james and we are experiencing some > performance issues . > The current implementation of Apache james has a dependency on Apache > Geronimo for mime and mail processing and it seems there is an issue at-least > in the version "geronimo-javamail_1.4_mail" package . > It seems like the "javax.mail.internet.MimeMessage.getEncoding()" method > never finishes and when I look at the cpu and I profiled the application it > shows this method has a high cpu consumtion, here is a jstack of what was > happening at the time: > "spooler-1" daemon prio=10 tid=0x2b3ee9a5 nid=0x57b4 runnable > [0x2b3e8388d000] >java.lang.Thread.State: RUNNABLE > at javax.mail.internet.MimeMessage.getEncoding(MimeMessage.java:751) > at > org.apache.james.core.MimeMessageUtil.writeMessageBodyTo(MimeMessageUtil.java:135) > at > org.apache.james.core.MimeMessageWrapper.writeTo(MimeMessageWrapper.java:338) > - locked <0x00060ceef588> (a > org.apache.james.core.MimeMessageWrapper) > at > org.apache.james.mailrepository.file.FileMailRepository.internalStore(FileMailRepository.java:203) > at > org.apache.james.mailrepository.lib.AbstractMailRepository.store(AbstractMailRepository.java:98) > at > org.apache.james.transport.mailets.ToRepository.service(ToRepository.java:91) > at > org.apache.james.mailetcontainer.impl.camel.CamelProcessor.process(CamelProcessor.java:65) > at > org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) > at > org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) > at > org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) > at > org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) > at > org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) > at > org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) > at > org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) > at > org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) > at > org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) > at > org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) > at > org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) > at > org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91) > at > org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) > at > org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:334) > at > org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:220) > at > org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) > at > org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) > at > org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303) > at > org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) > at > org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) > at > org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:81) > at > org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) > at >
[jira] [Updated] (JAMES-1593) James Spooler performance issue
[ https://issues.apache.org/jira/browse/JAMES-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler updated JAMES-1593: - Attachment: 0001-JAMES-1593-unit-test-to-show-geronimo-bug.patch This test case show the broken geronimo behavior > James Spooler performance issue > --- > > Key: JAMES-1593 > URL: https://issues.apache.org/jira/browse/JAMES-1593 > Project: James Server > Issue Type: Bug > Components: SMTPServer >Affects Versions: 3.0-beta4 > Environment: Linux , CentOS release 6.6 (Final), >Reporter: Mehdi Salarkia > Labels: newbie, performance > Attachments: 0001-JAMES-1593-unit-test-to-show-geronimo-bug.patch, > problem_1.eml > > > We have a mail system based on Apache james and we are experiencing some > performance issues . > The current implementation of Apache james has a dependency on Apache > Geronimo for mime and mail processing and it seems there is an issue at-least > in the version "geronimo-javamail_1.4_mail" package . > It seems like the "javax.mail.internet.MimeMessage.getEncoding()" method > never finishes and when I look at the cpu and I profiled the application it > shows this method has a high cpu consumtion, here is a jstack of what was > happening at the time: > "spooler-1" daemon prio=10 tid=0x2b3ee9a5 nid=0x57b4 runnable > [0x2b3e8388d000] >java.lang.Thread.State: RUNNABLE > at javax.mail.internet.MimeMessage.getEncoding(MimeMessage.java:751) > at > org.apache.james.core.MimeMessageUtil.writeMessageBodyTo(MimeMessageUtil.java:135) > at > org.apache.james.core.MimeMessageWrapper.writeTo(MimeMessageWrapper.java:338) > - locked <0x00060ceef588> (a > org.apache.james.core.MimeMessageWrapper) > at > org.apache.james.mailrepository.file.FileMailRepository.internalStore(FileMailRepository.java:203) > at > org.apache.james.mailrepository.lib.AbstractMailRepository.store(AbstractMailRepository.java:98) > at > org.apache.james.transport.mailets.ToRepository.service(ToRepository.java:91) > at > org.apache.james.mailetcontainer.impl.camel.CamelProcessor.process(CamelProcessor.java:65) > at > org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) > at > org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) > at > org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) > at > org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) > at > org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) > at > org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) > at > org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) > at > org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) > at > org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) > at > org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) > at > org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) > at > org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91) > at > org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) > at > org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:334) > at > org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:220) > at > org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) > at > org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) > at > org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303) > at > org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) > at > org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) > at > org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:81) > at > org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) > at > org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) > at > org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) > at > org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) > at >
[jira] [Created] (MAILBOX-248) The source code should not issue any warning
Matthieu Baechler created MAILBOX-248: - Summary: The source code should not issue any warning Key: MAILBOX-248 URL: https://issues.apache.org/jira/browse/MAILBOX-248 Project: James Mailbox Issue Type: Improvement Reporter: Matthieu Baechler A great way to be productive with our IDEs is to fix all warnings. That way, we can easily detect newly introduced warning that could be real bugs and fix them immediately. I propose to fix all warning that I find in eclipse as a first step. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1610) CLI usage doesn't output command names
Matthieu Baechler created JAMES-1610:
Summary: CLI usage doesn't output command names
Key: JAMES-1610
URL: https://issues.apache.org/jira/browse/JAMES-1610
Project: James Server
Issue Type: Bug
Components: CLI
Reporter: Matthieu Baechler
Current output :
{code}
usage: java org.apache.james.cli.ServerCmd --host
-h,--hostnode hostname or ip address
-p,--portremote jmx agent port number
{code}
Should be :
{code}
usage: java org.apache.james.cli.ServerCmd --host
-h,--hostnode hostname or ip address
-p,--portremote jmx agent port number
adduser
removeuser
listusers
adddomain
removedomain
containsdomain
listdomains
listmappings
listuserdomainmappings
addaddressmapping
removeaddressmapping
addregexmapping
removeregexmapping
setpassword
copymailbox
deleteusermailboxes
createmailbox
listusermailboxes
deletemailbox
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-254) Don't depends on commons-logging in HBase
Matthieu Baechler created MAILBOX-254: - Summary: Don't depends on commons-logging in HBase Key: MAILBOX-254 URL: https://issues.apache.org/jira/browse/MAILBOX-254 Project: James Mailbox Issue Type: Bug Components: hbase Reporter: Matthieu Baechler Since MAILBOX-250, hbase mailbox depends on commons-logging. James uses slf4j as a logging facade and we should use jcl-over-slf4j to make the bridge between hadoop and hbase dependencies and slf4j. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
