Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.8K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 439 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Issue at the customer end - gateway timeout error

Hi,
We are getting an "gateway timeout error" for one customer when we tries to place an order from his local machine, this is happening for only one customer. Hence , it looks like there is some problem at the customer end, what are the parameters which can contribute to this issue from the customer end like n/w connectivity, etc? which we need to verify?
As Gateway timeout Error happens when "one server did not receive a timely response from another server that it was accessing while attempting to load the web page "?
Please clarify.
Thanks
Answers
-
If it's not happening with all your customers, or at least all your customers performing a certain operation, it does not smell like a coding issue, but rather something in your infrastructure or networking. See https://www.reference.com/technology/504-gateway-timeout-mean-a3a1efcaf584ea22
I'm afraid a Java forum is probably not a good place to ask questions like this.
-
You need to put a network trace on the route, or more easily, start out with a trace route using the IP protocol and see where the congestion is. Does it happen every time or just some times? If it happens sometimes, that is a horrible problem to trace, you have to put a packet sniffer in the line and see what conditions are present when the problem manifests. I have had it as simple as a router or gateway needed to be rebooted, and happy day, the problem was fixed. On the other hand I've had to trace for weeks to finally get enough cases to form an opinion of what was happening and then take even longer tracing out options on what was the cause.
good luck,
Les