[JIRA] (OSJ-379) "trustAnchors parameter must be non-empty" failure in httpClient

[Brent Putman (Jira)]

Brent Putman ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A97de0981-adc3-4044-95ed-131622fad81e ) *commented* on OSJ-379 ( https://shibboleth.atlassian.net/browse/OSJ-379?atlOrigin=eyJpIjoiNDdkZmY5NmNjOTE0NDVmMjk3MjI4YTdmZGY0ZjE1ZGIiLCJwIjoiaiJ9 )

Re: "trustAnchors parameter must be non-empty" failure in httpClient ( https://shibboleth.atlassian.net/browse/OSJ-379?atlOrigin=eyJpIjoiNDdkZmY5NmNjOTE0NDVmMjk3MjI4YTdmZGY0ZjE1ZGIiLCJwIjoiaiJ9 )

Ok, thanks. Yes, same on my searching. It’s common for it to always fail if the trust store is non-existent, empty, no perms, etc. But not intermittently.

Since this file is supplied by an RPM, I wonder if there is a correlation between when RPM updates are applied and the intermittent errors. Replacing/updating that package file on the filesystem isn’t instantaneous. So maybe it’s just “unlucky” that some attempted reads are when the file is in an unreadable state during the RPM update? (Although on second thought, probably you shut down your IdP when you update the Java package, so maybe this is a red herring…)

Or could there be some other process that is attempting to periodically refresh that trust store file somehow, outside of an explicit RPM update? I don’t know Rocky Linux that well.

Short of a bug in Java itself, live file manipulation/update is the only thing I can think of.

( https://shibboleth.atlassian.net/browse/OSJ-379#add-comment?atlOrigin=eyJpIjoiNDdkZmY5NmNjOTE0NDVmMjk3MjI4YTdmZGY0ZjE1ZGIiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/OSJ-379#add-comment?atlOrigin=eyJpIjoiNDdkZmY5NmNjOTE0NDVmMjk3MjI4YTdmZGY0ZjE1ZGIiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100225- sha1:d57183e )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230518/270c9592/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-bae4d741-0ebd-4a1c-b172-c6e0af0ed0c6
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230518/270c9592/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-c0fd29e0-5ae8-4bc6-805c-865e76aee26c
Type: image/png
Size: 345 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230518/270c9592/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-55d1c83d-484b-4f2f-bdd9-f13d860c2db6
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230518/270c9592/attachment-0005.png>