.net client and session management issue

[Rajesh Patel <rp...@connecterra.com>]

Hi,
     I have implemented axis webservice using axis 1.2.1. It works fine with java client but .net client behaves unexpectedly. In short session starts after second method call instead of first call. Here is what happens,

1** First method call made by .net client makes server side create instance for the session
Here is the request and response info from tcpmon,
**Request:
POST /axis/services/ProductCatalogCSVReader HTTP/1.1

VsDebuggerCausalityData: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2032)
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
Content-Length: 438
Expect: 100-continue
Connection: Keep-Alive
Host: localhost:8060
<?xml version="1.0" encoding="utf-8"?>...</soap:Envelope>

**Response:
HTTP/1.0 200 OK
Set-Cookie: 60
Set-Cookie2: 60
Content-Type: text/xml; charset=utf-8
<?xml version="1.0" encoding="utf-8"?>...</soapenv:Envelope>
2** Second method call made by .net client also makes server side create new instance for the session eventhough Client request contains cookie ref returned by first response.
**Request:
POST /axis/services/ProductCatalogCSVReader HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2032)
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
Content-Length: 438
Expect: 100-continue
Connection: Keep-Alive
Host: localhost:8060
Cookie: 60=; 60=
<?xml version="1.0" encoding="utf-8"?>...</soap:Envelope>

**Response:
HTTP/1.0 200 OK
Set-Cookie: 60=
Set-Cookie2: 60=
Content-Type: text/xml; charset=utf-8
<?xml version="1.0" encoding="utf-8"?>...</soapenv:Envelope>


3.** calls after this for same method gives same content for request and response and no server side instance is created and session instance is used as expected.

Why session is not starting at first method call and instead starts at second method call. Especially even though client request has session id provided?? Am I supposed to see JSESSIONID in http header or it is not the case anymore?

-Raj