Question About IceGrid

haykinhaykin Member Haijin YingOrganization: Shanghai Baosight Co.Project: iPlature developed by us used in steel industory
hi
IceGrid had some error for unknow reason in my application after it run some days. it happened some times. The error information as follows:

icegridnode: error: execption in 'IceGrdi.Registry.Admin.ThreadPool':
.\ThreadPool.cpp:274: Ice::SocketException:
socket exception: WSAECONNRESET

icegridnode: error: execption in 'IceGrdi.Registry.Admin.ThreadPool':
.\ThreadPool.cpp:274: Ice::SocketException:
socket exception: WSAECONNRESET

icegridnode: error: execption in 'IceGrdi.Registry.Admin.ThreadPool':
.\ThreadPool.cpp:274: Ice::SocketException:
socket exception: WSAECONNRESET

i would appreciate it if someone could explain it in details.


* Ice version : 3.1.1
* Compiler version : Visual Studio 2005
* Operating system : Windows server 2003
ice.JPG 75.5K

Comments

  • benoitbenoit Rennes, FranceAdministrators, ZeroC Staff Benoit FoucherOrganization: ZeroC, Inc.Project: Ice ZeroC Staff
    Hi,

    This error shouldn't occur under normal circumstances. It indicates that the network connection used internally by the Ice thread pool has been forcefully closed. This connection is established over the loopback interface for internal purposes (it's used to interrupt the select() system call).

    Could some network related settings have been changed on the machine when this error started to occur?

    Ice 3.1.1 is quite an old version, did you consider upgrading? The latest Ice version doesn't rely anymore on select() and this internal socket. It's now using completion ports and as a result it also scales a lot better for large numbers of clients. So if possible, the best would be to upgrade to Ice 3.4.1.

    Cheers,
    Benoit.
  • haykinhaykin Member Haijin YingOrganization: Shanghai Baosight Co.Project: iPlature developed by us used in steel industory
    the information when icegridnode start

    hi
    thanks for your reply.

    When the icegridnode start, it alway display some wrong message.
    [ icegridnode: Object: removed object 'IceGrid/Admin' ]
    [ icegridnode: Object: added object 'IceGrid/Admin ' ]
    [ icegridnode: Object: removed object 'IceGrid/SessionManager' ]
    [ icegridnode: Object: added object 'IceGrid/SessionManager' ]
    ... ...
    [ icegridnode: Locator: couldn't resolve adapter 'IceStrom.TopicManager' endpoints:
    IceGrid::NodeUnreachableException:
    node: MainNode
    reason: the node is not active ]
    ... ...
    [ icegridnode: Acitvator: activating server '0Strom' ]
    ... ...
    (normally loading server)
    Attachment not found.
  • haykinhaykin Member Haijin YingOrganization: Shanghai Baosight Co.Project: iPlature developed by us used in steel industory
    warning from icegirdnode

    in additions, warning occured some times, though the applicatin worked well.
    icegridnode: warning: thread pool 'IceGrid.NodeThreadPool' is runing low on the threads
    Size=1, SizeMax=10, SizeWarn=8
    Attachment not found.
  • benoitbenoit Rennes, FranceAdministrators, ZeroC Staff Benoit FoucherOrganization: ZeroC, Inc.Project: Ice ZeroC Staff
    Hi,

    Those traces don't indicate anything abnormal or something which could be related to the original problem. It is expected that some object adapter endpoints can't be resolved if the node hosting the server is not reachable. Are you still seeing the original problem? When it occurs, are the traces always about the 'IceGrid.Registry.Admin.ThreadPool' and is it only the administrative functionality of the registry which is affected (can client still resolve proxies with the IceGrid registry locator)?

    Cheers,
    Benoit.
Sign In or Register to comment.