OneView Monitor port 44450 still open after Policy Server down

book

Article ID: 129574

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) AXIOMATICS POLICY SERVER CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On

Issue/Introduction

We're running the script start-all and stop-all script and we don't
see the OneView Monitor starting nor stopping.

Once we run stop-all script, after the Policy Server stopped
completely, we still see the ports 44449 and 44450 open.

How can we fix this ?

Environment

Release: MSPSSO99000-12.8-Single Sign-On-for Business Users-MSP
Component:

Resolution

At first glance, the OneView Monitor has a component that runs on
Tomcat Server, which communicate with the Policy Server on ports (by
default 44450). And when you start the Policy Server with the out of
the box start-all script, it start the Policy Server and the OneView
Monitor client that will give the data to the OneView Monitor
application that runs on Tomcat.

I've tried this scenario on my lab : 

  - Tomcat down; 
  - Start the Policy Server with start-all script; 
  - I see the ports 44449 and 44450 open on tcp; 
  - Stop the Policy Server with stop-all script; 
  - I see the ports 44449 and 44450 getting closed;