Ok, the thread wasn't dying... simply blocked. I was not able to
reproduce the error. Now I get a class not found exception. In my
further tests the thread seemed to block on calling the constructor
which is logical because a class used in a member wasn't found.
>
>
> Threads don't just go away without a trace. :-) Its low
> tech, but try
> going through the code and adding
> debug output every couple lines to track down exactly where
> the thread
> is dying. More than likely it
> is blocking someplace rather than dying??? Not sure what
> your class is
> doing exactly that would cause
> this because of a missing jar. It is possible that someone has a
> try{}catch without a propper logging
> someplace, but I doubt it. (If so, someone needs to be thwapped :-)
>
> Do try to find out where the thread was going though. If it is an
> avalon problem, it needs to be fixed.
>
> In addition to placing debug output in the NBIOAcceptor construction,
> try modifying your method like
> this to make sure that nothing is being thrown and being
> ignored higher
> up. Just remember to take it out.
>
> public Acceptor createAcceptor()
> {
> try
> Acceptor acceptor = new NBIOAcceptor();
> m_acceptors.add(acceptor);
> return acceptor;
> }
> catch (Throwable t)
> {
> t.printStackTrace();
> }
> }
>
> More info?
>
> Cheers,
> Leif
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
