Skip to main content
Summary Received message "errno is -30975 (DB_RUNRECOVERY: Fatal error, run database recovery)"
Article Number 16812
Environment Orbix 6.3 UNIX
Question/Problem Description Received message "errno is -30975 (DB_RUNRECOVERY: Fatal error, run database recovery)"
Received message "ATLI2 failure caused by function ::setsockopt(SO_LINGER) failing with system error 22 ('Invalid argument')"
Service becoming unresponsive
Service showing database errors
Clarifying Information
Error Message
Defect/Enhancement Number
Cause The above messages can indicate a resource problem.
Resolution To limit the load on an Orbix service, we can restrict the number of connections made to and from it using the following configuration variables:

  plugins:iiop:incoming_connections:soft_limit
    Sets the number of connections at which IIOP begins closing incoming (server-side) connections. Defaults to -1 (disabled).

  plugins:iiop:incoming_connections:hard_limit
    Specifies the maximum number of incoming (server-side) connections permitted to IIOP. IIOP does not accept new connections above this limit. Defaults to -1 (disabled)

  plugins:iiop:outgoing_connections:soft_limit
    Specifies the number of connections at which IIOP begins closing outgoing (client-side) connections. Defaults to -1 (disabled).

  plugins:iiop:outgoing_connections:hard_limit
    Sets the maximum number of outgoing (client-side) connections permitted to IIOP. IIOP does not allow new outgoing connections above this limit. Defaults to -1 (disabled).
Workaround
Notes For more information on Orbix 6.3 configuration variables, please see our configuration reference guide:
http://supportline.microfocus.com/Documentation/books/Orbix/635/configuration reference.pdf
Attachment

Created date: 06 September 2011
Last Modified: 21 May 2013
Last Published: 26 June 2012
First Published date: 10 September 2011


#KnowledgeDocs
#Orbix