Actions
Bug #1963
closedServer not respond
Start date:
06/08/2013
Due date:
% Done:
0%
Estimated time:
Description
After a two or three days the server stop to reponse the requests, but the wt server process continue on memory and the log not show what happens
Files
Updated by Koen Deforche over 11 years ago
- Status changed from New to Feedback
- Assignee set to Koen Deforche
Hey Marcio,
Can you attach gdb to the process when that happens, and print a full stacktrace of all threads?
(gdb) thread apply all bt
Regards,
koen
Updated by Marcio Sales over 11 years ago
Hey Koen,
look, appear to lock thread.
Regards,
Márcio
Updated by Koen Deforche over 11 years ago
Hey Marcio,
That's just one thread; we need to know the state of all threads.
Regards,
koen
Updated by Marcio Sales over 11 years ago
Hey Koen,
see the complete log.
Regards,
Márcio
Updated by Koen Deforche over 11 years ago
- Status changed from Feedback to Resolved
- Target version changed from 3.3.0 to 3.3.1
Hey Marco,
Thanks for the log. We recently discovered this issue too and it has been solved in git.
Regards,
koen
Updated by Marcio Sales over 11 years ago
Hey Koen,
I'll wait for the new version
thanks
Regards,
Marcio
Updated by Koen Deforche over 11 years ago
- Status changed from Resolved to Closed
Actions