![]() IF/WHEN INTERESTING PROBLEMS / SOLUTIONS ARISE, I WILL KEEP THIS FORUM UPDATED. THANKS AGAIN FOR THE HELP IN SUGGESTIONS FROM THE FORUM Only the browser LOADING UI… screen made it apparent. So Jenkins never made it clear there was a problem. Only the browser symptoms made me aware of this dilemma.Īs it turns out, Jenkins Maven build processes are extremely robust the Maven builds worked after waiting 2 or 3 minutes and trying again. Nexus + Jenkins performance testing did NOT reveal the above problem. Inside NEXUS we moved the LDAP realm to the BOTTOM of the list. Maven builds waiting, retried, and succeeded. Randomly NEXUS would “choke” on this (for lack of better term) and performance degradation occurred horribly, which caused lag to browsers & maven builds. ![]() LDAP failed to find “anonymous” user, and thus spammed exceptions into WRAPPER.LOG. NEXUS “anonymous” user was only inside the NEXUS’ proprietary XML realm. NEXUS “anonymous” user was NOT in our LDAP realm The NEXUS “anonymous” user was used for all artifact download requests & browser access. Saw LDAP errors were getting spammed whenever Nexus was contacted. We set the NEXUS server ROOT logger to DEBUG level. The fact Maven builds could trigger the NEXUS lag was a key-indicator that the problem was NOT browser-caused. Meaning, either type of mechanism could perform the instigating requests. Importantly, when either of the above behaviors occurred (in Browser or Maven process) But the Nexus lag problem was still there the whole time. Jenkins was so robust however, that Jenkins kept trying artifact downloads again and again, and eventually succeeded in the builds. In a different machine architecture of build machines, our Jenkins SLAVE machines’ MAVEN java processes suffered severe (2-3 minute) lags during artifact downloads. “LOADING UI… / Cannot connect to Nexus” errors. Web Browsers (Firefox / Chrome / Edge) all suffered random, but frequent, The problem manifested itself in a really odd way. Summary below – Maybe the below explanation can help other people… The fix: we put LDAP below the XML realms (as mentioned in NEXUS documentation). Vivaldi is accessible for Windows, Mac, and Linux. Here, users can install all extensions from the Chrome web store on their browser. The program is based on Chromium, the base code that powers Google Chrome. In short: the LDAP Realm position order in NEXUS SERVER configuration was the problem. Vivaldi is a free web browser, established sometime in 2016 by the makers of the Opera browser. Thanks again for everyone’s help & comments. We resolved our “LOADING UI / Cannot connect to Nexus” problems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |