CABI portal stopped responding with HTTP status 404 error after a configuration change

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After doing a modification on $UIM_HOME/nimsoft/probes/service/wasp/webapps/cabijs/WEB-INF/applicationContext.xml (suggested in Article ID 221896) the CABI page is no longer accessible.

The CABI portal is down with the following error showing in the cabi.log:

Sep 08 23:52:23:840 [UserSynchronizationThread, cabi] JasperUserUtility:login(): URL attempted :https://<cabi_ip_address>:<cabi_port>/cabijs/login.html 
Sep 08 23:52:23:840 [UserSynchronizationThread, cabi] JasperUserUtility:login(): Response code :404 
Sep 08 23:52:23:840 [UserSynchronizationThread, cabi] UimToJasperUserSync(): I can't log into CABI I've tried all the known passwords. I give up...

wasp.log (CABI robot) show next error message:

Sep 09 10:59:19:950 INFO  [Catalina-utility-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/]] No Spring WebApplicationInitializer types detected on classpath
Sep 09 10:59:27:519 ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/cabijs]] listenerStart() Exception sending context initialized event to listener instance of class [org.springframework.web.context.ContextLoaderListener]
Sep 09 10:59:27:520 ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/cabijs]] org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'org.springframework.transaction.config.internalTransactionalEventListenerFactory' defined in null: Cannot register bean definition [Root bean: class [org.springframework.transaction.event.TransactionalEventListenerFactory]; scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null] for bean 'org.springframework.transaction.config.internalTransactionalEventListenerFactory': There is already [Root bean: class [org.springframework.transaction.event.TransactionalEventListenerFactory]; scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null] bound.

Before making the change, the applicationContext.xml file was backed up, and after CABI failed to start,  the backed up version was used to try to fix the problem. However, it is not working.

Environment

Release : 20.4

Component : UIM - CABI

Cause

Problem started after modifying C:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\jasperserver-pro\WEB-INF\applicationContext-audit file, and  saving a copy of the file  to the same folder as the original.

 

 

Resolution

Deleting the "applicationContext-audit - Copy.xml" in the location listed below.

C:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\jasperserver-pro\WEB-INF\applicationContext-audit - Copy.xml

and following the next  steps at the CABI robot:

1.  Deactivate the wasp probe
2.  Deactivate the cabi probe
3.  Delete the following directory and its contents on the CABI robot:

- <installPath>\Nimsoft\probes\service\wasp\work

4.  Activate the wasp probe
5.  When the PID and port columns for the wasp probe both have values, activate the cabi probe
6.  When the PID and port columns for the cabi probe have values, clear the browser cache from the beginning of time, then verify that the CABI server URL can be accessed directly from the browser: https://<cabi_ip_address_or_fqdn>:<cabi_port>/cabijs/login.html