Voltar
-
Título
Azure SQL Database agent SQL PI dashboard doesn't open and UI error for Connection Details -
Descrição
SQL PI dashboard doesn't open for any Azure SQL Database agent. Clicking on the SQL PI icon doesn't appear to do anything.
SQL Performance Investigator screen in the Global Administration section doesn't load, it gets stuck at 95%.
Corresponding FMS (Management Server) logs show:
ERROR [http-exec-4075] org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/console].[Portal Servlet] - Servlet.service() for servlet [Portal Servlet] in context with path [/console] threw exception [Could not initialize class com.quest.qsi.fason.framework.utils.QSIAES] with root cause java.lang.NoClassDefFoundError: Could not initialize class com.quest.qsi.fason.framework.utils.QSIAES at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83) at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:60) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:235) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:239) at system._dbwc_azure_GA_Database_spi.scripts.prepareAzureAgentsSessions.run(prepareAzureAgentsSessions:35) [...]
Connection Details in the Global Administration section for Azure SQL DB agent generates a message for Error rendering view "inner"
Corresponding FMS logs show:
ERROR [http-exec-31373] com.quest.wcf.portal.ajax.BaseAjaxDelegate - Error rendering view: inner com.quest.wcf.datasupport.progress.ProgressException: failed to complete ProgressTracker at com.quest.wcf.core.module.function.BaseAsyncProgressTracker.isComplete(BaseAsyncProgressTracker.java:114) at com.quest.wcf.portal.viewcomponents.BaseTrackingProgressInfo.checkTracker(BaseTrackingProgressInfo.java:126) at com.quest.wcf.portal.viewcomponents.TrackingProgressInfo.getAndCheckTracker(TrackingProgressInfo.java:55) at com.quest.wcf.portal.viewcomponents.BaseTrackingProgressInfo.getProgressTracker(BaseTrackingProgressInfo.java:84) [...] Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.quest.qsi.fason.framework.utils.QSIAES [...]
And:2022-12-07 11:37:08.766 ERROR [http-exec-29303] com.quest.wcf.portal.ajax.BaseAjaxDelegate - Error rendering view: inner com.quest.wcf.datasupport.progress.ProgressException: failed to complete ProgressTracker at com.quest.wcf.core.module.function.BaseAsyncProgressTracker.isComplete(BaseAsyncProgressTracker.java:114) at com.quest.wcf.portal.viewcomponents.BaseTrackingProgressInfo.checkTracker(BaseTrackingProgressInfo.java:126) at com.quest.wcf.portal.viewcomponents.TrackingProgressInfo.getAndCheckTracker(TrackingProgressInfo.java:55) at com.quest.wcf.portal.viewcomponents.BaseTrackingProgressInfo.getProgressTracker(BaseTrackingProgressInfo.java:84) [...] Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of com/quest/nitro/service/cartridge/api/CartridgeClassLoader$PublicApiClassLoader) previously initiated loading for a different type with name "org/apache/logging/log4j/spi/LoggerContext" [...]
-
Causa
These issues are due to a Java class loading problem when using a solution from an older version of KB 4225835 that suggested to save two jar files (log4j-core.jar and log4j-api.jar) into the [FMS_HOME]/lib directory.
This issue affects Foglight 5.9.x with Azure SQL DB cartridge versions 5.9.7.23 and 5.9.7.24. -
Resolução
RESOLUTION 1
Same as described in KB 4225835, the preferred solution is to upgrade Foglight and cartridges to 6.1.x or higher.
RESOLUTION 2
Hotfix HFIX-381 was backported for Azure SQL DB cartridge version 5.9.7.24 through Global View cartridge version 5.9.7.24 available for download from the Support Portal .- Install the cartridge DB_Global_View_UI-5_9_7_24.car
- Remove specified jars from [FMS_HOME]/lib
- Stop fms service/daemon
- Remove log4j-api.jar and log4j-core.jar from [FMS_HOME]/lib
- Start fms service/daemon
-
ID do defeito
HFIX-381