Not able to send the request through GET Method of libcurl

Hi,

We are accessing our remote webserver using libcurl.We are using GET method to post the request.The request is a simplified URL.We will receive XML Response for the URL request.

Problem

For Few Scenarios, The URL request is not being posted and our component is killed abruptly.Can anyone pls help me what would be the reason for this issue.It would be great if any one reply me the quick response.

Thanks in anticipation

I Have attached the log below which will help to track the issue clearly. our component is killed in the last statement of failure scenario abruptly.

Failure Scenario

Message code f00bb000 received at 09:07:08.550 Tuesday 30 March 2010 Thread 0xf2. CMPClient Audit ACE_CLIENT: HttpWrapper::urlRequest (http://ccp.nat.bt.com/cmps/customers?serviceId=02085785670&v=3.0)
Message code f00bb000 received at 09:07:08.550 Tuesday 30 March 2010 Thread 0xf2. CMPClient Audit ACE_CLIENT: HttpResponse::reset() entry
Message code f00bb000 received at 09:07:08.550 Tuesday 30 March 2010 Thread 0xf2. CMPClient Audit ACE_CLIENT: Transaction Started - URL http://ccp.nat.bt.com/cmps/customers?serviceId=02085785670&v=3.0
Message code f00bb000 received at 09:07:08.550 Tuesday 30 March 2010 Thread 0xf2. CMPClient Audit ACE_CLIENT: doPost is initiated its action
Message code f00bb000 received at 09:07:08.550 Tuesday 30 March 2010 Thread 0xf2. CMPClient Audit ACE_CLIENT: Response Received
Message code f00bb000 received at 09:07:08.550 Tuesday 30 March 2010 Thread 0xf2. CMPClient Audit ACE_CLIENT: About to connect() to ccp.nat.bt.com port 80

Message code f00bb000 received at 09:07:08.551 Tuesday 30 March 2010 Thread 0xf2. CMPClient Audit ACE_CLIENT: Trying 193.113.234.18…
Message code f00bb000 received at 09:07:08.551 Tuesday 30 March 2010 Thread 0xf2. CMPClient Audit ACE_CLIENT: TCP_NODELAY set

Message code f00bb000 received at 09:07:08.571 Tuesday 30 March 2010 Thread 0xf2. CMPClient Audit ACE_CLIENT: connected

Message code f00bb000 received at 09:07:08.571 Tuesday 30 March 2010 Thread 0xf2. CMPClient Audit ACE_CLIENT: Connected to **ccp.nat.bt.com **(193.113.234.18) port 80

Successful scenario

Message code f00bb000 received at 06:04:56.854 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: CMPClient::serviceRequest entry
Message code f00bb000 received at 06:04:56.855 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: HttpWrapper::urlRequest ( http://ccp.nat.bt.com/cmps/customers/1000221583.xml?v=2.0)
Message code f00bb000 received at 06:04:56.855 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: HttpResponse::reset() entry
Message code f00bb000 received at 06:04:56.855 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: Transaction Started - URL http://ccp.nat.bt.com/cmps/customers/1000221583.xml?v=2.0
Message code f00bb000 received at 06:04:56.855 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: doPost is initiated its action
Message code f00bb000 received at 06:04:56.855 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: Response Received
Message code f00bb000 received at 06:04:56.879 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: About to connect() to ccp.nat.bt.com port 80
Message code f00bb000 received at 06:04:56.879 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: Trying 193.113.234.18…
Message code f00bb000 received at 06:04:56.879 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: TCP_NODELAY set
Message code f00bb000 received at 06:04:56.904 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: connected
Message code f00bb000 received at 06:04:56.904 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: Connected to ccp.nat.bt.com (193.113.234.18) port 80
Message code f00bb000 received at 06:04:56.904 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: **GET /cmps/customers/1000221583.xml?v=2.0 **HTTP/1.1
Host: ccp.nat.bt.com
Accept: /

Message code f00bb000 received at 06:04:57.117 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: HTTP/1.1 200 OK
Message code f00bb000 received at 06:04:57.117 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: Date: Fri, 26 Mar 2010 06:04:56 GMT
Message code f00bb000 received at 06:04:57.117 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: Content-Length: 1614
Message code f00bb000 received at 06:04:57.117 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: Content-Type: text/xml
Message code f00bb000 received at 06:04:57.117 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: Content-Language: en-GB
Message code f00bb000 received at 06:04:57.118 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: X-Powered-By: Servlet/2.4 JSP/2.0
Message code f00bb000 received at 06:04:57.118 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: e2eData: 7=CMPS_getCustomer,2=getCustomerDetails,6=PCK002069,1=1ms29gkpne,1.1=APP09739:1ms29gkpne:,10=1ms29gkpsl,5=getCustomerDetails,9=cmps,15=CMPS,4=CMPS-Dflt,8=UNKNOWN
Message code f00bb000 received at 06:04:57.140 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: <?xml version=“1.0” encoding=“UTF-8” standalone=“yes”?><ns9:queryCustomerResponse xmlns=" http://capabilities.nat.bt.com/xsd/ManageCustomer/2008/09/26/CCM/QueryCustomerResponse/Parties/PartyRoles/Customer" xmlns:ns2=" http://capabilities.nat.bt.com/xsd/ManageCustomer/2008/09/26/CCM/QueryCustomerResponse/Finance" xmlns:ns3=" http://capabilities.nat.bt.com/xsd/ManageCustomer/2008/09/26/CCM/QueryCustomerResponse/Portfolio" xmlns:ns4=" http://capabilities.nat.bt.com/xsd/ManageCustomer/2008/09/26/CCM/QueryCustomerResponse/CoreClasses/Specifications" xmlns:ns5=" http://capabilities.nat.bt.com/xsd/ManageCustomer/2008/09/26/CCM/QueryCustomerResponse/Places" xmlns:ns6=" http://capabilities.nat.bt.com/xsd/ManageCustomer/2008/09/26/CCM/QueryCustomerResponse/Agreements" xmlns:ns7=" http://capabilities.nat.bt.com/xsd/ManageCustomer/2008/09/26/CCM/QueryCustomerResponse/Identification" xmlns:ns8=" http://capabilities.nat.bt.com/xsd/ManageCustomer/2008/09/26/CCM/QueryCustomerResponse/Incidents" xmlns:ns9=" http://capabilities.nat.bt.com/xsd/ManageCustomer/2008/09/26" xmlns:ns10=" http://wsi.nat.bt.com/2005/06/StandardHeader/" xmlns:ns11=" http://capabilities.nat.bt.com/xsd/ManageCustomer/2008/09/26/CCM/QueryCustomerResponse/Parties/PartyRoles/Customer/SearchResult" xmlns:ns12=" http://capabilities.nat.bt.com/xsd/contacts/2009/09/07/getContacts"><ns9:customerAccount><id>1000221583</id><creditScore>500</creditScore><primaryContactId><id>2000107326</id></primaryContactId><name>MR GEORGE FORDYCE</name><type>Consumer</type><customerClass>C</customerClass><sacId> </sacId></ns9:customerAccount></ns9:queryCustomerResponse>
Message code f00bb000 received at 06:04:57.140 Friday 26 March 2010 Thread 0xf3. CMPClient Audit ACE_CLIENT: Closing connection #0

Anjalin wrote:

please reply with output of:

cat /etc/SuSE-release
or
cat /etc/issue

and: were any system updates applied between the success on 26 and
failure on 30 March? which?

were any other changes made to the system or systemS (either end?)

[not that i think i can help you personally, but i have an idea that
most anyone who can might be able to would like to know what system is
working and what changed]


palladium