Maximo Open Forum

I have users reporting 504 Gateway Time-out error in Maximo when accessing Service Request.  

Maximo 7.6.1.0

Linux servers

#Administration

------------------------------
Curtis Rushing
Baxter Healthcare
------------------------------

I would access this on the internal JVM port (such as 9080) to see how long that takes to avoid the gateway. Something abnormal is going on with the service request application it seems that is making it take a long time to load which is why you're seeing the gateway timeout. Looking at the Maximo logs might help indicate the performance issue if it's query related for example. 

I think there was a separate post here about service request performance issue that was identified as an APAR but I'm struggling to find it at the moment. It involved something with labor transactions.

------------------------------
Steven Shull
IBM
------------------------------

A 504 Gateway Time-out usually indicates that the web server or reverse proxy isn't receiving a timely response from the Maximo application server. Since you're running Maximo 7.6.1.0 on Linux, I'd start by checking the application server logs, web server timeout settings, database performance, and overall server resource usage (CPU, memory, and disk I/O). It's also worth verifying whether the issue occurs only with the Service Request module or across other applications.

If the problem is intermittent, there could be a long-running query or a network communication delay between the web server and the Maximo application server.

We encountered a similar timeout issue while integrating an enterprise SMS Gateway Solution with a business application. Increasing the gateway timeout, optimising backend processing, and reviewing server logs helped identify the bottleneck. Looking at your proxy and application server timeout configurations may help pinpoint the root cause.

------------------------------
John Raugh
100Coins
------------------------------