Home > Back-end >  Tomcat to 45 will automatically stop at 7 o 'clock in the evening, after the restart
Tomcat to 45 will automatically stop at 7 o 'clock in the evening, after the restart

Time:10-06




A running is fine, but run to 7 PM began to complain about 46, every day is such, before seem to have no this kind of situation, only to restart the computer, checked memory leaks, but I'm not sure, whether tomcat configuration have what problem, please, answer,

CodePudding user response:

Added a memory or 45 at 7 PM yesterday when problems happened

CodePudding user response:

May be you have timing task program at this time, the timing task cause memory leaks

CodePudding user response:

But inside the log log without OutOfMemoryError this error, I also don't know whether I memory leaks

CodePudding user response:

Top, for bosses to solve it

CodePudding user response:

You don't see what the reason, you should have the monitoring server memory, and CPU time state, then look again

CodePudding user response:

With the threadlocal not remove lead to?

CodePudding user response:

I also strange problems,
My CMD running Java, access it should print the original socket,
Results themselves there, as long as I'm on the keyboard keys, just see the output,
I feel strange, can't solve,

CodePudding user response:



Still can't solve, bosses, but it seems related to this new problem,,,

CodePudding user response:

Is usually caused by increased traffic,
In general the bottleneck will appear in the database server
Check each server CPU usage, memory usage,
If all the server CPU usage, memory usage is less than 90%, can be big nginx, tomcat, the maximum number of connections database

CodePudding user response:

Peak CPU usage, memory usage to check (20:00 to 22:00) value, nothing to look at ordinary times,

CodePudding user response:

Confirm whether mysql problems caused by eight hours will automatically disconnect, idle for more than eight hours will automatically disconnect
  • Related