shalinee

Issue while restarting the services using command niku start

Discussion created by shalinee on Oct 9, 2012
Latest reply on Oct 11, 2012 by Chris_Hackett
Hi All,

We are getting weird error when trying to restart the services on my application server 2. We have load balancing environment with 2 application servers. We are on CA Clarity 12.0.4 setup with default web server (Tomcat) and java 1.5.0.11. We have an automated script to restart the server on ever week and this script was working fine since a long time .

Recently, we have observed that we are not getting mail from app server 2 restarted and then noticed the automated script log is throwing an error when trying to deploy the "app" service. Here is the error.

Deploying service(s)...
Done.
The Niku System Admin Server service is starting...
The Niku System Admin Server service was started successfully.

Deploying service(s)...

Failure occured:
E:\Clarity\.setup\scripts\deploy.xml:172: E:\Clarity\.setup\scripts\deploy.xml:173: The following error occurred while executing this line:
E:\Clarity\.setup\scripts\deploy.xml:182: org.jdom.JDOMException: Error in building: The process cannot access the file because another process has locked a portion of the file

See admin.log file for possible errors, or try -verbose option.
Deploying service(s)...
Done.
The Niku Server 3 service is starting....
The Niku Server 3 service was started successfully.

Deploying service(s)...
Done.
The Niku Server 4 service is starting....
The Niku Server 4 service was started successfully.

Then we tried to stop the services via command line and restarted again and it is throwing the same error when trying to start the app service. Later when we ran the niku start app command only then it is working fine and no error.

Thanks,

Outcomes