First of all: We are running right now Integrity 10.4.
I'm facing from time to time trouble with Web Services commands (for eg. getConfigurationPath), but I can't say why.
I postulate maybe a problem with the Session Handling or Timeout trouble.
Usually for periodic activity every hour (for example) I prepare a set of commands beginning with connect and ending with disconnect.
In the Documentation for Web Service I've found this inf (document: WebServicesReference_Integrity_10_4.pdf, page 67):
Does anyone have experiences with such an approach?
Our server's timeout settings are as short as possible ....
Thanks for every hint.
Hello Klaus Hoppe,
If you don't disconnect and reconnect, does the session still get disconnected?
How are these web services being used, or in what context? It sounds like your issue, is that the web service session is held too long? You don't mean it's getting disconnected too soon, do you? Web services does its own management of sessions, so it may be for your use-case, it's not releasing them soon enough?
Are triggers fired or involved here, at all?
I ask, because if I remember correctly, there are trigger related issues that can cause API sessions to not be released. But, it doesn't sound like that is involved here.
You may want to open a Support case, to look into this.
Additional info for usage of WebServices in this context
An application developed by another company sends around every hour some commands to fetch Project Structure and look for new/changed member.
From time to time the commands fail, but after that they succeed again.
My intention for this question is, if this could have to do with Session handling.
I remember of timeout settings for GUI-/CLI-activities and ask myself if something similar might cause trouble we are facing here.
Sorry to be not precise enoguh in my first posting.
To the questions:
I can't say whether sessions have been disconnected and reconnected. Following the documentation the App Provider does not do such activities.
AND there are no trigger involved now.
I think there's a defect that can cause sessions to disconnect after an hour, regardless of activity, but I can't remember the SPR, nor the versions affected. It's probably worth opening a case to investigate.
Possibly defect SPR # 6175680, if that is the problem Klaus is seeing with this.
your link tells about a defect which applies to Integrity Lifecycle Manager Integrity 10.6 to Integrity 11.0
We are running 10.4 now.
Or do you think it has been in that earlier version a bug, too ?
It looks like the "defect" was reported or found on Integrity 10.6, but I would be surprised if it is not also present on earlier 10.x releases as well. The article you refer to, is constantly updated when we get information from customers, so it's likely we just haven't had reports of that issue on earlier 10.x releases.
I would open up a Support case, to pursue this more, and to confirm if this defect could apply to you on 10.4.
Case already opened, but my colleague who I need to do tests and to verify behaviour, is out of office for a longer time.
I let you hear as soon I have new infos.