On Thu, Apr 20, 2000 at 08:24:06AM -0700, Bill Trost wrote:
> Scott G. Miller writes:
> It seems the command-line client is not quiting after a
> request. It transfers the data and just stops.
>
> Can you be more precise -- which command-line client did you use, what
> command-line arguments (including the key you requested), what operating
> system, what JVM, what phase of moon?
>
> I suspect, however, that I am seeing roughly the same problem. Under
> Kaffe on FreeBSD,
> I get the following errors after the data has been transferred by
> RequestClient:
>
> Dumping live threads:
> `Thread-0' tid 0x82e3010, status SUSPENDED flags
> blocked at 0x82e2340 (0x82e3010->|)
> `gc' tid 0x81cb010, status SUSPENDED flags
> blocked at 0x8196dc0 (0x81cb010->|)
> `finaliser' tid 0x81c2010, status SUSPENDED flags
> blocked at 0x8196d90 (0x81c2010->|)
> Deadlock: all threads blocked on internal events
>
> I don't get the problem under JDK 1.1.8. I also noticed that a
> Kaffe-compiled client refuses to run under JDK ("Error loading class
> Freenet.client.RequestClient: Bad index into constant pool"), although
> the compiler used does not affect how the Kaffe VM behaves.
>
> It might be time to start naming threads, just to get a handle on this
> sort of bug (it's not the first time I have seen it).
I've seen the same problem, consistently, using the freenet_request script
with two arguments (maybe three, incl. -htl) key, and filename.
Linux, Blackdown 1.2.2, and sorry, I don't even know what month it is,
let alone what day it is.
David Schutt
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
