Internal Website Search

incidents. The system seems to destabilize for about 10-15 minutes and then it returns to normal. During these 10-15 minutes we get a lot of slow responses. Not all of the requests during these times ... a high load - around 25000 calls to the db per minute. This includes variety of read and update

. The sequence of events was: 13:20 - our monitoring reported GC time per minute on the SLAVE ... until it reached almost 1 minute per minute, at which point the process is essentially hanging - see attached ... . All requests sent to the database during 3 minutes between 13:22:43 and 13:25:43 returned at 13:25:44

also occurs, if we wait 10 minutes before we close the database. We have also the code ... also occurs, if we wait 10 minutes before we close the database. Could please clarify if in this case the exception is also thrown after 10 minutes, immediately after closing the database

sockets in some loop. This took about minute, so I will try to create java thread dump ... sockets in some loop. This took about minute, so I will try to create java thread dump ... was started for 4 minutes and idle. I saw 40 instances of SSLSocketImpl in heap dump

, 0);         cal.set(Calendar.MINUTE, 0);     ... ;      cal.set(Calendar.MINUTE, 0);       

the project again. Important: do all that until a new number is printed. There is a 1 minute ... , and run the project again. Important: do all that until a new number is printed. There is a 1 minute delay

details about the number and types of transactions per minute when the system is on load? minutesminute, new objects and updates by type per minute

the tool needs less than 2 minutes to read a million values - now as before with different cache settings and enhanced classes it takes more than 8 minutes. This I would have not expected - normally ... > With not enhanced classes the tool needs less than 2 minutes to read a million values - now

, but they are relatively light, and the db has just a few MB at the moment. After a few minutes ... is relatively low, the errors start to appear after some minutes or half an hour, or even an hour ... the situation. With a heap of 100 MB, Tomee runs out of memory in ~20 minutes. With a heap

for this process to complete (about 20-30 minutes on your sample database). It may be effective to run ... ; version 2.8.3 query plan (query takes minutes): Query plan 1/16 description