Here is another data point on RMI and JServ. I've been using RMI
extensively in JServ for several months under a limited, but similar,
range of system configurations:
Machines: Ultra 1, E3000 Ultra 1, E3000
O/S: Solaris 2.5.1 Solaris 2.5.1
Apache: 1.3.4 1.3.6
JServ: 1.0b2, 1.0b3 1.0b4
JDK: 1.1.7B (production) 1.1.7B (production)
The only RMI-related problem I've encountered is RMI's (known, but
not terribly well-documented) inability to handle Strings of
length > 64000. In this situation, however, I believe you should
get an RMI exception, probably an Unmarshalling exception.
Also, I didn't quite understand the original problem description:
>After about 3 RMI calls in the init method, Apache JServ crashes. I get
>a message like this when I restart:
>
>[18/05/1999 09:54:45:027] (EMERGENCY) wrapper: JServ (14549) didn't die
>nicely, killing it
What is meant by "JServ crashes"? If the wrapper was forced to kill
a JServ process on restart (as the error above seems to indicate),
then doesn't this suggest that JServ was still running? The fact
that the browser timed out (rather than reporting an empty HTTP
response) likewise implies that JServ was still doing _something_.
Perhaps I'm just used to a different interpretation of "crash," but
this sounds more like a "hang."
Jonathan
Center for Bioinformatics, UPenn.
-- --------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
