1
So I have a web application (Java + Spring + JPA) on Tomcat 9.0 and several machines connected on it, mobile phones and laptops, all working perfectly.
However, there is a notebook (i5, Windows 10 Pro) that connects and can use all the features, but after 1 minute more or less it goes unanswered, when refreshing the page the warning is:
192.168.x. x(server ip) is not working.
Only in this notebook this happens, and the strange thing is that by removing the domain of the application I can access the Tomcat host in this notebook. I’ve disabled firewall and antivirus, changed the ip and browser and nothing, just when restarting the note it connects, and soon falls.
Any idea?
Have error log or warn?
– adelmo00
No, nothing, the Tomcat logs show nothing wrong, the application does not even load, I realized that in Mozilla the error that the page shows me is Connection restarted( The connection to the server was restarted while loading), and simultaneously there are other laptops and mobile phones accessing without problems, including after the notebook in question stop working.
– Bem Hur Ganem
Already tested in another browser? Ever tried to connect this notebook without another device being connected?
– DiegoAugusto
try to keep shooting ping to this server on the machine with problem when it stops working, in theory ping should stop too, it may also be the network card of this machine that is not working well, try to use wired network or Wi-Fi and see if the problem persists
– Guilherme Golfetto
This can be anything that causes the program to exhaust itself. Maybe little memory (the program lasts more than 1 minute if not used)? It could be a background lawsuit consuming resources. It may be a timeout with the database connection that is no longer reopened (local databases with the default configuration may present surprisingly small limits). It can be a deadlock of any nature that holds the other connections. It may be that the system is not closing connections with the bank and the connection pool is empty, which blocks new requests.
– utluiz
I suggest we try to create some simpler page, no bank access, and see if it remains accessible. Finally, perform some tests trying to isolate the problem and determine if it is even in Tomcat or some specific function of the system. Monitoring the JVM using a tool like Jvisualvm that comes in JDK 6 onwards can help a lot. The tool allows you to see in real time the memory used, the active threads (and possible deadlocks, if you know how to analyze the stacks) and much more.
– utluiz