[
https://issues.apache.org/jira/browse/BUILDS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705811#comment-14705811
]
Gavin commented on BUILDS-85:
-----------------------------
Oh I see whats happening.
Most people in this ticket have been talking about Jenkins, so I've deployed
toolchain to jenkins.
Do me a favour please and open a new ticket and I'll do the same for Buildbot ;)
> Could not generate DH keypair / peer not authenticated
> -------------------------------------------------------
>
> Key: BUILDS-85
> URL: https://issues.apache.org/jira/browse/BUILDS-85
> Project: Infra Build Platform
> Issue Type: Bug
> Components: Jenkins
> Reporter: Andreas Lehmkühler
> Assignee: Tony Stevenson
> Attachments: SSLPoke.java
>
>
> We're getting this since june 10th:
> [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ pdfbox-parent ---
> Downloading:https://repository.apache.org/content/repositories/snapshots/org/apache/pdfbox/pdfbox-parent/1.8.10-SNAPSHOT/maven-metadata.xml
> [WARNING] Could not transfer metadata
> org.apache.pdfbox:pdfbox-parent:1.8.10-SNAPSHOT/maven-metadata.xml from/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots): Error
> transferring file: java.lang.RuntimeException: Could not generate DH keypair
> and this:
> [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ pdfbox-parent
> ---
> Downloading:https://repository.apache.org/content/repositories/snapshots/org/apache/pdfbox/pdfbox-parent/2.0.0-SNAPSHOT/maven-metadata.xml
> [WARNING] Could not transfer metadata
> org.apache.pdfbox:pdfbox-parent:2.0.0-SNAPSHOT/maven-metadata.xml from/to
> apache.snapshots.https
> (https://repository.apache.org/content/repositories/snapshots): peer not
> authenticated
> The issue seems to be jdk related as only those builds using java 1.6.0_37
> (unlimited security) are failing. I've reconfigured the trunk build to use
> java 7 and everything works fine, as well as our jdk7 based branch build.
> Any ideas? Maybe a plugin update which doesn't work with java6?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
