Build failed in Jenkins: jdkim-trunk ยป Apache James :: jDKIM :: DomainKey Project #2324

2015-03-31 Thread Apache Jenkins Server
See 
https://builds.apache.org/job/jdkim-trunk/org.apache.james.jdkim$apache-jdkim-project/2324/

--
maven3-agent.jar already up to date
maven3-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
===[JENKINS REMOTING CAPACITY]===   channel started
Executing Maven:  -B -f 
https://builds.apache.org/job/jdkim-trunk/org.apache.james.jdkim$apache-jdkim-project/ws/pom.xml
 -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/1 -U clean 
deploy
[INFO] Scanning for projects...
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] Apache James :: jDKIM :: DomainKey Project
[INFO] Apache James :: jDKIM
[INFO] Apache James :: jDKIM :: Mailets
[INFO] Apache James :: jDKIM :: Assembly
[INFO] 
[INFO] 
[INFO] Building Apache James :: jDKIM :: DomainKey Project 0.3-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ 
apache-jdkim-project ---
[INFO] Deleting 
https://builds.apache.org/job/jdkim-trunk/org.apache.james.jdkim$apache-jdkim-project/ws/target
[TASKS] Scanning folder 
'https://builds.apache.org/job/jdkim-trunk/org.apache.james.jdkim$apache-jdkim-project/ws/'
 for files matching the pattern '**/*.java' - excludes: main/**/*, 
mailets/**/*, assemble/**/*
[TASKS] Found 0 files to scan for tasks
Found 0 open tasks.
[TASKS] Computing warning deltas based on reference build #2323
log4j:WARN No appenders could be found for logger 
(org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ 
apache-jdkim-project ---
[INFO] 
[INFO] --- maven-site-plugin:3.0:attach-descriptor (attach-descriptor) @ 
apache-jdkim-project ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
apache-jdkim-project ---
[INFO] Installing 
https://builds.apache.org/job/jdkim-trunk/org.apache.james.jdkim$apache-jdkim-project/ws/pom.xml
 to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/james/jdkim/apache-jdkim-project/0.3-SNAPSHOT/apache-jdkim-project-0.3-SNAPSHOT.pom
[INFO] Installing 
https://builds.apache.org/job/jdkim-trunk/org.apache.james.jdkim$apache-jdkim-project/ws/target/apache-jdkim-project-0.3-SNAPSHOT-site.xml
 to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/james/jdkim/apache-jdkim-project/0.3-SNAPSHOT/apache-jdkim-project-0.3-SNAPSHOT-site.xml
[INFO] 
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ 
apache-jdkim-project ---
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/james/jdkim/apache-jdkim-project/0.3-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata 
org.apache.james.jdkim:apache-jdkim-project:0.3-SNAPSHOT/maven-metadata.xml 
from/to apache.snapshots.https 
(https://repository.apache.org/content/repositories/snapshots): 
java.lang.RuntimeException: Could not generate DH keypair
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache James :: jDKIM :: DomainKey Project  FAILURE [13.076s]
[INFO] Apache James :: jDKIM . SKIPPED
[INFO] Apache James :: jDKIM :: Mailets .. SKIPPED
[INFO] Apache James :: jDKIM :: Assembly . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 14.870s
[INFO] Finished at: Tue Mar 31 11:23:22 UTC 2015
[INFO] Final Memory: 13M/245M
[INFO] 
Waiting for Jenkins to finish collecting data[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on 
project apache-jdkim-project: Failed to retrieve remote metadata 
org.apache.james.jdkim:apache-jdkim-project:0.3-SNAPSHOT/maven-metadata.xml: 
Could not transfer metadata 
org.apache.james.jdkim:apache-jdkim-project:0.3-SNAPSHOT/maven-metadata.xml 
from/to apache.snapshots.https 
(https://repository.apache.org/content/repositories/snapshots): 
java.lang.RuntimeException: Could not generate DH keypair: Prime size must be 
multiple of 64, and can only range from 512 to 1024 (inclusive) - [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 

Build failed in Jenkins: jdkim-trunk #2324

2015-03-31 Thread Apache Jenkins Server
See https://builds.apache.org/job/jdkim-trunk/2324/

--
Started by timer
Building remotely on ubuntu-6 (docker Ubuntu ubuntu) in workspace 
https://builds.apache.org/job/jdkim-trunk/ws/
Updating http://svn.apache.org/repos/asf/james/jdkim/trunk at revision 
'2015-03-31T11:23:00.938 +'
At revision 1670305
no change for http://svn.apache.org/repos/asf/james/jdkim/trunk since the 
previous build
[locks-and-latches] Checking to see if we really have the locks
[locks-and-latches] Have all the locks, build can start
Parsing POMs
maven3-agent.jar already up to date
maven3-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[trunk] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx2g -Xms256m 
-XX:MaxPermSize=512m -cp 
/home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar
 org.jvnet.hudson.maven3.agent.Maven3Main 
/home/jenkins/tools/maven/apache-maven-3.0.4 
/home/jenkins/jenkins-slave/slave.jar 
/home/jenkins/jenkins-slave/maven3-interceptor.jar 
/home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 45586
===[JENKINS REMOTING CAPACITY]===   channel started
Executing Maven:  -B -f 
https://builds.apache.org/job/jdkim-trunk/ws/trunk/pom.xml 
-Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/1 -U clean 
deploy
[INFO] Scanning for projects...
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] Apache James :: jDKIM :: DomainKey Project
[INFO] Apache James :: jDKIM
[INFO] Apache James :: jDKIM :: Mailets
[INFO] Apache James :: jDKIM :: Assembly
[INFO] 
[INFO] 
[INFO] Building Apache James :: jDKIM :: DomainKey Project 0.3-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ 
apache-jdkim-project ---
[INFO] Deleting https://builds.apache.org/job/jdkim-trunk/ws/trunk/target
[TASKS] Scanning folder 'https://builds.apache.org/job/jdkim-trunk/ws/trunk' 
for files matching the pattern '**/*.java' - excludes: main/**/*, mailets/**/*, 
assemble/**/*
[TASKS] Found 0 files to scan for tasks
Found 0 open tasks.
[TASKS] Computing warning deltas based on reference build #2323
log4j:WARN No appenders could be found for logger 
(org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ 
apache-jdkim-project ---
[INFO] 
[INFO] --- maven-site-plugin:3.0:attach-descriptor (attach-descriptor) @ 
apache-jdkim-project ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
apache-jdkim-project ---
[INFO] Installing https://builds.apache.org/job/jdkim-trunk/ws/trunk/pom.xml 
to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/james/jdkim/apache-jdkim-project/0.3-SNAPSHOT/apache-jdkim-project-0.3-SNAPSHOT.pom
[INFO] Installing 
https://builds.apache.org/job/jdkim-trunk/ws/trunk/target/apache-jdkim-project-0.3-SNAPSHOT-site.xml
 to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/james/jdkim/apache-jdkim-project/0.3-SNAPSHOT/apache-jdkim-project-0.3-SNAPSHOT-site.xml
[INFO] 
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ 
apache-jdkim-project ---
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/james/jdkim/apache-jdkim-project/0.3-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata 
org.apache.james.jdkim:apache-jdkim-project:0.3-SNAPSHOT/maven-metadata.xml 
from/to apache.snapshots.https 
(https://repository.apache.org/content/repositories/snapshots): 
java.lang.RuntimeException: Could not generate DH keypair
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache James :: jDKIM :: DomainKey Project  FAILURE [13.076s]
[INFO] Apache James :: jDKIM . SKIPPED
[INFO] Apache James :: jDKIM :: Mailets .. SKIPPED
[INFO] Apache James :: jDKIM :: Assembly . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 14.870s
[INFO] Finished at: Tue Mar 31 11:23:22 UTC 2015
[INFO] Final Memory: 13M/245M
[INFO] 
Waiting for Jenkins to finish collecting data[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on 
project apache-jdkim-project: Failed to retrieve remote metadata 

[jira] [Updated] (MAILBOX-220) StoreMessageManager::getMessages returns no messages when using FROM ranges.

2015-03-31 Thread Tellier Benoit (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAILBOX-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated MAILBOX-220:
---
Summary: StoreMessageManager::getMessages returns no messages when using 
FROM ranges.  (was: toreMessaageManager::getMessages returns no messages when 
using FROM ranges.)

 StoreMessageManager::getMessages returns no messages when using FROM ranges.
 

 Key: MAILBOX-220
 URL: https://issues.apache.org/jira/browse/MAILBOX-220
 Project: James Mailbox
  Issue Type: Bug
  Components: store
Affects Versions: 0.5
Reporter: Tellier Benoit

 I do not get any messages using StoreMessaageManager::getMessages combined 
 with MessageRange::from.
 This is due to the way StoreMessageResultIterator works : it is based on the 
 comparaison with the TO value of the range.
 If this value is set to NOT_A_UID ( which is the case for the from range ), 
 it will result in the StoreMessageResultIterator::hasNext to fail.
 Setting the TO value for the FROM message range to MAX_UID will solve the 
 issue.



--
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-219) A user with any right on a mailbox gets full rights on the given mailbox.

2015-03-31 Thread Tellier Benoit (JIRA)
Tellier Benoit created MAILBOX-219:
--

 Summary: A user with any right on a mailbox gets full rights on 
the given mailbox.
 Key: MAILBOX-219
 URL: https://issues.apache.org/jira/browse/MAILBOX-219
 Project: James Mailbox
  Issue Type: Bug
  Components: api
Affects Versions: 0.5
 Environment: James uses binary operation code in order to store user's 
ACL on a single int.

This was buggy as a or was used to see if the user have a given right. A and 
should have been used.

So, as a consequence, setting any write to a user gives him full rights on the 
given mailbox, wich is a major security issue.

All mailbox implementations are affected.

Reporter: Tellier Benoit






--
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-220) toreMessaageManager::getMessages returns no messages when using FROM ranges.

2015-03-31 Thread Tellier Benoit (JIRA)
Tellier Benoit created MAILBOX-220:
--

 Summary: toreMessaageManager::getMessages returns no messages when 
using FROM ranges.
 Key: MAILBOX-220
 URL: https://issues.apache.org/jira/browse/MAILBOX-220
 Project: James Mailbox
  Issue Type: Bug
  Components: store
Affects Versions: 0.5
Reporter: Tellier Benoit


I do not get any messages using StoreMessaageManager::getMessages combined with 
MessageRange::from.

This is due to the way StoreMessageResultIterator works : it is based on the 
comparaison with the TO value of the range.

If this value is set to NOT_A_UID ( which is the case for the from range ), it 
will result in the StoreMessageResultIterator::hasNext to fail.

Setting the TO value for the FROM message range to MAX_UID will solve the issue.



--
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-219) A user with any right on a mailbox gets full rights on the given mailbox.

2015-03-31 Thread Tellier Benoit (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAILBOX-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated MAILBOX-219:
---
Description: 
James uses binary operation code in order to store user's ACL on a single int.

This was buggy as a or was used to see if the user have a given right. A and 
should have been used.

So, as a consequence, setting any write to a user gives him full rights on the 
given mailbox, wich is a major security issue.

All mailbox implementations are affected.

Environment: (was: James uses binary operation code in order to store 
user's ACL on a single int.

This was buggy as a or was used to see if the user have a given right. A and 
should have been used.

So, as a consequence, setting any write to a user gives him full rights on the 
given mailbox, wich is a major security issue.

All mailbox implementations are affected.
)

 A user with any right on a mailbox gets full rights on the given mailbox.
 -

 Key: MAILBOX-219
 URL: https://issues.apache.org/jira/browse/MAILBOX-219
 Project: James Mailbox
  Issue Type: Bug
  Components: api
Affects Versions: 0.5
Reporter: Tellier Benoit

 James uses binary operation code in order to store user's ACL on a single int.
 This was buggy as a or was used to see if the user have a given right. A and 
 should have been used.
 So, as a consequence, setting any write to a user gives him full rights on 
 the given mailbox, wich is a major security issue.
 All mailbox implementations are affected.



--
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