pavolgocal (Customer) to rsaSFDCadmin (RSA): asked a question.
504 HTTP error while using IGL application
Hello guys,
We are on customer production environment with a new installation of IGL
version 7.5.2. P05.
I get a lot of HTTP 504 timed outs while using the UI. I checked the logs and
the errors I see are in attachments of this post.
For example – when I configure the AD collector, I go to the first screen
(description, business source, etc.), then click “Next” and all I see is a
loading bar (no screen shown). After a few moments, the error is shown with
HTTP 504 exception.
Or when I get to the account collector connection settings (if it does not
timed out), when I check "use ssl", again it shows 504 time out.
The same happens when I configure rules, or workflows. I do the configuration
work, and them the app is just loading and then HTTP 504 exception is shown.
I have to do all the configuration again, nothing is saved.
I have no idea what can cause this, because we have the same installation on
customer PROD environment as we have on customer TEST environment.
Any ideas what could cause this?
**Important note:** The customer and customer's environment is very specific,
with restricted access -> I cannot just log in and download logs, or check
something using linux commands on demand -> I have to be physically present in
the room, where I have a computer available -> so it is hard to share specific
information with the community.
I also created support case, but as we are about to go to the production, this
is the highes priority for us and I try all available channels. Maybe you
could help.
Thank you.
We are on customer production environment with a new installation of IGL
version 7.5.2. P05.
I get a lot of HTTP 504 timed outs while using the UI. I checked the logs and
the errors I see are in attachments of this post.
For example – when I configure the AD collector, I go to the first screen
(description, business source, etc.), then click “Next” and all I see is a
loading bar (no screen shown). After a few moments, the error is shown with
HTTP 504 exception.
Or when I get to the account collector connection settings (if it does not
timed out), when I check "use ssl", again it shows 504 time out.
The same happens when I configure rules, or workflows. I do the configuration
work, and them the app is just loading and then HTTP 504 exception is shown.
I have to do all the configuration again, nothing is saved.
I have no idea what can cause this, because we have the same installation on
customer PROD environment as we have on customer TEST environment.
Any ideas what could cause this?
**Important note:** The customer and customer's environment is very specific,
with restricted access -> I cannot just log in and download logs, or check
something using linux commands on demand -> I have to be physically present in
the room, where I have a computer available -> so it is hard to share specific
information with the community.
I also created support case, but as we are about to go to the production, this
is the highes priority for us and I try all available channels. Maybe you
could help.
Thank you.
response time of the application is less than the timeout specified on the
gateway. It may be hiding some other error on the backend, or more simply it
just is hiding a normal (but slow) display of the page.
This error is not diagnostic for any specific failure (and in fact there may
be no failure).
The gateway can (and likely should) be configured for a slightly longer
timeout. You still may have performance issues after doing this but you will
not get the failure and will have an opportunity to address performance
separately.
The other examples you provided are very specific things that are failing but
its impractical to troubleshoot them in the presence of the gateway blocking
access to the page after the timeout.
Note that the gateway is not part of the RSA application. We don't have
general guidance and it depends on what load balancer you are using.