0 Replies Latest reply on Nov 16, 2019 4:47 PM by 3573277

    ORDS memory leak ?

    3573277

      Nov 16, 2019 10:59:37 AM org.apache.coyote.AbstractProtocol pause

      INFO: Pausing ProtocolHandler ["http-bio-8082"]

      Nov 16, 2019 10:59:37 AM org.apache.coyote.AbstractProtocol pause

      INFO: Pausing ProtocolHandler ["ajp-bio-8009"]

      Nov 16, 2019 10:59:37 AM org.apache.catalina.core.StandardService stopInternal

      INFO: Stopping service Catalina

      Nov 16, 2019 10:59:37 AM

      INFO: Destroyed pool : |apex|pu|-2019-11-16T15:59:23.437Z

      Nov 16, 2019 10:59:37 AM

      INFO: Destroyed pool : |prodes|pu|-2019-11-16T15:59:26.505Z

      Nov 16, 2019 10:59:37 AM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc

      SEVERE: The web application [/ords] registered the JDBC driver [oracle.jdbc.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

      Nov 16, 2019 10:59:37 AM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads

      SEVERE: The web application [/ords] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.

      Nov 16, 2019 10:59:37 AM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads

      SEVERE: The web application [/ords] appears to have started a thread named [UCP Clock] but has failed to stop it. This is very likely to create a memory leak.

      Nov 16, 2019 10:59:37 AM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads

      SEVERE: The web application [/ords] appears to have started a thread named [oracle.ucp.actors.InterruptableActor-control] but has failed to stop it. This is very likely to create a memory leak.

      Nov 16, 2019 10:59:37 AM org.apache.coyote.AbstractProtocol stop

      INFO: Stopping ProtocolHandler ["http-bio-8082"]

      Nov 16, 2019 10:59:37 AM org.apache.coyote.AbstractProtocol destroy

      INFO: Destroying ProtocolHandler ["http-bio-8082"]

      Nov 16, 2019 10:59:37 AM org.apache.coyote.AbstractProtocol stop

      INFO: Stopping ProtocolHandler ["ajp-bio-8009"]

      Nov 16, 2019 10:59:37 AM org.apache.coyote.AbstractProtocol destroy

      INFO: Destroying ProtocolHandler ["ajp-bio-8009"]

       

      ** the above was during the start-up of tomcat

       

       

      On constant load of around 30 threads and more than 2,000,000 transaction+ testing, all threads gets kiled with 500 or 503 error

      Exception in thread "Thread-26" java.lang.RuntimeException: Failed : HTTP error code : 503

              at com.cognizant.ehdl.provider.main.ORDSServices.run(ORDSServices.java:157)

      Exception in thread "Thread-28" java.lang.RuntimeException: Failed : HTTP error code : 500

              at com.cognizant.ehdl.provider.main.ORDSServices.run(ORDSServices.java:157)

      Exception in thread "Thread-17" java.lang.RuntimeException: Failed : HTTP error code : 503

              at com.cognizant.ehdl.provider.main.ORDSServices.run(ORDSServices.java:157)

      Exception in thread "Thread-0" java.lang.RuntimeException: Failed : HTTP error code : 500

              at com.cognizant.ehdl.provider.main.ORDSServices.run(ORDSServices.java:157)

      Exception in thread "Thread-13" java.lang.RuntimeException: Failed : HTTP error code : 500

              at com.cognizant.ehdl.provider.main.ORDSServices.run(ORDSServices.java:157)

      Exception in thread "Thread-16" java.lang.RuntimeException: Failed : HTTP error code : 503

              at com.cognizant.ehdl.provider.main.ORDSServices.run(ORDSServices.java:157)

       

      The end point is same and average response time started with 41 and slowly increased to 50 and then it collapsed. Total of 1,695,931 was executed before it collapsed.

       

      Any thoughts