debug: new socket accepted

Several times, I got many many messages like this. Then the client can not use the sockd service. but i can see the port when i type netstat -na,

after i restart sockd , it works fine. I have met this issue several times, Is there anyone met the same issue ?

[03/Jan/2007:12:35:05] 000 debug:new socket accepted[4536]

[03/Jan/2007:12:35:32] 000 debug:new socket accepted[4537]

[03/Jan/2007:12:35:54] 000 debug:new socket accepted[4538]

[03/Jan/2007:12:35:54] 000 debug:new socket accepted[4539]

[03/Jan/2007:12:35:55] 000 debug:new socket accepted[4540]

[03/Jan/2007:12:39:33] 000 debug:new socket accepted[4541]

[03/Jan/2007:12:39:38] 000 debug:new socket accepted[4542]

[03/Jan/2007:12:41:35] 000 debug:new socket accepted[4543]

[03/Jan/2007:12:41:35] 000 debug:new socket accepted[4544]

[03/Jan/2007:12:44:07] 000 debug:new socket accepted[4545]

[03/Jan/2007:12:44:07] 000 debug:new socket accepted[4546]

[03/Jan/2007:12:45:36] 000 debug:new socket accepted[4547]

[03/Jan/2007:12:45:36] 000 debug:new socket accepted[4548]

[03/Jan/2007:12:47:19] 000 debug:new socket accepted[4549]

[03/Jan/2007:12:47:19] 000 debug:new socket accepted[4550]

[03/Jan/2007:12:48:38] 000 debug:new socket accepted[4551]

[03/Jan/2007:12:48:38] 000 debug:new socket accepted[4552]

[03/Jan/2007:12:51:09] 000 debug:new socket accepted[4553]

[03/Jan/2007:12:51:09] 000 debug:new socket accepted[4554]

[03/Jan/2007:12:54:09] 000 debug:new socket accepted[4555]

[03/Jan/2007:12:54:10] 000 debug:new socket accepted[4556]

[03/Jan/2007:12:54:49] 000 debug:new socket accepted[4557]

[03/Jan/2007:12:54:49] 000 debug:new socket accepted[4558]

[03/Jan/2007:12:54:54] 000 debug:new socket accepted[4559]

[03/Jan/2007:12:54:54] 000 debug:new socket accepted[4560]

[03/Jan/2007:12:55:32] 000 debug:new socket accepted[4561]

[03/Jan/2007:12:55:32] 000 debug:new socket accepted[4562]

[03/Jan/2007:12:56:15] 000 debug:new socket accepted[4563]

[03/Jan/2007:12:56:15] 000 debug:new socket accepted[4564]

[03/Jan/2007:12:58:17] 000 debug:new socket accepted[4565]

[03/Jan/2007:12:58:17] 000 debug:new socket accepted[4566]

[03/Jan/2007:12:59:28] 000 debug:new socket accepted[4567]

[03/Jan/2007:12:59:28] 000 debug:new socket accepted[4568]

[03/Jan/2007:13:13:15] 000 debug:new socket accepted[4569]

[03/Jan/2007:13:13:16] 000 debug:new socket accepted[4570]

[03/Jan/2007:13:18:31] 000 debug:new socket accepted[4571]

[03/Jan/2007:13:18:31] 000 debug:new socket accepted[4572]

[03/Jan/2007:13:40:20] 000 debug:new socket accepted[4573]

[4033 byte] By [imtaconfig.jara] at [2007-11-26 14:04:18]
# 1

I believe that this occurs when no sockd worker threads are available. Use netstat to check how many connections to the sockd port (1080 by default) there are. You can increase the number of worker threads if you are simply running out. The default is 40.

There is also a bug in the 4.0.3 sockd where sockets are stuck in a CLOSE_WAIT state. This ties up worker threads. The problem seems related sockd handling UDP connection requests. Stopping and starting sockd closes all the sockets that sockd has opened which clears the CLOSE_WAIT state. We currently have a ticket open with Sun on this issue.

aberry01a at 2007-7-8 1:48:17 > top of Java-index,Web & Directory Servers,Web Servers...
# 2

The worker threads numbers in my configuration is 300. And i am puzzling with the worker threads, if there are about over 200 persons using the sockd server, what is the number should i set ?

I have wrote a script, and monitor the log of sockd, if there is no new data is written in, the sockd will be restart, Is it a good solution?

Message was edited by:

imtaconfig.jar

imtaconfig.jara at 2007-7-8 1:48:17 > top of Java-index,Web & Directory Servers,Web Servers...