his problem is most likely not caused by exceeding the maximum
number of fds, but by kaffe closing a file descriptor prematurely.
If an fd is closed, the corresponding entry in java.io.Fd is set to
-1, subsequent attempts will result in a "bad fd message".
Specifically, Kaffe does not properly implement in/out streams for
URLConnections. If you try JMeter, you'll see the same problem.
- Godmar
>
>
> Hello,
>
> I am working with a person who is trying to run a program developed with
> Sun's JDK under Kaffe and is having problems (see questions below). I know
> almost nothing about Kaffe or Java so perhaps one of you may be able to
> answer these questions. If there's anything else you need let me know.
>
> RedHat Linux 5.2, kaffe-1.0.b2-2 (comes with RedHat), kernel 2.2.5
>
> Thanks for the help...
>
> --
> Michael Hamblin http://www.utdallas.edu/~michaelh/
> [EMAIL PROTECTED] http://www.ductape.net/
> UTD Linux User Group Engineering and Computer Science Support x2997
>
> ---------- Forwarded message ----------
> > On Fri, 23 Apr 1999, Nathanael P Altice wrote:
> >
> > > My chatroom works well, and I really appreciate your help. The only
> > > glitch is a bad file descriptor error every once in a while at random
> > > times. I was wondering what the maximum number of connections for a
> > > socket is and also what causes it to destroy the socket (ie. what will
> > > cause it to get rid of the server socket file descriptor?) I'm wondering
> > > if some of these things are causing my bad file descriptor error. I
> > > appreciate any information that you can give. Thanks.
>
>
