Clarity Application service restarts automatically. The user gets error message: "Page cannot be displayed".

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Description:

The app-niku.log reports following messages:-

Clarity 12.0.1.5063 initializing...
Clarity 12.0.1.5063 ready.
JVM appears hung: Timed out waiting for signal from JVM.
JVM did not exit on request, terminated
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.

CTRL-C trapped. Shutting down.
<-- Wrapper Stopped
Niku Server installed.
--> Wrapper Started as Service
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.

Solution:

• Add the wrapper.ping.timeout property in the $niku_home\bin\nikuappcmd.conf file.
  
  
  • The service commands read these *.conf file from $NIKU_HOME\bin folder.
    Please note, every time the services are deployed these files are overwritten so you need to make the changes to the templates of those files.
    
    wrapper.ping.timeouot value should reduce the recurrences of the JVM hung instances.
    
    
• There can be more information obtained from a google search:
  
  http://www.google.co.uk/search?hl=en&q=%22JVM+appears+hung%3A+Timed+out+waiti
  
  If the above does not help,
  
  
• One can start Clarity APP server in a console mode using following command.
  niku start nikuappcmd
  
  Then capture the output messages when Clarity restarts/crashes. Contact CA Technical support providing these messages.

Keywords: CLARITYKB, nikuadmin, start, status.

Environment

Release:
Component: PPMENV