- From: Anselm Baird-Smith <abaird@w3.org>
- Date: Mon, 7 Oct 1996 11:57:51 -0400 (EDT)
- To: "Bruce Nelson (bnelson)" <bnelson@www.css.filenet.com>
- Cc: www-jigsaw@w3.org
Bruce Nelson writes: > Anselm.. Thanks for your efforts to get alpha3 released! > > We are started to taked a look at the new release last night > and set it up with the same environment that we had run alpha1 > (IBM AIX Java 1.02 with JIT and green-threads). We came accross an > interesting problem -- (bug?) that is either Jigsaw or Java related. > Alpha3 runs stable (but kind of slow) with regular Java, > with JIT enabled it still runs stable - and fast - no problems, > but when green-threads are enabled the socket handling on network > connections gets very wierd (strange) - > > The problem: > > with green-threads enabled the browser will make the TCP connection but can't > get its URI accross to the server -- you end up with a "Document Contains > no data" error (from Netscape for example) which tells me the connection was > dropped. If you telnet to that same host on the http port and enter a URL by > hand -- it works great -- (if you dont mind entering URIs ;-)) -- This is > not a big issue for us. The original intent of using green-threads was to > boost performance on Jigsaw and our Sybase drivers.... but as IBM says in > thier documentation "some applications may not work with green-threads". Unfortunatelly I don't know enough about IBM work on green threads. The only thing I can say is that if you have a mean to avoid green thread, avoid them like a plea ;-) [They are slowwww] Anselm.
Received on Monday, 7 October 1996 11:58:02 UTC