After upgrade to UIM 20.3 Admin Console throws Server Error 500

Products

• DX Infrastructure Management

Issue/Introduction

After upgrading UIM from 20.1 to 20.3, the Admin Console stopped working after running the Operator Console upgrade.

A subsequent upgrade to 20.3.1 didn't change the situation. This is a single-box installation - primary hub and OC are running on the same machine.

 

The following is seein the wasp.log:

Exception

org.apache.jasper.JasperException: An exception occurred processing [/jsp/view.jsp] at line [37]

34: <%
35:     String ht = DEF_HEIGHT;
36:     String cp = request.getContextPath();
37:     Locale locale = LocaleUtils.getBestLocale(request);
38:     String strLocale = locale.toString();
39:     String isPortlet = (String)session.getAttribute("is_portlet");
40:     // handle cases where extra locale information is passed in; our downstream tools only use the primary identifier

Stacktrace:
 org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:626)
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:500)
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:385)
 org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
 com.firehunter.adminconsole_core.NimsofCsrfPreventionFilter.doFilter(NimsofCsrfPreventionFilter.java:195)
 org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:126)
 com.firehunter.adminconsole.config.ResponseHeaderFilter.doFilter(ResponseHeaderFilter.java:111)
 com.firehunter.adminconsole.filter.XSSParamFilter.doFilter(XSSParamFilter.java:107)

Root Cause

javax.servlet.ServletException: java.lang.NoSuchMethodError: com.firehunter.ump.auth.NmsAuth.getLiferayUserByLoginName(Ljava/lang/String;)Lcom/liferay/portal/model/User;
 org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:666)
 org.apache.jsp.jsp.view_jsp._jspService(view_jsp.java:431)
 org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:71)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:477)
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:385)
 org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
 com.firehunter.adminconsole_core.NimsofCsrfPreventionFilter.doFilter(NimsofCsrfPreventionFilter.java:195)
 org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:126)
 com.firehunter.adminconsole.config.ResponseHeaderFilter.doFilter(ResponseHeaderFilter.java:111)
 com.firehunter.adminconsole.filter.XSSParamFilter.doFilter(XSSParamFilter.java:107)

Root Cause

java.lang.NoSuchMethodError: com.firehunter.ump.auth.NmsAuth.getLiferayUserByLoginName(Ljava/lang/String;)Lcom/liferay/portal/model/User;
 com.nimsoft.nimbus.probe.service.wasp.api.i18n.LocaleUtils.getBestLocale(LocaleUtils.java:63)
 org.apache.jsp.jsp.view_jsp._jspService(view_jsp.java:183)
 org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:71)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:477)
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:385)
 org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
 com.firehunter.adminconsole_core.NimsofCsrfPreventionFilter.doFilter(NimsofCsrfPreventionFilter.java:195)
 org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:126)
 com.firehunter.adminconsole.config.ResponseHeaderFilter.doFilter(ResponseHeaderFilter.java:111)
 com.firehunter.adminconsole.filter.XSSParamFilter.doFilter(XSSParamFilter.java:107)

Environment

Release : 20.3

Component : UNIFIED INFRASTRUCTURE MGMT

Resolution

Applying the following steps solves this issue:

• Take the system to the state where adminconsole is not working
• In IM deactivate the wasp probe
• Go to the product installation folder of the UIM server
• Open <Nimsoft installed location>\probes\service\wasp\webapps\adminconsoleapp\WEB-INF\lib
• Find the jar file wasp_api-8.4.0-K
• Take a backup of this file in another location (NOT in the same folder) 
• Delete the file from the original location
• Delete work folder from the location <Nimsoft installed location>\probes\service\wasp\
• Activate wasp probe in IM
• Delete browser cache and run the adminconsole app in the browser