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...
Ralph Schoon selected this answer as the correct answer
|
3 other answers
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Jan 17 '19, 5:47 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER 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.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.