search cancel

wasp is kept restarting on core failover hub


Article ID: 190698


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


wasp is kept restarting on core failover hub. It works just fine on Core Primary hub.

UIM : 9.20
wasp: 9.20
Robot: 9.20Shf13
HUB: 9.20Shf11

OS: Windows 2012 X64 Bit Standard 

This was upgraded from 8.5.1 to 9.0.2 to 9.2.0

This was recently upgraded.

from the logs I can see the following error:

mei 12 12:02:01:278 ERROR [main, org.apache.catalina.util.LifecycleBase] handleSubClassException() Failed to initialize component [Connector[HTTP/1.1-8443]]
mei 12 12:02:01:279 ERROR [main, org.apache.catalina.util.LifecycleBase] org.apache.catalina.LifecycleException: Protocol handler initialization failed
 at org.apache.catalina.connector.Connector.initInternal(
 at org.apache.catalina.util.LifecycleBase.init(
 at org.apache.catalina.core.StandardService.initInternal(
 at org.apache.catalina.util.LifecycleBase.init(
 at org.apache.catalina.core.StandardServer.initInternal(
 at org.apache.catalina.util.LifecycleBase.init(
 at org.apache.catalina.util.LifecycleBase.start(
 at org.apache.catalina.startup.Tomcat.start(
 at com.nimsoft.nimbus.probe.service.wasp.Probe.doit(
 at com.nimsoft.nimbus.probe.service.wasp.Probe.main(
Caused by: java.lang.IllegalArgumentException: Alias name [wasp] does not identify a key entry
 at org.apache.coyote.AbstractProtocol.init(
 at org.apache.coyote.http11.AbstractHttp11Protocol.init(
 at org.apache.catalina.connector.Connector.initInternal(
 ... 9 more
Caused by: Alias name [wasp] does not identify a key entry
 ... 16 more


Release : 9.2.0

Component : UIM - UMP_USM


Redeploy the adminconsole, wasp and mpse probes to make it work.