Re: java + X11 memory leak (a crazy idea)

1999-08-12 Thread Daniel W. Dulitz x108
Rob Clark writes: > Here's a crazy idea: the whole problem, as I see it, arises because > the JVM's garbage collector only knows of one resource pool, the > heap, when in fact there are other resource pools outside the JVM > that it should also concern itself with. [...] > > For example, sun could

Re: java + X11 memory leak

1999-08-12 Thread Daniel W. Dulitz x108
Chris Abbey writes: > So what part of garbage collection actually releases the resources > of an object? java/lang/Object.finalize(); The way gc frees up > resources is that it calls finalize on any object that it has > detected is garbage (is not reachable) before it goes through and > takes the

Re: Migrating Applets to Servlets

1999-07-26 Thread Daniel W. Dulitz x108
Nathan Meyers writes [in response to Matt Zagni]: > All applets are browser-based, unless there's some subtlety in your > statement I'm missing. But applets interact with users through a GUI... > windows, pointers, menus, etc. Imagine rewriting your applet without > being able to use any classes f

Re: netscape 4.61, Java, Redhat 6.0

1999-07-23 Thread Daniel W. Dulitz x108
Paul Ho writes: > No problem here. Netscape communicator 4.61 from Redhat rpm on > RedHat 6.0 with updates from (updates|rawhide).redhat.com Interesting. So 4.61 seems not to be the (only) culprit. However, 4.5, 4.6, and 4.61 all had nasty Java problems for me, under both RedHat 5.2 with update

Re: netscape 4.61, Java, Redhat 6.0

1999-07-23 Thread Daniel W. Dulitz x108
Nelson Minar writes: > >I've not had that many problems with Netscape and Java. > > Could it really just be me? No. I finally had to disable Netscape 4.61 Java. I'd say 75% of all applets cause either the 100%-CPU-utilization problem or the instant-Netscape-crash problem. Best, daniel dulitz

Re: Bad file descriptors?

1999-07-22 Thread Daniel W. Dulitz x108
Dustin Lang writes: > Can someone tell me what this means: > > java.io.IOException: Bad file descriptor > at java.io.FileInputStream.readBytes(Native Method) > at java.io.FileInputStream.read(Compiled Code) > ... Sorry, I can't say without looking at the native method. But

Re: Java and Endianess

1999-05-07 Thread Daniel W. Dulitz x108
Bernd Kreimeier writes: > The only statement I found is in the VMspecs, basically > saying: > > Multibyte data items are always stored in big-endian > order, where the high bytes come first. > > Does this apply to "int" in memory? Is the VM on Linux > using big endian and swaps when it int

Re: Big-Endians

1999-04-21 Thread Daniel W. Dulitz x108
> ---On Wed, 21 Apr 1999 13:54:02 -0700 (PDT), Jeffrey Radick said > > If a Java app exchanges data with data from a non-Java program > > then it must face platform-specific endianness issues. > > Does a program fail to be 100% Pure Java if it exchanges > > data with a non-Java program? (I'm ask

Re: jEdit/Blackdown 1.1.7a

1999-04-09 Thread Daniel W. Dulitz x108
Christopher Rowan writes: > So I tried something crazy for comparison purposes: I ran jEdit on > NT4.0sp3 with Sun's jdk1.1.7B. It didn't crash even once in 8 hours. > And the performance on a Pentium 200/64MB was much better (except for > startup time) than with Linux on a Pen II 300/196MB. >

Re: system limits

1999-03-18 Thread Daniel W. Dulitz x108
[EMAIL PROTECTED] writes: > I'm sure I saw a note on this list about increasing the limit on > file descriptors and/or processes by modifying the kernel > source, but I can't seem to find one. Can someone point me > in the right direction? In the 2.0 series, /usr/src/linux/include/linux/tasks.h

re: Electrical Fire

1999-02-26 Thread Daniel W. Dulitz x108
Nick Bailey writes: > "In the interim, there had been some bit-rot and, after some effort, the > code will compile, but not > run." (on the Unix page). They are working on it, though. The > Microsoft version works fine. Good luck to porting team, though! > > I've no criticism on the Netscape/Mo

Re: Electrical Fire

1999-02-26 Thread Daniel W. Dulitz x108
Nick Bailey writes: > ...but have you read the Unix page? > > http://www.mozilla.org/projects/ef/unixbuild.html > > Another one in the eye for Linux users wanting efficient Java. Also, > the main page says "get JDK 1.2, then..." I don't understand how this is a problem. They say you need JDK

Re: JavaLinux for servlets [off-topic]

1999-02-16 Thread Daniel W. Dulitz x108
Kevin Hester writes: > John Goerzen writes: > > I would certainly not use Java for CGI. libapache-mod-perl, FastCGI, etc. > > if necessary. > > I'd definitely encourage anyone to use servlets with wild abandon. So easy > and clean - I haven't had to write CGI cruft in over a year. In exchange

Re: simple imput from command line

1999-02-14 Thread Daniel W. Dulitz x108
cobra writes: > IF my question is too silly please ignore it. Well, you sent it twice. It's pretty silly, and it's off topic, but now I'm worried that if everyone ignores it you'll keep sending it. > I'd need a translation for basic : INPUT "AGE";A import java.io.*; public int getIntegerF

Re: java programming

1999-02-14 Thread Daniel W. Dulitz x108
alexander lang writes: > Does anyone know if one is allowed to initialize static final variables > within the "try" clause of a static initializer block? > > (eg. > static final int x; > static{ > try > { > x = 5; > } > catch(exc

Re: finalizer()

1999-01-05 Thread Daniel W. Dulitz x108
John Summerfield writes: > Someone mentioned offline (please, all, keep discussion ON the list) that > it's possible to force garbage collection. My code has the necessary > statements to do that (two versions that I found). If (as someone else indicated) Sun's JVM uses a conservative garbage col

Re: Deprecated `Thread.stop()' in forthcoming JDK 1.2. Why?

1998-11-13 Thread Daniel W. Dulitz x108
Pavel Tolkachev writes: > > I read somewhere that Thread.stop() is now deprecated. > Yes, and it's very good. > > Now how on earth do we stop a thread ? > Just allow it to exit from its run() method. So there is no way to stop a thread that is waiting for user input? daniel dulitz Valley

pipe question

1998-11-09 Thread Daniel W. Dulitz x108
This is a general Java question, although it might (possibly) point to a bug in the v5 port or in 1.1.6 itself. Under what circumstances does PipedInputStream.read() or PipedOutputStream.write() throw an IOException for "Pipe broken?" Intuitively, what I think should happen is that a pipe throw