Project and Portfolio Management Practitioners Forum
cancel

Command Step is not subject to timing out

Highlighted
LouiseZhang
New Member.

Command Step is not subject to timing out

Hi, dears

In reqeust web page, when I click workflow step 'Recalculate' button, it takes 2 minutes to complete the calculation, and then return the web page. sometime, it returns time-out error page.

I have a look at the Execution log, the log begin with below :

 

The following Command Step is not subject to timing out: com.kintana.core.server.execution.CLStoreCommand

KSC Store Source Command: Clear out calculated fieldsHIGH_BAND="", ""

The following Command Step is not subject to timing out: com.kintana.core.server.execution.CLStoreCommand

KSC Store Source Command: Clear out calculated fieldsQT_HIGH_BAND_LOCAL="", ""

The following Command Step is not subject to timing out: com.kintana.core.server.execution.CLStoreCommand
................
KSC SQL Query Source Command: Calculate Support Discount %Running query: select round(((6480 - 4924.8) / 6480) * 100,2) from dual
The following Command Step is not subject to timing out: com.kintana.core.server.execution.CLStoreCommand
................
Hope someone experienced can solve this issue.
Thanks so much.
Louise
2 REPLIES
AlexSavencu
Acclaimed Contributor.

Re: Command Step is not subject to timing out

Hi, Louise,

Your description is pretty vague. You have to investigate one full log which contains the error and then you will be able to figure out what the problem is.

Cheers
Alex

--remember to kudos people who helped solve your problem
Utkarsh_Mishra
Acclaimed Contributor.

Re: Command Step is not subject to timing out

Try to increae the command time out in  the command.

 

Also can you share the commad log file... you can find it under <PPM_ROOT>/logs/REQ_<your_request_id> folder.

 

Secondly whenever you are using ksc_run_sql command then alteast 1 environment of host must be set correctly in PPM and then use this command as

 

ksc_run_sql QUERY_STRING="select * from dual" ENV_NAME="PPM_INSTANCE" (put env_name as per your configuration)

or

ksc_run_sql QUERY_STRING="select * from dual" ENV_NAME='[SOURCE_ENV.ENVIRONMENT_NAME]'

(here you need to mention the enviornment in Source environment field in workflow step properties)

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)