michael.lukatchik
Member
All,
We're currently using JDE 8.11 across a WAN.
At any given time, a User could successfully be logged into the web for JDE. However, upon subsequent attempts to log back into the web, Users are receiving a "Page Cannot Be Displayed" error. To the User, it appears that the JDE web is unavailable. At the same time, it is entirely possible for other Users to be on the same server and same environment that appears to be "culprit" to our other Users.
When a User indicates that the web is unavailable, we can clearly see through OAS that the culprit environment is in fact up and running, and when instructed, the user can successfully ping the JAS server they're trying to log on to.
Our temporary solution has been to restart the JDE Web serivces for the culprit environment every time a User reports that the web is unavailable. We certainly cannot have this happen every time the issue arises as it impacts other users on the system.
Is there something cached on the JAS Server that's randomly not letting users into the JDE Web?
Again, when the problem happens an HTTP 404 Page Cannot be Displayed error is displayed. Restarting the web services has resolved this, but it cannot happen every time the issue arises.
Does this sound like a JAS Server configuration issue or does it sound more like a network issue?
Thanks for your input.
We're currently using JDE 8.11 across a WAN.
At any given time, a User could successfully be logged into the web for JDE. However, upon subsequent attempts to log back into the web, Users are receiving a "Page Cannot Be Displayed" error. To the User, it appears that the JDE web is unavailable. At the same time, it is entirely possible for other Users to be on the same server and same environment that appears to be "culprit" to our other Users.
When a User indicates that the web is unavailable, we can clearly see through OAS that the culprit environment is in fact up and running, and when instructed, the user can successfully ping the JAS server they're trying to log on to.
Our temporary solution has been to restart the JDE Web serivces for the culprit environment every time a User reports that the web is unavailable. We certainly cannot have this happen every time the issue arises as it impacts other users on the system.
Is there something cached on the JAS Server that's randomly not letting users into the JDE Web?
Again, when the problem happens an HTTP 404 Page Cannot be Displayed error is displayed. Restarting the web services has resolved this, but it cannot happen every time the issue arises.
Does this sound like a JAS Server configuration issue or does it sound more like a network issue?
Thanks for your input.