Bad bad service :-(
-
I am sunk in misery now. I have a program running as a service. It opens a TCP port [Winsock only/no CSocket stuff] and listens on it. Once a TCP connection is made it does some stuff which included inserting into an MS Access mdb. I use CDatabase for it. Now I have an unusual problem. After 2-3 days of running, the service suddenly starts hogging system resources. My machine crawls to a slow slow pace and I can't even move the mouse properly. If I stop and restart the service, with some difficulty given the system condition, it get's okay again. I am confused as to what's going on. What's funny is that for the last 2 days I haven't even connected to the TCP port. It was simply running blindly. The moment a client connects I use AfxBeginThread to start a thread that processes the TCP connection. Now what I feel is that the accept call fails and thus I am actually starting a thread and passing to it a bad SOCKET. I am not checking whether the SOCKET is okay. But what saddens me no end is the fact that this shouldn't be happening. Wht should accept fail? I thought accept would block and block and block and block and block and block and block till a connection is made :(( Regards Sad-Nish :(
Regards, Nish Native CPian. Born and brought up on CP. With the CP blood in him.
-
I am sunk in misery now. I have a program running as a service. It opens a TCP port [Winsock only/no CSocket stuff] and listens on it. Once a TCP connection is made it does some stuff which included inserting into an MS Access mdb. I use CDatabase for it. Now I have an unusual problem. After 2-3 days of running, the service suddenly starts hogging system resources. My machine crawls to a slow slow pace and I can't even move the mouse properly. If I stop and restart the service, with some difficulty given the system condition, it get's okay again. I am confused as to what's going on. What's funny is that for the last 2 days I haven't even connected to the TCP port. It was simply running blindly. The moment a client connects I use AfxBeginThread to start a thread that processes the TCP connection. Now what I feel is that the accept call fails and thus I am actually starting a thread and passing to it a bad SOCKET. I am not checking whether the SOCKET is okay. But what saddens me no end is the fact that this shouldn't be happening. Wht should accept fail? I thought accept would block and block and block and block and block and block and block till a connection is made :(( Regards Sad-Nish :(
Regards, Nish Native CPian. Born and brought up on CP. With the CP blood in him.
I had a simmilar problem, but it related to the Access database and i wasn't using a socket connection. It turned out that the ODBC driver you need to set up on the ODBC Cad 32 was out of date and the program just sat there chewing up processing time and ram... I don't know if this is your problem, but you could try to look at Access connection for the fault. Good Luck Dor
-
I had a simmilar problem, but it related to the Access database and i wasn't using a socket connection. It turned out that the ODBC driver you need to set up on the ODBC Cad 32 was out of date and the program just sat there chewing up processing time and ram... I don't know if this is your problem, but you could try to look at Access connection for the fault. Good Luck Dor
Thanks Dor. What puzzles me is that when I am inserting, no probs at all. But I leave it idle for a couple of days and this happens :-( Nish p.s. I have added the check to see that the socket accept(...) returns is a valid socket. Hopefully, that should solve it :-)
Regards, Nish Native CPian. Born and brought up on CP. With the CP blood in him.