Server stopps responding after PUT request
I am trying to update some test case data programmatically via PUT request. On the first request, everything works fine. After that, the next PUT request just times out, the RQM server seems to stop responding to any requests, also GET or POST requests fail with timeout.
Is this a known issue, or should i do some kind of logout after a PUT request or something similar? If I wait a while and login-logout to RQM interactively a couple of times, it works again, but again only once.
Accepted answer
Somehow I had commented out my "response.close()" during login. So for the server I was initiating a session again and again, so the sessions were locking out each other.
Now I'm taking extra care to really close the requests and all is working fine...
3 other answers
There is pretty much no usable information in this post. See How should I ask a question in the Forum if I want to receive useful answers?
Since the Web UI uses PUT all the time, I would assume it is your client and its usage that creates the lock up. Since you omitted providing any insight in how the PUT is done, I'd suggest you search in a forum related to your method doing the PUT.
If, after your PUT, communication with the server is no longer possible using a Browser, your PUT kills the server which should not happen. The server log could be a place to start.
As Ralph mentioned, it's difficult to provide assistance with no details (including the REST API you are using). I would suggest it's your HTTP client since this is not an expected behaviour.
Thanks for the answers, I'll try to be more specific:
What I am trying to do is update the description of many test cases in RQM programmatically. So I GET the test case, do some minor changes in the XML I received from the GET request and PUT back the whole XML to RQM.
I am trying to connect via c# programmatically to our companies RQM server. My c# application does an authentication somthing like this:
request2 = (HttpWebRequest)WebRequest.Create(_rqmSrvr + "/jts/authenticated/j_security_check?j_username="+ username + "&j_password="+ password);
Then I get a response with the authentication cookie and store that for later use. This works fine. The next thing I do in my code is a GET request, something like:
XDocument testcase = RQMGetRequest(_rqm_srvr+"/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources//testcase/urn:com.ibm.rqm:testcase:4964")
The method uses the cookie internally and puts it in the CookieContainer of the GET request.
This also works fine.
I then modify the description of the test case, and send it back with something like:
RQMPutRequest(_rqm_srvr+"/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources//testcase/urn:com.ibm.rqm:testcase:4964", myModifiedXml)
Where I also provide the cookie container internally in that method.
The PUT method internally looks like this:
HttpWebRequest request = (HttpWebRequest)WebRequest.Create(prefix + querySuffix);
request.CookieContainer = _rqmSessionCookieContainer;
request.Method = "PUT";
request.Accept = "application/xml";
request.ContentType = "text/xml; encoding='utf-8'";
byte[] bytes = System.Text.Encoding.UTF8.GetBytes(xdoc.ToString());
request.ContentLength = bytes.Length;
Stream requestStream = request.GetRequestStream();
requestStream.Write(bytes, 0, bytes.Length);
requestStream.Close();
requestStream.Dispose();
HttpWebResponse response = (HttpWebResponse)request.GetResponse();
I am just trying out things at the moment, so I do the whole procedure every time new:
- Login to the server
- Get the cookie
- Do the GET request for a single (sample) test case
- Do the PUT request
First time: all ok, second dime: Timeout
Maybe there is there some kind of disposal of the session that I should do, before starting the second time?
I have no access (or I don't know how to access) the RQM server logs, unfortunately...
Thanks for the advice again, I hope this makes a bit clearer what I want to do...
Comments
