Resolution:
Description:
============
Occasionally, when using the HTTP client adapter, the servive context created by the driver can timeout before the end of the service order and lead to the following error message :

2011-04-05 13:30:53.348860|WARN |provca:47|ccdriver:sc:1302002813624183000|ccdriver:sc:1302002813624183000|REQUEST TIMEOUT

The HTTP Responder, without the service context, cannot send the response.
2011-04-05 13:34:56.914528|WARN |provca:52|ccresponder|ccaid2890585|43543|ServiceContext &ltccdriver:sc:1302002813624183000> NOT FOUND in OSSM. It may have been removed as a request timeout consequence.


Environment:
===========
Solaris 5.10 64-bit platform
Linux Redhat 5.0 x86_64 i386-64 GNU/Linux

Symptoms:
========
HTTP request timeout, KPSA responder not sending the response.

Cause:
=====
By default, the requestTimeout parameter is configured to 60 seconds for each service context created by the HTTP driver. If a service order takes more than 60 seconds to be processed then the service context will expire and will be deleted. The HTTP responder wull not be able to response to the north bound application because of the deletion of the service context.

Resolution:
==========
To avoid this occurrence increase the value of the parameter requestTimeout configured in the ServiceContextFactory configuration. The idlosdocs of the provca package (see ServiceContextFactory interface) explains the usage of this parameter. This has to be done in the config.ini file in the section ServiceContextFactory as follows :
[ SCF_CC : provca::ServiceContextFactory ]
name    = SCF:CC
makeRequestCheckpoint    = 0
makeFrameCheckpoint    = 0
requestTimeout = 180

[Keywords / TAGS]
KPSA,provca,HTTP,ServiceContextFactory

Configuration of request timeout on HTTP CA