Error - trustAnchors parameter must be non-empty

java hudson jakarta-mail jenkins
David Gill picture David Gill · Jul 22, 2011 · Viewed 644.9k times · Source

I'm trying to configure my e-mail on Jenkins/Hudson, and I constantly receive the error:

java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be
    non-empty

I've seen a good amount of information online about the error, but I have not gotten any to work. I'm using Sun's JDK on Fedora Linux (not OpenJDK).

Here are a few things I've tried. I tried following the advice from this post, but copying the cacerts from Windows over to my Fedora box hosting Jenkins didn't work. I tried following this guide as I'm trying to configure Gmail as my SMTP server, but it didn't work either. I also tried to download and move those cacert files manually and move them over to my Java folder using a variation of the commands on this guide.

I am open to any suggestions as I'm currently stuck right now. I have gotten it to work from a Windows Hudson server, but I am struggling on Linux.

Answer

Marquis of Lorne picture Marquis of Lorne · Jul 22, 2011

This bizarre message means that the truststore you specified was:

  • empty,
  • not found, or
  • couldn't be opened (due to access permissions for example).

See also @AdamPlumb's answer below.

Related questions

Bamboo Vs. Hudson(a.k.a. Jenkins) vs Any other CI systems

Anyone out there have experience with both Hudson and Bamboo? Any thoughts on the relative strengths and weaknesses of these products? Okay, since folks keep mentioning other CI products I'll open this up further. Here are my general problem. I …

Read More
What is the difference between Hudson and CruiseControl for Java projects?

I think the title sums it up. I just want to know why one or the other is better for continous integration builds of Java projects from Svn.

Read More
How can I configure a Hudson job to use a specific JDK?

I have a number of projects running on a Hudson slave. I'd like one of them to run Ant under Java6, rather than the default (which is Java5 in my environment). In the project configuration view, I was hoping to …

Read More