Uploaded image for project: 'Data Collection, Analytics, and Events'
  1. Data Collection, Analytics, and Events
  2. DCAEGEN2-1615

PM-Mapper creates too many ssl_client processes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • El Alto Release
    • Dublin Release
    • None
    • 3 Node deployment of ONAP installed on 10 June 2019

      During Performance testing of BulkPMe2e it was observed that Pm-Mapper has too many ssl_ client ( aprox 2646 process ) process running.. that is causing IO exception error..

      /var/log/ONAP/dcaegen2/services/pm-mapper $
      /var/log/ONAP/dcaegen2/services/pm-mapper $ ps
      PID USER TIME COMMAND
      1 pm-mappe 2h47 /usr/bin/java -jar /opt/app/pm-mapper/pm-mapper.jar
      7 pm-mappe 0:02 sh etc/reconfigure.sh
      84 pm-mappe 0:00 [ssl_client]
      98 pm-mappe 0:00 [ssl_client]
      112 pm-mappe 0:00 [ssl_client]
      126 pm-mappe 0:00 [ssl_client]
      140 pm-mappe 0:00 [ssl_client]
      154 pm-mappe 0:00 [ssl_client]
      168 pm-mappe 0:00 [ssl_client]
      182 pm-mappe 0:00 [ssl_client]
      196 pm-mappe 0:00 [ssl_client]
      210 pm-mappe 0:00 [ssl_client]
      224 pm-mappe 0:00 [ssl_client]

      2019-06-12T11:29:45.862Z XNIO-1 I/O-9 DEBUG io.undertow.request UT005013: An IOException occurred java.nio.channels.ClosedChannelException: null\n\tat io.undertow.protocols.ssl.SslConduit.doWrap(SslConduit.java:876)\n\tat io.undertow.protocols.ssl.SslConduit.doHandshake(SslConduit.java:649)\n\tat io.undertow.protocols.ssl.SslConduit.access$900(SslConduit.java:63)\n\tat io.undertow.protocols.ssl.SslConduit$SslReadReadyHandler.readReady(SslConduit.java:1136)\n\tat org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88)\n\tat org.xnio.nio.WorkerThread.run(WorkerThread.java:561)\n
      2019-06-12T11:30:00.938Z XNIO-1 I/O-15 INFO org.onap.dcaegen2.services.pmmapper.healthcheck.HealthCheckHandler InstanceUUID=b6f7ab32-d2e3-4263-abbe-05c9cd92a9e0, RequestID=e047d8c6-2737-4681-9b05-09b0922af6b4, ServiceName=/healthcheck, InvocationID=680014e7-1720-42b7-87ff-41ec4797f930, InvokeTimestamp=2019-06-12T11:30:00.938Z, PartnerName=, ClientIPAddress=/10.42.0.1, ServerFQDN=10.42.63.56 ENTRY
      2019-06-12T11:30:00.939Z XNIO-1 I/O-15 INFO org.onap.dcaegen2.services.pmmapper.healthcheck.HealthCheckHandler ResponseCode=, InstanceUUID=b6f7ab32-d2e3-4263-abbe-05c9cd92a9e0, RequestID=e047d8c6-2737-4681-9b05-09b0922af6b4, ServiceName=/healthcheck, ResponseDescription=, InvocationID=680014e7-1720-42b7-87ff-41ec4797f930, Severity=, InvokeTimestamp=2019-06-12T11:30:00.938Z, PartnerName=, ClientIPAddress=/10.42.0.1, ServerFQDN=10.42.63.56, StatusCode=EXIT
      2019-06-12T11:30:00.940Z XNIO-1 I/O-15 DEBUG io.undertow.request UT005013: An IOException occurred java.nio.channels.ClosedChannelException: null\n\tat io.undertow.protocols.ssl.SslConduit.doWrap(SslConduit.java:876)\n\tat io.undertow.protocols.ssl.SslConduit.doHandshake(SslConduit.java:649)\n\tat io.undertow.protocols.ssl.SslConduit.access$900(SslConduit.java:63)\n\tat io.undertow.protocols.ssl.SslConduit$SslReadReadyHandler.readReady(SslConduit.java:1136)\n\tat io.undertow.protocols.ssl.SslConduit$1.run(SslConduit.java:168)\n\tat org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:582)\n\tat org.xnio.nio.WorkerThread.run(WorkerThread.java:466)\n
      2019-06-12T11:30:15.828Z XNIO-1 I/O-13 INFO org.onap.dcaegen2.services.pmmapper.healthcheck.HealthCheckHandler InstanceUUID=b6f7ab32-d2e3-4263-abbe-05c9cd92a9e0, RequestID=627b78a7-66ea-4a91-a9b5-da863d7463c6, ServiceName=/healthcheck, InvocationID=5f62b75d-2e43-48bb-ad24-f44d16b45087, InvokeTimestamp=2019-06-12T11:30:15.828Z, PartnerName=, ClientIPAddress=/10.42.0.1, ServerFQDN=10.42.63.56 ENTRY
      2019-06-12T11:30:15.831Z XNIO-1 I/O-13 INFO org.onap.dcaegen2.services.pmmapper.healthcheck.HealthCheckHandler ResponseCode=, InstanceUUID=b6f7ab32-d2e3-4263-abbe-05c9cd92a9e0, RequestID=627b78a7-66ea-4a91-a9b5-da863d7463c6, ServiceName=/healthcheck, ResponseDescription=, InvocationID=5f62b75d-2e43-48bb-ad24-f44d16b45087, Severity=, InvokeTimestamp=2019-06-12T11:30:15.828Z, PartnerName=, ClientIPAddress=/10.42.0.1, ServerFQDN=10.42.63.56, StatusCode=EXIT

       

      This is causing DR to process files slower than expected

            liamburke liamburke
            liamburke liamburke
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: