On Fri, Apr 27, 2001 at 08:27:23AM -0500, Joi Ellis wrote:
> I wrote off the IBM JVM last year after living with swing bugs and
> a broken debugger that dumped core every time I tried to use it. I
> deleted it off my machine after I spent a day crafting a reproducible
> test case for the debugge
dear all
I am using tomcat on linux. My servlet is in a classes subforder under
my home. When servlet run, I don't see the output from System.out.println
printed to the screen. What should I do in order to see the output. (Before
I was using NT, the output would be printed to the Dos windo
On Thu, 26 Apr 2001, Vladimir G Ivanovic wrote:
> Why don't you try IBM's JDK? The Volano test results show it to be a
> powerful performer, and coupled with jikes, it makes pretty nifty
> development environment. Seems like an all-around winner to me.
>
> But that may not solve your problem. I
On Thu, 26 Apr 2001, Vladimir G Ivanovic wrote:
> Why don't you try IBM's JDK? The Volano test results show it to be a
> powerful performer, and coupled with jikes, it makes pretty nifty
> development environment. Seems like an all-around winner to me.
Yes, but it has some very **nasty bugs**.
T
Why don't you try IBM's JDK? The Volano test results show it to be a
powerful performer, and coupled with jikes, it makes pretty nifty
development environment. Seems like an all-around winner to me.
But that may not solve your problem. I seem to remember some funkiness
having to do with signals a
I've been trying to write unit tests for a simple udp listener service.
When I use a HotSpot jvm, the tests pass. When I use native threads,
the tests pass. When I use green threads, or a classic JVM, the tests
fail.
The tests are braindead simple. Open a udp listen socket, open a send
socket
