View Issue Details

IDProjectCategoryView StatusLast Update
0008359VALENTINA SERVERDatabasepublic2019-11-06 11:46
ReporterAleksandar SpasojevicAssigned To 
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionopen 
PlatformALLOSWindows Server 2016 StandardOS VersionALL
Product Version8.2.x 
Target VersionFixed in Version 
Summary0008359: VServer stucks after few minutes of working
DescriptionProblem which I'm trying to explain is happening from VServer version 8.3 . Currently, we are using VServer 8.5.5 .
I couldn't find reason for this. We have Applications written in XOJO which are working with DB. When I start VServer 8.5.5 it works great. Few minutes later, sometimes 2, 5, 10 or 1 hour later, it stops responding. Our application also stops responding, it stucks forever when it tries to get something from DB. For example, table1.RecID = 100 when VServer is stuck doesn't work. There is no any Exception, just stays on that line until I kill VServer, so VServer is affecting application, even if communication with DB is from Thread.
Valentina Studio can see VServer on that time, but it cannot connect, its just showing progress bar. When I go to Services, VServer is running, and if I click Stop, it will start filling ProgressBar, but it won't stop it. I was waiting for few minutes and after that, Windows returns message that it cannot stop Service and change VServer status from Running to Stopping. The only way to actually stop it is to Kill process in Task Manager.

WINDOWS MESSAGE WHILE TRYING TO STOP VSERVER:
"Windows could not stop the VServer_64 service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion."

This is happening on Windows 10 Pro and Windows Server 2016 Standard.

I saw in one of logs problems in DB, I did reindex and after that Diagnose. There is no errors.


In case logs are not uploaded here becaues of size limit, you can download it from here:
https://drive.google.com/open?id=1o_Mr6_5aVGJoDPlOM5fZgeq-NNFFOzqs

Here are logs from second machine after killing service, with also VServer 8.5.5 but with new and completely healthy DB:
https://drive.google.com/open?id=16t0zc1OcC2ZwA5Tr7tKL2BnbrL5GKoNn


If you have any other questions about this, please ask, I will try to help as much as I can, or if want to test databases. This means we cannot use versions after 8.2
TagsNo tags attached.

Activities

Ruslan Zasukhin

Ruslan Zasukhin

2019-11-06 11:46

administrator   ~0011057

we did maximum for now for this

Issue History

Date Modified Username Field Change
2018-09-13 11:36 Aleksandar Spasojevic New Issue
2019-11-06 11:46 Ruslan Zasukhin Note Added: 0011057
2019-11-06 11:46 Ruslan Zasukhin Status new => closed