Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
7.0.0 DXP FP8
-
7.0.x
-
Committed
-
1.75
-
3
Description
Description
The master node is being notified multiple times that AuthVerifier configurations are being modified, while a slave node is starting up.
Note: This only happens when using a bundled instance, when the com.liferay.portal.security.auth.verifier module is deployed via LPKG.
Steps to Reproduce: Bundle + DE-8 fixpack
- Configure two Liferay DXP bundles + DE-8 fixpack
- Configure Multicast Clustering between the two nodes
- Startup the first node in the cluster
- Start a debugger for the first node
- Breakpoint on: Line 72
- Class: com/liferay/portal/security/auth/verifier/internal/module/BaseAuthVerifierPublisher.java
- Method: protected void modified(BundleContext bundleContext, Map<String, Object> properties)
- Line: deactivate();
- Sample Breakpoint: sample_breakpoint_settings.png
- Breakpoint on: Line 72
- Make sure the 1st node is completed started
- Startup the 2nd node
- Make sure to clear osgi/state folder if Node 2 is not a fresh instance
- Notice the breakpoints
- Can add logging instead of suspending the call on breakpoint (at least in intellij)
Expected behavior: The master node is not being notified regarding AuthVerifier configurations being modified.
Actual behavior: The master node is being notified multiple times regarding AuthVerifier configurations being modified.
Sample Breakpoint Log
com.liferay.portal.secur[email protected]7c853f6a com.liferay.portal.secur[email protected]6f8d81be com.liferay.portal.[email protected]4a567eb9 com.liferay.portal.[email protected]37661f14 com.[email protected]5421778a com.[email protected]3e08f715
Steps to demonstrate that the issue is not reproducible when not deployed via lpkg
- Continuing from the steps above
- Shutdown Node 2
- Find com.liferay.portal.security.auth.verifier-2.0.2.jar within osgi/marketplace/Liferay Foundation.lpkg
- Copy com.liferay.portal.security.auth.verifier-2.0.2.jar to the osgi/marketplace/override folder
- Startup the 2nd node
- Make sure to clear osgi/state folder if Node 2 is not a fresh instance
Actual behavior: The master node is not being notified regarding the AuthVerifier configurations being modified.