[jira] [Created] (JAMES-2076) CassandraSieveRepositoryTests are unstable
Tellier Benoit created JAMES-2076: - Summary: CassandraSieveRepositoryTests are unstable Key: JAMES-2076 URL: https://issues.apache.org/jira/browse/JAMES-2076 Project: James Server Issue Type: Improvement Reporter: Tellier Benoit We have issues with the quotas, as well as with script activation. Apparently, some concurrent delete/inserts/updates were performed on the same entry upon single writes, leading to instability. We should run these operations sequentially. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2075) MimeMessageInputStream did not initialize array size on copy
Tellier Benoit created JAMES-2075: - Summary: MimeMessageInputStream did not initialize array size on copy Key: JAMES-2075 URL: https://issues.apache.org/jira/browse/JAMES-2075 Project: James Server Issue Type: Improvement Components: James Core, JMAP, mailbox Reporter: Tellier Benoit Assignee: Antoine Duprat It leads to many realocations, starting at 32 bytes, and doubling each time. It is not the only class affected: - MessageSearches - FullByteContent - SerialiseToHTTP - StripAttachment - MimeBodyElement - MailHeaders - MimeMessageInputStream - MimeMessageWrapper - MBoxMailRepository - MailMessageAlteringUtils - MIMEMessageConverter -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2074) Run James servers on random ports in tests
Antoine Duprat created JAMES-2074: - Summary: Run James servers on random ports in tests Key: JAMES-2074 URL: https://issues.apache.org/jira/browse/JAMES-2074 Project: James Server Issue Type: Bug Reporter: Antoine Duprat Run James servers on random ports in tests, so they can be played in parallel. No port should be written in _src/test/resources/*.xml_ files. For example: _0.0.0.0:*0*_ instead of _0.0.0.0:*1143*_ -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2073) Run Cassandra test on random port
Antoine Duprat created JAMES-2073: - Summary: Run Cassandra test on random port Key: JAMES-2073 URL: https://issues.apache.org/jira/browse/JAMES-2073 Project: James Server Issue Type: Bug Components: cassandra Reporter: Antoine Duprat The Cassandra server used in tests should use random ports. This may prevent failure when running parallel tests. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (MAILBOX-45) [gsoc2011] Design and Implement Mailbox with NoSQL Storage
[ https://issues.apache.org/jira/browse/MAILBOX-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed MAILBOX-45. --- Resolution: Fixed > [gsoc2011] Design and Implement Mailbox with NoSQL Storage > -- > > Key: MAILBOX-45 > URL: https://issues.apache.org/jira/browse/MAILBOX-45 > Project: James Mailbox > Issue Type: New Feature >Reporter: Eric Charles >Assignee: Norman Maurer > Labels: gsoc2011 > > Context: The mailbox subproject (http://james.apache.org/mailbox/) supports > maildir, SQL database (via JPA) and Java Content Repository (JCR) as > technology for mail storage. This flexibility is achieved thanks to a API > design that abstracts mail storage from the mail protocols. > Task: NoSQL storage (for example CouchDB or Cassandra) has great potential > for mail storage. Design and develop an suitable RESTful integration API and > implementations for as many NoSQL targets as possible in the time. > Mentor: rdonkin at apache dot org > Complexity: easy -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-2072) RFE: support for tight integration with embedded (ie. Jetty) servers
[ https://issues.apache.org/jira/browse/JAMES-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gruust updated JAMES-2072: -- Description: Hello! I'd like to integrate James with my embedded server. That means: * Start and configure all parts of James in (Java) code, possibly via Jetty LifeCycle classes. * Make James use my own EntityManager/EntityTransaction, based on Hibernate/H2. Share transactions with the rest of my server, ie. for writing mails sent by the server to the spool or to manage email users/domains from within Servlet context. * Make James use tables in my pre-existing database, prefixed with "James" or similar. TY! was: Hello! I'd like to integrate James with my embedded server. That means: * Start and configure all parts of James in (Java) code, possibly via Jetty LifeCycle classes. * Make James use my own EntityManager/EntityTransaction, based on Hibernate/H2. Share transactions with the rest of my server, ie. for writing mails sent by the server to the spool or to manage email users/domains. * Make James use tables in my pre-existing database, prefixed with "James" or similar. TY! > RFE: support for tight integration with embedded (ie. Jetty) servers > > > Key: JAMES-2072 > URL: https://issues.apache.org/jira/browse/JAMES-2072 > Project: James Server > Issue Type: New Feature > Components: IMAPServer, mailbox, MailStore & MailRepository, Queue, > SMTPServer, UsersStore & UsersRepository >Affects Versions: 3.0-beta4 > Environment: all >Reporter: Gruust > > Hello! > I'd like to integrate James with my embedded server. That means: > * Start and configure all parts of James in (Java) code, possibly via Jetty > LifeCycle classes. > * Make James use my own EntityManager/EntityTransaction, based on > Hibernate/H2. Share transactions with the rest of my server, ie. for writing > mails sent by the server to the spool or to manage email users/domains from > within Servlet context. > * Make James use tables in my pre-existing database, prefixed with "James" or > similar. > TY! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2072) RFE: support for tight integration with embedded (ie. Jetty) servers
Gruust created JAMES-2072: - Summary: RFE: support for tight integration with embedded (ie. Jetty) servers Key: JAMES-2072 URL: https://issues.apache.org/jira/browse/JAMES-2072 Project: James Server Issue Type: New Feature Components: IMAPServer, mailbox, MailStore & MailRepository, Queue, SMTPServer, UsersStore & UsersRepository Affects Versions: 3.0-beta4 Environment: all Reporter: Gruust Hello! I'd like to integrate James with my embedded server. That means: * Start and configure all parts of James in (Java) code, possibly via Jetty LifeCycle classes. * Make James use my own EntityManager/EntityTransaction, based on Hibernate/H2. Share transactions with the rest of my server, ie. for writing mails sent by the server to the spool or to manage email users/domains. * Make James use tables in my pre-existing database, prefixed with "James" or similar. TY! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-2071) Improve ElasticSearch mapping
Luc DUZAN created JAMES-2071: Summary: Improve ElasticSearch mapping Key: JAMES-2071 URL: https://issues.apache.org/jira/browse/JAMES-2071 Project: James Server Issue Type: Improvement Reporter: Luc DUZAN Firstly in a first time, we put header in ES but we do not specify anything about them in the mapping! By default each time ES see a field (or "subfield") it infear the type for it and create a index for it. If a new document arrive with the same field with a type that is different from the inferre type that will create a exception. So in a first time we should specify in the mapping all the header we need to look for and move the mapping to `dynamic: false`. Also we should review the mapping to see if it suffers from other issues. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (MAILBOX-301) Lucene terms length exceeded on some emails
[
https://issues.apache.org/jira/browse/MAILBOX-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064335#comment-16064335
]
Tellier Benoit commented on MAILBOX-301:
https://github.com/linagora/james-project/pull/864 proposes tests and fixes for
this issue
> Lucene terms length exceeded on some emails
> ---
>
> Key: MAILBOX-301
> URL: https://issues.apache.org/jira/browse/MAILBOX-301
> Project: James Mailbox
> Issue Type: Bug
> Components: elasticsearch
>Affects Versions: master
>Reporter: Tellier Benoit
> Fix For: master
>
>
> Lucene supports a maximum term size of 32KB
> This term size can get exceeded, causing the index to fail.
> Thus, the team had position "ignore_above" filters to filter out too long
> terms and positionned it's value to Lucene maximum.
> However, as stated in
> https://www.elastic.co/guide/en/elasticsearch/reference/current/ignore-above.html
> :
> {code:java}
> Note:
> The value for ignore_above is the character count, but Lucene counts bytes.
> If you use UTF-8 text with many non-ASCII characters, you may want to set the
> limit to 32766 / 3 = 10922 since UTF-8 characters may occupy at most 3 bytes.
> {code}
> Thus the maximum value is computed for string length in ES and not based on
> bytes length in Lucene.
> We can craft a char sequence in UTF-8 exceeding the Lucene value but not
> triggering the ES limit.
> A much lower value (like 4KB) seems more reasonable, as long terms my not be
> significant.
> Note:
> - Implement tests:
> - Demonstrating this bug
> - Demonstrating only too long terms are ignored
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
