Bad file number

From: Alistair McKeown (Alistair.Mckeown@jacobsrimell.com)
Date: Thu Mar 10 2005 - 03:40:27 EST


Hi Gurus,

                Although the initial cause of my problem isn't directly
related to Solaris, I think altering a system configuration might help it.
We currently have a customer who is running are software on different
machines which communicate with each other through CORBA. Yesterday corba
completely locked up and also JRUN and I got the following error in the
orbixd.log, both machines are running Solaris 8.

On one server it says

AMSAPS03

[orbixd: Bad connection attempt: rejected! ]
[ Exception was 10082-- Communication failure
  - read error
           Reason: Bad file number
            (Possibly your target server has crashed/exited)
  [Completion status : COMPLETED_NO]
[ Continuing..... ]

And on the other server it says

AMSAPS06

[orbixd: redirecting request to NS on port 1591]
[orbixd: Bad connection attempt: rejected! ]
[ Exception was 10082-- Communication failure
  - read error
           Reason: Connection reset by peer
            (Possibly your target server has crashed/exited)
  [Completion status : COMPLETED_NO]
[ Continuing..... ]

So does anyone know what 'bad file number' means? Is this to do with file
descriptors? There wasn't anything in the /var/adm/messages log so this must
be a application specific error, I'm not sure. Just would like to know what
bad file number means.

Regards,

Alistair Mckeown

Jacobs Rimell Ltd.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:19 EDT