Archived
This forum has been archived. Please start a new discussion on GitHub.
what has happened with filedescriptor
I am a Java programmer and find the following exception throws by some c++ code. Which causes the trouble, c++ code or Icegrid?
_________________________________________________________________
ICE_ERROR: filedescriptor 1120 not registered with `Ice.ThreadPool.Server'
ICE_ERROR: filedescriptor 1036 not registered with `Ice.ThreadPool.Server'
ICE_ERROR: filedescriptor 1046 not registered with `Ice.ThreadPool.Server'
ICE_ERROR: filedescriptor 1054 not registered with `Ice.ThreadPool.Server'
ICE_ERROR: filedescriptor 1076 not registered with `Ice.ThreadPool.Server'
_________________________________________________________________
ICE_ERROR: filedescriptor 1120 not registered with `Ice.ThreadPool.Server'
ICE_ERROR: filedescriptor 1036 not registered with `Ice.ThreadPool.Server'
ICE_ERROR: filedescriptor 1046 not registered with `Ice.ThreadPool.Server'
ICE_ERROR: filedescriptor 1054 not registered with `Ice.ThreadPool.Server'
ICE_ERROR: filedescriptor 1076 not registered with `Ice.ThreadPool.Server'
0
Comments
-
Its not really clear what you are doing to cause this problem. You are spawning java only applications from an ice grid node? Or are you spawning C++ applications also? Can you regularly reproduce this issue?0
-
It is a spawned C++ applications. It has no regulation. It reproduced by two program writen by two other guys. I got two message like this:
"ACE|Jun 22 15:27:49.836 2006@LM_ERROR@ICE_ERROR: filedescriptor 1120 not registered with `Ice.ThreadPool.Server'
ACE|Jun 22 15:27:49.836 2006@LM_ERROR@ICE_ERROR: filedescriptor 1046 not registered with `Ice.ThreadPool.Server' ..."
"ACE|Jun 25 23:03:21.667 2006@LM_ERROR@ICE_ERROR: exception in `Ice.ThreadPool.Server':
ThreadPool.cpp:353: Ice::SocketException:
socket exception: Bad file descriptor"
And then the programs drop into a dead loop. It seems easy to happen in the time when the network load is the most heavy.0 -
my config file for registry
IceGrid.InstanceName=MyGrid
#
# IceGrid registry configuration.
#
IceGrid.Registry.Client.Endpoints=default -p 22000
IceGrid.Registry.Server.Endpoints=default
IceGrid.Registry.Internal.Endpoints=default
IceGrid.Registry.Admin.Endpoints=default
IceGrid.Registry.Data=/opt/mysee/var/icegridregistry
# new configuration
IceGrid.Registry.Admin.ThreadPool.Size=50
IceGrid.Registry.Admin.ThreadPool.SizeMax=100
IceGrid.Registry.Admin.ThreadPool.SizeWarn=10
#IceGrid.Registry.AdminSessionTimeout=3600
IceGrid.Registry.Client.ThreadPool.Size=50
IceGrid.Registry.Client.ThreadPool.SizeMax=100
IceGrid.Registry.Client.ThreadPool.SizeWarn=10
IceGrid.Registry.Internal.ThreadPool.Size=100
IceGrid.Registry.Internal.ThreadPool.SizeMax=200
IceGrid.Registry.Internal.ThreadPool.SizeWarn=10
#IceGrid.Registry.NodeSessionTimeout=3600
IceGrid.Registry.Server.ThreadPool.Size=100
IceGrid.Registry.Server.ThreadPool.SizeMax=200
IceGrid.Registry.Server.ThreadPool.SizeWarn=100 -
Hi,
On which platform/OS do you get these errors and which Ice version do you use? Also, are you linking your application with any other libraries than Ice?
The best way to investigate this error would be to send us a small self-compilable example that we can use to reproduce the error. Would it be feasible to send us such a test case?
Thanks,
Benoit.0 -
OS: Dieban
Ice Version: 3.01
libraries include: ACE
I think it is very difficult to reproduce the error in your machines. Because I didn't find the problem appeared in LAN. And only when the network load is very heavy, it is frequent. In addition, to config our application is very complicated and needs serveral applications to cooperate with.
It may be linked the threadpool as I noticed that other guys also have similar trouble(in bug reports).0 -
Mmm, I can't find similar reports for this error, could you point us to the specific threads?
I'm afraid, it's difficult to help you with this issue if we can't easily reproduce it. We also don't know ACE very well and the side effects it could potentially cause. Are you perhaps doing anything unusual in your server (such as canceling threads, forking processes for example)?
Cheers,
Benoit.0 -
one of my staff said this may be due to the limitation of thread.
and the following is the link
http://www.zeroc.com/vbulletin/showthread.php?t=16330