CodePudding user response:
Restarting, troubleshooting, the key is the memory problem, problem is twofold:A, the operating system problems
The failures of the operating system itself,
Second, the server code problems
1, inner occupy, the release of the incomplete,
2, and the failure of the thread and the server program is thread mistakes I make miserably,
No code, imagined, are for reference only.
CodePudding user response:
Why each connection to a database connection, database connection usually just one or two long connection, and then through the queue service,CodePudding user response:
Memory is full or the number of connections is fullCodePudding user response:
Why don't you try to restart the SQL server server?CodePudding user response:
Even determines the SQL server run out of service due to handle problems,You also are problems of this kind of writing method,
Improved a little bit more simple, can will need to write the content, in a List,
In another thread, read the contents of the List, write operations, a TADOConnection done, also need not repeat creation,
CodePudding user response:
Suggestions don't create TADOConnection, but use, is a low global static TADOConnection, try,CodePudding user response:
This time, will long even database, because the program is running on the server side,Look from the phenomenon, should be a resource is exhausted,
After the turn off the process, to determine whether the process of program still exist?
If not, may be the cause of the database, but in the end, or your program problem,
If there is, may be program,
In a word, is to write program has a problem,
CodePudding user response:
Don't always create the connection, the Server using a static long connection, through the message or thread synchronization to operation,CodePudding user response:
The number of connections, I met