Tomcat with a new configuration is throwing a 'failed to query error' while connecting

book

Article ID: 221802

calendar_today

Updated On:

Products

DX Infrastructure Management CA Unified Infrastructure Management for z Systems CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM) NIMSOFT PROBES

Issue/Introduction

We are getting the error below while connecting to the tomcat probe from the local host.

Host Response

Failed to query the host <ip address >

The reason for this could be one of many, please check:

- the hostname or ip address is illegal or wrong
- the port number is wrong
- the handlerclass is wrong
Aug 16 17:22:23:497 [DC#0, com.nimsoft.nimbus.probe.application.extractbase.TimerCach] TimerCach: Get(connect);class com.nimsoft.nimbus.NimException
Aug 16 17:22:23:498 [DC#0, com.nimsoft.nimbus.probe.application.extractbase.Extract] Unable to connect : 150.x.xx.xxx
Aug 16 17:22:23:498 [DC#0, com.nimsoft.nimbus.probe.application.extractbase.Extract] (1500) , Connection is down (already reported for [150.x.xx.xxx]:9000)
 at com.nimsoft.nimbus.probe.application.jsr160.ConnectionHolder.connect(ConnectionHolder.java:317) 
 at com.nimsoft.nimbus.probe.application.jsr160.Handler.connect(Handler.java:79) 
 at com.nimsoft.nimbus.probe.application.extractbase.Extract.connect(Extract.java:4663) 
 at com.nimsoft.nimbus.probe.application.extractbase.Extract.reconnect(Extract.java:4772) 
 at com.nimsoft.nimbus.probe.application.extractbase.Extract.processResource(Extract.java:1943) 
 at com.nimsoft.nimbus.probe.application.extractbase.Extract.preSet(Extract.java:1430) 
 at com.nimsoft.nimbus.probe.application.extractbase.Extract$InitialCheckThreadOne.run(Extract.java:4995) 
Aug 16 17:22:23:498 [DC#0, com.nimsoft.nimbus.probe.application.extractbase.Resource] The resource Alarm (D, severity=5, message==The resource 150.x.xx.xxx is not responding, subsystem=1.1.14.4.1, suppressionid=150.1.50.203, source=150.1.50.203) is already in the bulk send queue
...
Aug 16 17:23:08:494 [Janitor, com.nimsoft.nimbus.probe.application.extractbase.Janitor] heap memory is 243712memorylimitlow is 0memorylimithigh is 0
Aug 16 17:23:08:495 [Janitor, com.nimsoft.nimbus.probe.application.extractbase.Janitor] memorylimit = 100000KB, heap = 243712KB, used = 34569KB 
Aug 16 17:23:08:495 [Janitor, com.nimsoft.nimbus.ci.RemoteDevice] Remote dev created for hostname 'null', probe 'tomcat' 
Aug 16 17:23:08:497 [Janitor, com.nimsoft.nimbus.probe.application.extractbase.Janitor] JVM heap size exceeds the memory limit (243712KB > 100000KB); Trying a restart

Cause

- default memory limit setting value in tomcat probe

Environment

Release : 20.3

Component : UIM - TOMCAT 1.30

Resolution

  1. Select the tomcat probe and open it via holding own the SHIFT-key and then Rt-click and choose Raw Configure.
  2. Navigate to the janitor section and select the memorylimit key.
  3. Edit the key. Since the error displayed the value of -> 243712KB, try setting the internal limit to 300000.

4. Deactivate the tomcat probe.
5. In the meantime, acknowledge the tomcat alarm.
6. Wait until the port and PID disappear.
7. Activate the probe.
8. Check the log again.

Additional Information

Critical alarm: The probe internal used memory nnnnnnKB (x%) is >= 100.0% of 124000KB