.net client issue for session management
Hi, I have implemented axis webservice managing sessions using axis 1.2.1. Session management works fine with java client but .net client behaves unexpectedly. For .net client 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 ... **Response: HTTP/1.0 200 OK Set-Cookie: 60 Set-Cookie2: 60 Content-Type: text/xml; charset=utf-8 ... 2** Second method call made by .net client also makes server side create new instance for the session even though 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= ... **Response: HTTP/1.0 200 OK Set-Cookie: 60= Set-Cookie2: 60= Content-Type: text/xml; charset=utf-8 ... 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
RE: .net client issue for session management
Also I don't see any JSESSIONID in cookie area while watching under tcpmon. Am I doing something wrong? Java client runs fine and behaves as expected but .net client raises issue on second method call. -Raj From: Rajesh Patel [mailto:[EMAIL PROTECTED] Sent: Thursday, June 23, 2005 5:17 PM To: axis-user@ws.apache.org Subject: .net client issue for session management I am using axis 1.2.1. I am implementing session management by adding --deployScope Session option for server side stub generation. I created java client with serviceLocator.setMaintainSession(true); for client stub locator and it works as expected for java client. I am trying to consume webservice on .net client by adding clientStub.CookieContainer = new CookieContainer(). When I make first call I see cookie returned by axis server side and requests after that includes cookie reference with Cookie: 7=; 7= in http header section under tcpmonitor utility. For some reason second call creates new instance on server side instead of using existing instance on server side eventhough it has cookie reference. After 2nd call all the rest of the method calls picks up existing instance on server side. Does anyone know why second call does not pickup existing instance and why axis creates new instance eventhough it has cookie reference for session maintenance? -Raj
.net client issue for session management
I am using axis 1.2.1. I am implementing session management by adding --deployScope Session option for server side stub generation. I created java client with serviceLocator.setMaintainSession(true); for client stub locator and it works as expected for java client. I am trying to consume webservice on .net client by adding clientStub.CookieContainer = new CookieContainer(). When I make first call I see cookie returned by axis server side and requests after that includes cookie reference with Cookie: 7=; 7= in http header section under tcpmonitor utility. For some reason second call creates new instance on server side instead of using existing instance on server side eventhough it has cookie reference. After 2nd call all the rest of the method calls picks up existing instance on server side. Does anyone know why second call does not pickup existing instance and why axis creates new instance eventhough it has cookie reference for session maintenance? -Raj
