Error: Accept on connect failed: Bad file number

[Traci Zee]

I get the following error 100 times and then it kills the thread.

[pdl :PDL :ERR /0:  main_res_in:09/25/2008 16:11:36] Accept on connect failed: Bad file number

[pti :sele:WARN/0:tcp_res_in_cmd:09/25/2008 16:11:36] Select returns -1 9: Bad file number

[pti :sele:ERR /0:tcp_res_in_cmd:09/25/2008 16:11:36] Bogus FD 25 in read list

[pti :sele:ERR /0:tcp_res_in_cmd:09/25/2008 16:11:36] Bogus FD 25 in except list

[pti :sele:ERR /0:tcp_res_in_cmd:09/25/2008 16:11:36] Warning # 101 on fd 25

[pti :sele:ERR /0:tcp_res_in_cmd:09/25/2008 16:11:36] Thread main_res_in is not cleaning up bad file descriptor 25

[pti :sele:ERR /0:tcp_res_in_cmd:09/25/2008 16:11:36] Sending Thread main_res_in a shutdown message.

[pdl :PDL :ERR /0:  main_res_in:09/25/2008 16:11:36] Accept on connect failed: Bad file number

[pdl :PDL :ERR /0:  main_res_in:09/25/2008 16:13:45] setsockopt NODELAY on socket failed: Invalid argument

I’m running the thread Multi-Server using Cloverleaf 5.5, Rev 1, on AIX 5.3.

Anyone know the cause and/or solution?

TIA,

Traci Zee

Emdeon Business Services

615.886.9329

Topic

[Tom Rioux]

Do you have some sort of tcl script on this thread that is reading from a file?

[Traci Zee]

Nothing file based.  It’s a pretty basic raw route with hl7Raw_Ack and a small tcl trx Id route determination that doesn’t happen to be referenced in the routing right now.  

The only interesting part is the Multi-Server protocol.  I am “Saving Client ID and Port to Driver Control” and saving IB messages to SMAT.

[Author]

Replies