[JIRA] (IDP-2025) Transitory errors on Windows V5 nightly builds

[Daniel Fisher (Jira)]

Daniel Fisher ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3A5040b2f7-37ad-4449-b621-76b5c7e66a9d ) *commented* on IDP-2025 ( https://shibboleth.atlassian.net/browse/IDP-2025?atlOrigin=eyJpIjoiOTI3NTBmYjBmYzdkNDBjYzg0OTBlODNkMmU0NTZhMGYiLCJwIjoiaiJ9 )

Re: Transitory errors on Windows V5 nightly builds ( https://shibboleth.atlassian.net/browse/IDP-2025?atlOrigin=eyJpIjoiOTI3NTBmYjBmYzdkNDBjYzg0OTBlODNkMmU0NTZhMGYiLCJwIjoiaiJ9 )

The latest version of ldaptive has the ability to auto reconnect when a connection is lost and this feature is on by default. The idp-conf AbstractFlowTest implementations start and stop the underlying directory after each test. This causes ldaptive to attempt reconnects, which fills up the logs will errors. Note that we could choose to ignore the errors or turn off this feature, but I’m saving that as a last resort.

I’m attempting to refactor the tests to do what I think is the right thing, which is to tie the directory lifecycle to the spring context lifecycle. That would allow the test to start the directory when password auth is needed and then stop the directory after the LDAP connection pools have been closed in response to the spring context shutting down.

I still haven’t bottomed out on how this interaction is causing a test failure.

( https://shibboleth.atlassian.net/browse/IDP-2025#add-comment?atlOrigin=eyJpIjoiOTI3NTBmYjBmYzdkNDBjYzg0OTBlODNkMmU0NTZhMGYiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-2025#add-comment?atlOrigin=eyJpIjoiOTI3NTBmYjBmYzdkNDBjYzg0OTBlODNkMmU0NTZhMGYiLCJwIjoiaiJ9 )

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#100209- sha1:6031644 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20221026/a3c8cdfb/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-c566505d-e7f7-4d08-aea8-dc2420fc77e2
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221026/a3c8cdfb/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-85d78372-bf67-42f4-9ba8-4f60c50557ce
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221026/a3c8cdfb/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-46366aa1-6de7-44ff-b225-3a42081983a6
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221026/a3c8cdfb/attachment-0005.png>