CORBA_HANDLER: server timeout minor:32 error causing Network Processor to restart
Last updated on SEPTEMBER 06, 2017
Applies to:Oracle Communications IP Service Activator - Version 7.2.0 and later
Information in this document applies to any platform.
This problem can occur on any platform.
The read timeout mechanism was triggering in the TCP connection method causing the Network Processor (NP) to terminate the connection. This was resulting in the broken pipe error on the policy server side. The broken pipe error is highlighted as a minor:32 error in the policy server logs.
If the policy server is restarting (going red in the GUI) when attempting to perform operations that involved large amounts of data it may be related to ORB TCP Read Timeouts
Transactions that cause operations to be performed on a large number of objects. An example would be performing a 'manage' on a few hundred devices.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms