Page 1 of 1

service first request is consuming more time

Posted: Tue Jul 30, 2013 9:29 am
by moulicherukuri
I have a web service job for address cleansing which accepts input as array and delivers array output

This job has 5 input columns and returns nearly 59 output columns (CASS address fields ,Standardized address fields..)

To improve performance and to reduce payloads build job to accept pipe delimited input and returns pipe delimited output without column names.

The following are the setting for services which this job is using

-- Active job instances
Min -- 2
Max -- 5

-- Idle Time
Min -- 60 sec
Max -- 0 sec( checked infinite check box)

-- Activation Threshold
Service requests -- 3
Delayed -- 1000 (milliseconds)

-- Request limit : 5

The problem is this service is going into Idle after sometime and getting timeout errors; to resolve this and to keep service alive implemented workaround method sending 10 records as requests to this services every 5 mins continuously through DataStage job

But every morning first request is consuming more time

Guru's:- Do I need to take any extra steps to keep this service alive ?

Posted: Tue Jul 30, 2013 2:02 pm
by eostic
Not sure.....prior to your submitting those dummy requests (ie..when you know you are going to have a long-response-time condition), take a look in the DS Director....are the instances up and running and available? That would be the first thing I would check....possibly there are issues with CASS and initialization after a long delay --- I'm not sure....

Ernie

Posted: Tue Jul 30, 2013 2:12 pm
by moulicherukuri
Yes the Instances are up and running.I checked it I have 1 in compiled state and other 2 in running state