Tomcat Server Discovery Horizontal v Top Down

[RobertB1]

Hi all!

I'm working on a Service Mapping Pilot currently, whilst wrapping up the Discovery Project. 

I'm having issues discovering Tomcat servers via top down discovery, despite them being discovered via horizontal fine. 

The failure occurs at the first stage of the 'http and AJP identification'. 

My thought currently is, horizontal discovery uses the combination of the IP and the PID, whereas top-down, uses the HTTPs end point (IP and port). Is this my issue? I'm also aware there's a lot of noise in the logs, and issue could be somewhere else. As, I would have thought the tool would be able to resolve this error.  

I've done a test from the mid server host, and can't reach the host server via the port in question. And the error message below confirms this also. 

So I suppose my question is, if I'm on the correct track, do we need to create firewall rules for all ports used by in-scope application across the network for Service Mapping? 

Thanks in advance!

The error message is see in the logs is "Failed to find process on port. No process detected on host, **.**.**.**, that is listening on port ****

ecc queue

2024-07-11 15:04:49 DEBUG (Worker-Interactive:PatternDebuggerProbe-1993d1c6c3538e9075dbec3bb00131b4) [DiscoveryCommandDomainManagerImpl:823] (123)DiscoveryCommandDomainManagerImpl - Checking if host **.**.**.** is listening on TCP port *****
2024-07-11 15:04:49 DEBUG (Worker-Interactive:PatternDebuggerProbe-1993d1c6c3538e9075dbec3bb00131b4) [PortScannerProvider:51] (123)PortScannerProvider - Starting port scan on host **.**.**.**. ports: *****
2024-07-11 15:04:50 DEBUG (Worker-Interactive:PatternDebuggerProbe-1993d1c6c3538e9075dbec3bb00131b4) [PortScannerProvider:65] (123)PortScannerProvider - Port scan completed on host **.**.**.**:{*****=closed}

[Community Alums]

Hi Robert, 

Looks like servicenow discovery couldn't find any active process on that port number. You can verify if the tomcat process is running on the server by reffering to the CI Server Record and scroll down to the Running process tab. Look for PID, Port and name path as shown in the below screenshot. Validate, if the tomcat process is running.

Regards, 

Srinija

[RobertB1]

Hi Srinija, 

As mentioned, horizontal discovery works as expected. Tomcat is running and listening on the port in question.  

Thanks 

Rob