FRM-92050

"FRM-92050 Failed To Connect to the Server" Error with Port Probing Security Tool [ID 1154303.1]

Applies to:

Oracle Applications Technology Stack - Version 12.0 to 12.1.3 [Release 12.0 to 12.1]
Oracle Applications Technology Stack - Version 10.1.2 to 10.1.2.3 [Release 10.1]
IBM AIX on POWER Systems (64-bit)

Symptoms

In R12 forms socket mode environment,  Form server hangs and unable to create new forms sessions. This results in, FRM-92050 error when users are attempting to connect to Oracle Applications. Forms server needs to be bounced to resolve the error temporarily.

 

ERROR and stack trace

 

FRM-92050 FAILED TO CONNECT TO THE SERVER

 

java.net.ConnectException: Connection refused: connect

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.PlainSocketImpl.doConnect(Unknown Source)

at java.net.PlainSocketImpl.connectToAddress(Unknown Source)

at java.net.PlainSocketImpl.connect(Unknown Source)

 

truss output of spinning client processes 

 

 

naccept(3, 0x2FF17760, 0x2FF17740)

naccept(3, 0x2FF17760, 0x2FF17740) Err#72 ECONNABORTED

kioctl(1, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY

close(3) = 0 

kwaitpid(0x2FF17770, -1, 5, 0x00000000, 0x00000000) = 0

kfcntl(3, F_GETFL, 0x00000000) Err#9 EBADF

Attempting to set Non-blocking IO caused

kwrite(2, " A t t e m p t i n g t".., 40) = 40

kwrite(2, " : ", 2) = 2Bad file number

kwrite(2, " B a d f i l e n u m".., 15) = 15

 

naccept(3, 0x2FF1B760, 0x2FF1B740) Err#72 ECONNABORTED  => Error occurred

kioctl(1, 22528, 0x00000000, 0x00000000) Err#19 ENODEV

close(3) = 0                                            => Socket was closed without exception handling

 

Changes

Security tool (i.e. WebKeeper or nmap) has been recently configured  which pings the forms server to do health check.

 

For example 

nmap is configured and using below command to check forms server port availability. 

 

nmap -p portnumber hostname

nmap -sT -p portnumber hostname

 

The same error can be reproduced when "Web Keeper" used  as a port probing tool as well.

Cause

The cause of this problem has been identified in Bug 9886338>>  which provides fix to handle scanning of frmsrv port availability.>>

Solution

1. Apply Patch 9913966 on top of forms 10.1.2.3 by following readme of the patch.
2. Restart all midtier services.