Warning in the Orbix locator log: (IT_ATLI2_IP:101) W - ATLI2 failure receiving data with minor_code 1230242771 occurred in TCPConnectionImpl::readable()

Dominique Sacre · 2013-05-17T17:43:00+00:00

Summary Warning in the Orbix locator log: (IT_ATLI2_IP:101) W - ATLI2 failure receiving data with minor_code 1230242771 occurred in TCPConnectionImpl::readable() Article Number 14086 Environment Orbix 6.x All Supported Operating Systems Question/Problem Description Getting the following warning in the Orbix locator log: (IT_ATLI2_IP:101) W - ATLI2 failure receiving data with minor_code 1230242771 occurred in TCPConnectionImpl::readable() locator log get filled with the following error messages: (IT_ATLI2_IOP:105) W - ATLI2 Failure occurred on connection to 10.161.9.150.48549: ::recvmsg() failed in TCPConnectionImpl::readable() with: Connection reset by peer Clarifying Information Error Message locator log get filled with the following error messages: (IT_ATLI2_IOP:105) W - ATLI2 Failure occurred on connection to 10.161.9.150.48549: ::recvmsg() failed in TCPConnectionImpl::readable() with: Connection reset by peer Defect/Enhancement Number Cause These messages generally show up in a CORBA service/server log when a client ungracefully disconnects from your server, where the client ORB doesn't send a GIOP CloseConnection message. It's a reasonably harmless message, basically meaning that at some point the transport tried to read/poll for data off of a particular file descriptor and found it closed. Resolution This message is considered warning message , not an error. CORBA clients/servers and services should still work fine, even with this warning message To prevent these messages from filling up logs, there's two possible solutions: Modify the default log filter settings of the CORBA services (internally the ORB uses "*=WARN ERR FATAL") to "*=ERR FATAL". Check the client code and make sure it's properly shutting down it's ORB instance. Typically you'd see these messages when a client creates a connection to a server and makes some invocations and then exits without calling CORBA::ORB::shutdown()/CORBA::ORB::destroy(), or in the case of Java it'd be CORBA::ORB::shutdown(1), where the wait for completion flag is set to true. Again, if a server/service tries to use an FD that is closed on the other end, it will print this warning, and keep on operating normally. Workaround Notes Attachment Created date: 06 September 2011 Last Modified: 13 February 2013 Last Published: 12 May 2012 First Published date: 09 September 2011 #KnowledgeDocs#Orbix

Forum|Forum|12 years ago
May 17, 2013
0 replies
1 view

D

Dominique Sacre
Rocketeer

Summary	Warning in the Orbix locator log: (IT_ATLI2_IP:101) W - ATLI2 failure receiving data with minor_code 1230242771 occurred in TCPConnectionImpl::readable()
Article Number	14086
Environment	Orbix 6.x All Supported Operating Systems
Question/Problem Description	Getting the following warning in the Orbix locator log: (IT_ATLI2_IP:101) W - ATLI2 failure receiving data with minor_code 1230242771 occurred in TCPConnectionImpl::readable() locator log get filled with the following error messages: (IT_ATLI2_IOP:105) W - ATLI2 Failure occurred on connection to 10.161.9.150.48549: ::recvmsg() failed in TCPConnectionImpl::readable() with: Connection reset by peer
Clarifying Information
Error Message	locator log get filled with the following error messages: (IT_ATLI2_IOP:105) W - ATLI2 Failure occurred on connection to 10.161.9.150.48549: ::recvmsg() failed in TCPConnectionImpl::readable() with: Connection reset by peer
Defect/Enhancement Number
Cause	These messages generally show up in a CORBA service/server log when a client ungracefully disconnects from your server, where the client ORB doesn't send a GIOP CloseConnection message. It's a reasonably harmless message, basically meaning that at some point the transport tried to read/poll for data off of a particular file descriptor and found it closed.
Resolution	This message is considered warning message , not an error. CORBA clients/servers and services should still work fine, even with this warning message To prevent these messages from filling up logs, there's two possible solutions: Modify the default log filter settings of the CORBA services (internally the ORB uses "=WARN ERR FATAL") to "=ERR FATAL". Check the client code and make sure it's properly shutting down it's ORB instance. Typically you'd see these messages when a client creates a connection to a server and makes some invocations and then exits without calling CORBA::ORB::shutdown()/CORBA::ORB::destroy(), or in the case of Java it'd be CORBA::ORB::shutdown(1), where the wait for completion flag is set to true. Again, if a server/service tries to use an FD that is closed on the other end, it will print this warning, and keep on operating normally.
Workaround
Notes
Attachment