Hi, Sorry that you got bitten by that bug but I believe it was fixed about 7 months ago. Heres the relevent cvs log
+++++++++++++++++++++++++++++++++++++++++++++++++++++++ revision 1.5 date: 2001/09/07 03:06:51; author: donaldp; state: Exp; lines: +2 -0 Make sure accept() calls are interupted frequently enough on win32. ---------------------------- revision 1.4 date: 2001/09/01 16:51:42; author: donaldp; state: Exp; lines: +6 -7 Threads are got from a pool and thus will never end. Thus when we were waiting for thread.join() it would wait indefinetly. Thus we now use monitors + wait()/notifyAll() to communicate between threads. +++++++++++++++++++++++++++++++++++++++++++++++++++++++ I am not sure if the above is the cause of your current woes but it sounds like it is. However if you want to take control of your project as you say then all you need do is ask for commit access and it will be granted. Then if you need to fix something you can fix it. As a side note just because it is in avalon does not mean there is any law stating that you have to use it. Some of the components I don't use because I don't like their design and some I don't use because they drag in too many dependencies or are not stable or whatever. If you have problems with particular components then you should feel free to fix them or use alternatives. On Thu, 18 Apr 2002 16:18, Paul Hammant wrote: > Serge, > > As an Avalon advocate, who has none of the problems you mention before, > I think I should offer my help. Your cry for help is heard. > > At the risk of contradicting you, Avalon comps have been released : - > http://freshmeat.net/projects/avalon/?topic_id=810 > Avalon-Cornerstone has not. Avalon-Phoenix is currently shipping a beta. > > Regards, > > - Paul H > > > I don't know if I can take much more of Avalon. I've lost so much > > interest in working on James because of the problems that arise from > > using Avalon, and am nearing my last straw this afternoon. > > > > The latest problem with our use of Avalon is that if you have any open > > connections when you try to stop the JVM, it hangs and has to be > > forcibly stopped. I thought the whole reason behind migrating to > > Avalon was so that we didn't have to deal with underlying threading, > > configuration, object pooling, database sources, connection handling, > > logging, and other server related issues. Unfortunately, none of the > > features are implemented that wonderfully, the platform continually > > moves from one pre-alpha release to another, there are regular huge > > arguments on the dev mailing list about what latest pre-pre-alpha > > component should be added next to the already uncertain platform, and > > meanwhile the James project is stuck working again and again on stuff > > that was already working before we ported to Avalon years ago. > > > > Sorry, I'm just really really tired of this stuff. Since there aren't > > any real official releases of Avalon, should we just do another > > snapshot? Or maybe just branch the code, import it into James so we > > can gain control over our project again? -- Cheers, Peter Donald -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
