-
Enhancement
-
Resolution: Fixed
-
P3
-
1.2.1_04, 5.0
-
tiger
-
generic, sparc
-
generic, solaris_7, solaris_8
An increasing number of Unix daemons are being written in
Java using RMI. Normally daemons like this would be started using inetd or xinetd,which starts processes in response to requests over specific ports.
Unfortunately, processes that use RMI can't be started this way, since
there's (apparently) no way to convert a descriptor inherited by the
process from inetd into a socket that can be used for RMI. As a result,
daemons using RMI must be started at system boot time, whether or not
they will be needed.
divyang.desai@eng 2000-01-05
Java using RMI. Normally daemons like this would be started using inetd or xinetd,which starts processes in response to requests over specific ports.
Unfortunately, processes that use RMI can't be started this way, since
there's (apparently) no way to convert a descriptor inherited by the
process from inetd into a socket that can be used for RMI. As a result,
daemons using RMI must be started at system boot time, whether or not
they will be needed.
divyang.desai@eng 2000-01-05
- relates to
-
JDK-4673940 Java networking applications should be startable from inetd/xinetd
- Resolved