Clarity

Expand all | Collapse all

Performance issue in one of the new server

  • 1.  Performance issue in one of the new server

    Posted Dec 22, 2016 08:35 AM

    Hello,

    We are building a new server with CA PPM 15.1 with windows server 2012 and RAM of 24 GB. When we tried to start the APP service it is taking 5 mins time to start the APP service which is strange when compared to other servers is starting with in 1 minute. Application performance is also so lagging in every step.

     

    There is no problem in database(MS SQL) side. when we have tried to connect this database from other application servers CA PPM is working fine. Can anyone suggest us if there is any adjustments needs to be made in NSA for application to improve performance?

     

    2016/12/21 08:34:51.422 | Licensed to CA, Inc. for CA PPM Application Server
    2016/12/21 08:34:51.422 |
    2016/12/21 08:34:52.966 | Launching a JVM...
    2016/12/21 08:34:53.189 | WrapperManager: Initializing...
    2016/12/21 08:34:54.064 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.064 | INFO: Server version: CA PPM
    2016/12/21 08:34:54.080 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.080 | INFO: Server built: Mar 18 2016 20:31:49 UTC
    2016/12/21 08:34:54.096 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.096 | INFO: Server number: 8.0.33.0
    2016/12/21 08:34:54.111 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.111 | INFO: OS Name: Windows Server 2012
    2016/12/21 08:34:54.127 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.127 | INFO: OS Version: 6.2
    2016/12/21 08:34:54.127 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.142 | INFO: Architecture: amd64
    2016/12/21 08:34:54.142 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.158 | INFO: Java Home: D:\Java\jdk1.8.0_112\jre
    2016/12/21 08:34:54.158 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.174 | INFO: JVM Version: 1.8.0_112-b15
    2016/12/21 08:34:54.174 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.189 | INFO: JVM Vendor: Oracle Corporation
    2016/12/21 08:34:54.189 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.205 | INFO: CATALINA_BASE: D:\niku\clarity\tomcat-app-deploy
    2016/12/21 08:34:54.220 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.220 | INFO: CATALINA_HOME: D:\niku\tomcat\apache-tomcat-8.0.33
    2016/12/21 08:34:54.236 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.236 | INFO: Command line argument: -Dcom.niku.union.instanceId=app
    2016/12/21 08:34:54.252 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.252 | INFO: Command line argument: -Dcom.niku.union.serviceId=app@usa0300vm2248:9091
    2016/12/21 08:34:54.267 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.267 | INFO: Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
    2016/12/21 08:34:54.283 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.283 | INFO: Command line argument: -Djava.endorsed.dirs=D:\\niku\\tomcat\\apache-tomcat-8.0.33/common/endorsed
    2016/12/21 08:34:54.298 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.314 | INFO: Command line argument: -Dcatalina.base=D:\\niku\\clarity\\tomcat-app-deploy
    2016/12/21 08:34:54.314 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.330 | INFO: Command line argument: -Dcatalina.home=D:\\niku\\tomcat\\apache-tomcat-8.0.33
    2016/12/21 08:34:54.330 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.345 | INFO: Command line argument: -Djava.io.tmpdir=D:\\niku\\clarity\\tomcat-app-deploy/temp
    2016/12/21 08:34:54.345 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.361 | INFO: Command line argument: -Dfile.encoding=UTF-8
    2016/12/21 08:34:54.361 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.361 | INFO: Command line argument: -Djava.awt.headless=true
    2016/12/21 08:34:54.361 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.376 | INFO: Command line argument: -Djava.net.preferIPv4Stack=true
    2016/12/21 08:34:54.376 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.392 | INFO: Command line argument: -Xms3072m
    2016/12/21 08:34:54.392 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.392 | INFO: Command line argument: -Xmx3072m
    2016/12/21 08:34:54.392 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.408 | INFO: Command line argument: -XX:-UseGCOverheadLimit
    2016/12/21 08:34:54.408 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.408 | INFO: Command line argument: -DforceMemorySettings=false
    2016/12/21 08:34:54.408 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.423 | INFO: Command line argument: -XX:MaxMetaspaceSize=192m
    2016/12/21 08:34:54.423 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.423 | INFO: Command line argument: -Duser.language=en
    2016/12/21 08:34:54.423 | Dec 21, 2016 8:34:53 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.439 | INFO: Command line argument: -Djava.library.path=D:\\niku\\clarity\\bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;D:\Java\jdk1.8.0_102\bin;D:\niku\clarity\bin;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\BMCSOF~1\Patrol3\bin;D:\Java\jdk1.8.0_112\bin
    2016/12/21 08:34:54.439 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.439 | INFO: Command line argument: -Dwrapper.key=8xMBRAxX4tRJAyENIc58xXKBuj6exCVY
    2016/12/21 08:34:54.454 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.454 | INFO: Command line argument: -Dwrapper.port=32000
    2016/12/21 08:34:54.454 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.454 | INFO: Command line argument: -Dwrapper.jvm.port.min=31000
    2016/12/21 08:34:54.454 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.470 | INFO: Command line argument: -Dwrapper.jvm.port.max=31999
    2016/12/21 08:34:54.470 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.470 | INFO: Command line argument: -Dwrapper.pid=76
    2016/12/21 08:34:54.486 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.486 | INFO: Command line argument: -Dwrapper.version=3.5.17-pro
    2016/12/21 08:34:54.486 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.486 | INFO: Command line argument: -Dwrapper.native_library=wrapper
    2016/12/21 08:34:54.486 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.501 | INFO: Command line argument: -Dwrapper.arch=x86
    2016/12/21 08:34:54.501 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.501 | INFO: Command line argument: -Dwrapper.service=TRUE
    2016/12/21 08:34:54.501 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.517 | INFO: Command line argument: -Dwrapper.cpu.timeout=600
    2016/12/21 08:34:54.517 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.517 | INFO: Command line argument: -Dwrapper.jvmid=1
    2016/12/21 08:34:54.517 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.VersionLoggerListener log
    2016/12/21 08:34:54.532 | INFO: Command line argument: -Dwrapper.lang.domain=wrapper
    2016/12/21 08:34:54.532 | Dec 21, 2016 8:34:54 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
    2016/12/21 08:34:54.532 | INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: D:\\niku\\clarity\\bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;D:\Java\jdk1.8.0_102\bin;D:\niku\clarity\bin;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\BMCSOF~1\Patrol3\bin;D:\Java\jdk1.8.0_112\bin
    2016/12/21 08:34:54.657 | Dec 21, 2016 8:34:54 AM org.apache.coyote.AbstractProtocol init
    2016/12/21 08:34:54.657 | INFO: Initializing ProtocolHandler ["http-nio-127.0.0.1-8800"]
    2016/12/21 08:34:54.876 | Dec 21, 2016 8:34:54 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
    2016/12/21 08:34:54.876 | INFO: Using a shared selector for servlet write/read
    2016/12/21 08:34:54.876 | Dec 21, 2016 8:34:54 AM org.apache.coyote.AbstractProtocol init
    2016/12/21 08:34:54.891 | INFO: Initializing ProtocolHandler ["ajp-nio-127.0.0.1-8019"]
    2016/12/21 08:34:54.891 | Dec 21, 2016 8:34:54 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
    2016/12/21 08:34:54.891 | INFO: Using a shared selector for servlet write/read
    2016/12/21 08:34:54.891 | Dec 21, 2016 8:34:54 AM org.apache.catalina.startup.Catalina load
    2016/12/21 08:34:54.907 | INFO: Initialization processed in 1262 ms
    2016/12/21 08:34:54.907 | Dec 21, 2016 8:34:54 AM org.apache.catalina.core.StandardService startInternal
    2016/12/21 08:34:54.938 | INFO: Starting service Catalina
    2016/12/21 08:34:54.938 | Dec 21, 2016 8:34:54 AM org.apache.catalina.core.StandardEngine startInternal
    2016/12/21 08:34:54.938 | INFO: Starting Servlet Engine: CA PPM
    2016/12/21 08:35:08.258 | Dec 21, 2016 8:35:08 AM org.apache.jasper.servlet.TldScanner scanJars
    2016/12/21 08:35:08.336 | INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
    2016/12/21 08:35:22.203 | Dec 21, 2016 8:35:22 AM org.apache.jasper.servlet.TldScanner scanJars
    2016/12/21 08:35:22.453 | INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
    2016/12/21 08:35:41.070 | Dec 21, 2016 8:35:41 AM org.apache.jasper.servlet.TldScanner scanJars
    2016/12/21 08:35:41.289 | INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
    2016/12/21 08:35:57.469 | Dec 21, 2016 8:35:57 AM org.apache.jasper.servlet.TldScanner scanJars
    2016/12/21 08:35:57.797 | INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
    2016/12/21 08:35:57.859 | Attempting to load ESAPI.properties via file I/O.
    2016/12/21 08:35:57.859 | Attempting to load ESAPI.properties as resource file via file I/O.
    2016/12/21 08:35:57.859 | Found in 'org.owasp.esapi.resources' directory: D:\niku\clarity\webroot\ESAPI.properties
    2016/12/21 08:35:57.859 | Loaded 'ESAPI.properties' properties file
    2016/12/21 08:35:57.859 | Attempting to load validation.properties via file I/O.
    2016/12/21 08:35:57.875 | Attempting to load validation.properties as resource file via file I/O.
    2016/12/21 08:35:57.875 | Found in 'org.owasp.esapi.resources' directory: D:\niku\clarity\webroot\validation.properties
    2016/12/21 08:35:57.875 | Loaded 'validation.properties' properties file
    2016/12/21 08:35:57.875 | Reset resource directory to: D:\niku\clarity\webroot\
    2016/12/21 08:35:57.891 | Attempting to load ESAPI.properties via file I/O.
    2016/12/21 08:35:57.891 | Attempting to load ESAPI.properties as resource file via file I/O.
    2016/12/21 08:35:57.906 | Found in 'org.owasp.esapi.resources' directory: D:\niku\clarity\webroot\ESAPI.properties
    2016/12/21 08:35:57.906 | Loaded 'ESAPI.properties' properties file
    2016/12/21 08:35:57.906 | Attempting to load validation.properties via file I/O.
    2016/12/21 08:35:57.922 | Attempting to load validation.properties as resource file via file I/O.
    2016/12/21 08:35:57.922 | Found in 'org.owasp.esapi.resources' directory: D:\niku\clarity\webroot\validation.properties
    2016/12/21 08:35:57.937 | Loaded 'validation.properties' properties file
    2016/12/21 08:35:57.937 | Dec 21, 2016 8:35:57 AM org.apache.catalina.core.ApplicationContext log
    2016/12/21 08:35:57.953 | INFO: ODataServlet: [Restlet] ServerServlet: component class is null
    2016/12/21 08:35:58.718 | Clarity 15.1.0.149 initializing...
    2016/12/21 08:36:00.917 |
    2016/12/21 08:36:00.917 | -------------------------------------------------------------------
    2016/12/21 08:36:00.917 | GMS: address=usa0300vm2248-51984, cluster=CLRTY, physical address=13.129.25.44:56729
    2016/12/21 08:36:00.917 | -------------------------------------------------------------------
    2016/12/21 08:41:16.210 |
    2016/12/21 08:41:16.210 | -------------------------------------------------------------------
    2016/12/21 08:41:16.210 | GMS: address=usa0300vm2248-30823, cluster=CLRTY-SA, physical address=13.129.25.44:64977
    2016/12/21 08:41:16.225 | -------------------------------------------------------------------
    2016/12/21 08:41:16.366 | Clarity 15.1.0.149 ready.
    2016/12/21 08:41:16.506 | Dec 21, 2016 8:41:16 AM org.apache.catalina.startup.HostConfig deployWAR
    2016/12/21 08:41:16.506 | INFO: Deploying web application archive D:\niku\clarity\tomcat-app-deploy\webapps\pm.war
    2016/12/21 08:41:29.891 | Dec 21, 2016 8:41:29 AM org.apache.jasper.servlet.TldScanner scanJars
    2016/12/21 08:41:29.891 | INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
    2016/12/21 08:41:29.907 | Dec 21, 2016 8:41:29 AM org.apache.catalina.startup.HostConfig deployWAR
    2016/12/21 08:41:29.907 | INFO: Deployment of web application archive D:\niku\clarity\tomcat-app-deploy\webapps\pm.war has finished in 13,526 ms
    2016/12/21 08:41:29.922 | Dec 21, 2016 8:41:29 AM org.apache.coyote.AbstractProtocol start
    2016/12/21 08:41:29.938 | INFO: Starting ProtocolHandler ["http-nio-127.0.0.1-8800"]
    2016/12/21 08:41:29.938 | Dec 21, 2016 8:41:29 AM org.apache.coyote.AbstractProtocol start
    2016/12/21 08:41:29.938 | INFO: Starting ProtocolHandler ["ajp-nio-127.0.0.1-8019"]
    2016/12/21 08:41:29.954 | Dec 21, 2016 8:41:29 AM org.apache.catalina.startup.Catalina start
    2016/12/21 08:41:29.954 | INFO: Server startup in 395023 ms
    2016/12/21 08:47:08.803 | Dec 21, 2016 8:47:08 AM org.apache.catalina.core.ApplicationContext log
    2016/12/21 08:47:08.803 | INFO: ODataServlet: Starting ODataServlet::createServer
    2016/12/21 08:47:09.349 | Dec 21, 2016 8:47:09 AM com.ca.platform.osf.object.odata.ODataJaxRsApp initClarityODataApp
    2016/12/21 08:47:09.349 | INFO: Starting ODataJaxRsApp
    2016/12/21 08:47:09.365 | Dec 21, 2016 8:47:09 AM com.ca.platform.osf.object.odata.ODataJaxRsApp initClarityODataApp
    2016/12/21 08:47:09.365 | INFO: Finished ODataJaxRsApp
    2016/12/21 08:47:09.365 | Dec 21, 2016 8:47:09 AM org.apache.catalina.core.ApplicationContext log
    2016/12/21 08:47:09.381 | INFO: ODataServlet: [Restlet] Attaching application: com.ca.platform.osf.object.odata.ODataJaxRsApp@4250d2b to URI: /niku/odata
    2016/12/21 08:47:09.396 | Dec 21, 2016 8:47:09 AM org.apache.catalina.core.ApplicationContext log
    2016/12/21 08:47:09.413 | INFO: ODataServlet: Finish ODataServlet::createServer



  • 2.  Re: Performance issue in one of the new server

    Posted Dec 22, 2016 09:06 AM

    Hi

     

    How much JVM Xmx have you assigned to app service?



  • 3.  Re: Performance issue in one of the new server

    Posted Dec 22, 2016 09:12 AM

    <applicationServerInstance id="app" serviceName="CA Clarity PPM App Server" rmiPort="23791" jvmParameters="-Xms3072m -Xmx3072m -XX:-UseGCOverheadLimit -DforceMemorySettings=false -XX:MaxMetaspaceSize=192m" maxThreads="200" programParameters="" distributed="true" cacheDistributedSession="false" runJobScheduler="false" useSSO="false" maxConcurrentJobs="10" runProcessEngine="false" messageTimeToLive="120" messageReceiverInterval="5" exceptionRunInterval="normal" serviceUser="" servicePassword="" autoStartService="true">
    <war context="pm" name="ppm-ux" enable="true"/>
    </applicationServerInstance>



  • 4.  Re: Performance issue in one of the new server

    Posted Dec 22, 2016 09:27 AM

    Why do you limit to XX:MaxMetaspaceSize=192m?

     

     

    Try to remove it and restart app.

     



  • 5.  Re: Performance issue in one of the new server

    Posted Dec 22, 2016 11:18 AM

    No change in application performance:

     

    2016/12/22 10:00:57.215 | Loaded 'validation.properties' properties file
    2016/12/22 10:00:57.215 | Dec 22, 2016 10:00:57 AM org.apache.catalina.core.ApplicationContext log
    2016/12/22 10:00:57.215 | INFO: ODataServlet: [Restlet] ServerServlet: component class is null
    2016/12/22 10:00:58.105 | Clarity 15.1.0.149 initializing...
    2016/12/22 10:01:00.413 |
    2016/12/22 10:01:00.413 | -------------------------------------------------------------------
    2016/12/22 10:01:00.413 | GMS: address=usa0300vm2248-62040, cluster=CLRTY, physical address=13.129.25.44:54160
    2016/12/22 10:01:00.429 | -------------------------------------------------------------------
    2016/12/22 10:06:03.590 |
    2016/12/22 10:06:03.590 | -------------------------------------------------------------------
    2016/12/22 10:06:03.590 | GMS: address=usa0300vm2248-17097, cluster=CLRTY-SA, physical address=13.129.25.44:54919
    2016/12/22 10:06:03.606 | -------------------------------------------------------------------
    2016/12/22 10:06:03.731 | Clarity 15.1.0.149 ready.
    2016/12/22 10:06:03.746 | Dec 22, 2016 10:06:03 AM org.apache.catalina.startup.HostConfig deployWAR
    2016/12/22 10:06:03.746 | INFO: Deploying web application archive D:\niku\clarity\tomcat-app3-deploy\webapps\pm.war
    2016/12/22 10:06:15.868 | Dec 22, 2016 10:06:15 AM org.apache.jasper.servlet.TldScanner scanJars
    2016/12/22 10:06:15.868 | INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
    2016/12/22 10:06:15.884 | Dec 22, 2016 10:06:15 AM org.apache.catalina.startup.HostConfig deployWAR
    2016/12/22 10:06:15.899 | INFO: Deployment of web application archive D:\niku\clarity\tomcat-app3-deploy\webapps\pm.war has finished in 12,199 ms
    2016/12/22 10:06:15.915 | Dec 22, 2016 10:06:15 AM org.apache.coyote.AbstractProtocol start
    2016/12/22 10:06:15.915 | INFO: Starting ProtocolHandler ["http-nio-8140"]
    2016/12/22 10:06:15.930 | Dec 22, 2016 10:06:15 AM org.apache.coyote.AbstractProtocol start
    2016/12/22 10:06:15.930 | INFO: Starting ProtocolHandler ["ajp-nio-8110"]
    2016/12/22 10:06:15.946 | Dec 22, 2016 10:06:15 AM org.apache.coyote.AbstractProtocol start
    2016/12/22 10:06:15.946 | INFO: Starting ProtocolHandler ["http-nio-8143"]
    2016/12/22 10:06:15.946 | Dec 22, 2016 10:06:15 AM org.apache.catalina.startup.Catalina start
    2016/12/22 10:06:15.962 | INFO: Server startup in 381210 ms
    2016/12/22 10:11:19.367 | Dec 22, 2016 10:11:19 AM org.apache.catalina.core.ApplicationContext log
    2016/12/22 10:11:19.367 | INFO: ODataServlet: Starting ODataServlet::createServer
    2016/12/22 10:11:19.928 | Dec 22, 2016 10:11:19 AM com.ca.platform.osf.object.odata.ODataJaxRsApp initClarityODataApp
    2016/12/22 10:11:19.928 | INFO: Starting ODataJaxRsApp
    2016/12/22 10:11:19.928 | Dec 22, 2016 10:11:19 AM com.ca.platform.osf.object.odata.ODataJaxRsApp initClarityODataApp
    2016/12/22 10:11:19.928 | INFO: Finished ODataJaxRsApp
    2016/12/22 10:11:19.928 | Dec 22, 2016 10:11:19 AM org.apache.catalina.core.ApplicationContext log
    2016/12/22 10:11:19.944 | INFO: ODataServlet: [Restlet] Attaching application: com.ca.platform.osf.object.odata.ODataJaxRsApp@28a5168f to URI: /niku/odata
    2016/12/22 10:11:19.944 | Dec 22, 2016 10:11:19 AM org.apache.catalina.core.ApplicationContext log
    2016/12/22 10:11:19.960 | INFO: ODataServlet: Finish ODataServlet::createServer



  • 6.  Re: Performance issue in one of the new server

    Posted Jan 09, 2017 05:49 PM

    Monitor memory used when starting services.

    You can try to allocate a bit more. I see -Xmx3072m, try with more to see if makes a difference.

    Is this APP server used for xogging or something special?

     

    Also, ensure you java version is the one supported and try to update to latest patch for that java version.



  • 7.  Re: Performance issue in one of the new server

    Posted Jan 10, 2017 09:31 AM

    what is the maximum RAM we can allocate for CA PPM. The same application works fine in 8 GB ram windows server and it is very slow in 24 GB ram system. 



  • 8.  Re: Performance issue in one of the new server

    Posted Jan 10, 2017 03:09 PM

    What do system resources look like on startup?  Is the CPU pegged, is memory swapping?

    Is this on a VM or a physical machine.



  • 9.  Re: Performance issue in one of the new server

    Posted Jan 30, 2017 06:19 AM

    This is an VM machine. All the performance and system resources are totally normal.



  • 10.  Re: Performance issue in one of the new server

    Posted Jan 30, 2018 10:22 AM

    I don't know what happen but all the time is losed on this step :

    2016/12/21 08:35:58.718 | Clarity 15.1.0.149 initializing...
    2016/12/21 08:36:00.917 | 
    2016/12/21 08:36:00.917 | -------------------------------------------------------------------
    2016/12/21 08:36:00.917 | GMS: address=usa0300vm2248-51984, cluster=CLRTY, physical address=13.129.25.44:56729
    2016/12/21 08:36:00.917 | -------------------------------------------------------------------
    2016/12/21 08:41:16.210 | 
    2016/12/21 08:41:16.210 | -------------------------------------------------------------------
    2016/12/21 08:41:16.210 | GMS: address=usa0300vm2248-30823, cluster=CLRTY-SA, physical address=13.129.25.44:64977
    2016/12/21 08:41:16.225 | -------------------------------------------------------------------
    2016/12/21 08:41:16.366 | Clarity 15.1.0.149 ready.

     

    Also for the performance of Tomcat you receive this message

    2016/12/21 08:34:54.532 | INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: 

     

    To override this message copy the file tcnative-1.dll from the Tomcat bin directory to D:\niku\clarity\bin



  • 11.  Re: Performance issue in one of the new server

    Broadcom Employee
    Posted Jan 31, 2018 01:04 AM

    So during start up time there is 5 minute lagged. Can you check the system resources @Joshua Leone asked. Because if the system is lacking memory or CPU then its bound to take time