How it can be fixed that the first webservice call generate a network error after a restart of the Openedge database/appserver?
The next and further call work fine
Could you provide more information like
What is the error?
Where and in which log file?
How are you calling the WebService?
Which client are you using?
How do you restart database/appServer?
This is actually a very good question. Something that I have seen since OE10 - never got a really good answer. And as far as I know this is only seen on the WSA (SOAP) based web services - for REST it works first time round.
We got around this issue to always try more than once when we called the web service - just to get it to become available.
Looking forward to a good answer on this one...
This is the first reply, tested with a SOAP-UI.
It works, I stop the appserver and start again (asbman) -> then the first call fails.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="schemas.xmlsoap.org/.../" xmlns:xsi="www.w3.org/.../XMLSchema-instance" xmlns:xsd="www.w3.org/.../XMLSchema">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>An error was detected while executing the Web Service request. (10893)</faultstring>
<detail>
<ns1:FaultDetail xmlns:ns1="urn:soap-fault:details">
<errorMessage>A network error occurred executing the Web Service application. (10899)</errorMessage>
<requestID>7ff01504dcfad085:-1506265f:14bb57ad063:-7fff#71</requestID>
</ns1:FaultDetail>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
This is actually a very good question. Something that I have seen since OE10 - never got a really good answer. And as far as I know this is only seen on the WSA (SOAP) based web services - for REST it works first time round.
We got around this issue to always try more than once when we called the web service - just to get it to become available.
Looking forward to a good answer on this one...
Flag this post as spam/abuse.
This has been an issue ever since the session free model was added. The session-free is advertised as connection-less, but consedering the issues it's not entirely connection-less after all. The link Stefan mentoined states "It was determined that the Progress Product is functioning as designed.", which may be true, but it's still odd for an connection-less protocol and it raises some questions about the design.
Anyway, it shouldn't be a problem anymore if you switch to PASOE, because then you can't switch off the AppServer independently from the WSA/REST adapter anymore...