JDK-4673940 : Java networking applications should be startable from inetd/xinetd
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 1.4.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_8
  • CPU: generic,sparc
  • Submitted: 2002-04-24
  • Updated: 2017-05-16
  • Resolved: 2003-09-26
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 tigerFixed
Related Reports
Duplicate :  
JDK-4706492 - need way to create Socket from stdin
Relates :  
JDK-4071045 - I need to be able to pass in a bound socket to a java application
Relates :  
JDK-5100617 - Java launcher should allow option to specify alternate process name
Relates :  
JDK-4295885 - RMI applications should be startable from inetd
Relates :  
JDK-6189256 - Inability to launch Java from inside ClearCase
Description
This RFE is being filed because RFE 4295885 (considered important for Tiger) depends on this feature.

RFE 4295885 (RMI applications should be startable from inetd) describes
the issue that RMI applications can't be launched via inetd/xinetd.  There is a
more general problem that a Java networking application (which includes
RMI applications) can't be launched via inetd.  A solution to the general 
problem needs to be addressed first before 4295885 can be addressed.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b22
14-06-2004
PUBLIC COMMENTS This RFE is being filed because RFE 4295885 (considered important for Tiger) depends on this feature. RFE 4295885 (RMI applications should be startable from inted) describes the issue that RMI applications can't be launched via inetd. There is a more general problem that a Java networking application (which includes RMI applications) can't be launched via inetd. A solution to the general problem needs to be addressed first before 4295885 can be addressed. Background [mostly from 4295885]: An increasing number of Solaris daemons [WBEM/Common System Management Web Console] are being written using Java-based networking applications that use either Java sockets or socket-based technology such as RMI. Normally daemons like this would be started using inetd which starts processes in response to requests over specific ports. Currently, Java networking applications can't be launched via inetd, since there's no way to convert a file descriptor inherited by the process from inetd into a server socket that can be used by the application. As a result, daemons using Java networking must be started at system boot time, whether or not they will be needed. This hurts boot performance and wastes memory and swap space, since often these services aren't used at all. Also customers can't configure (i.e., disable) these services in the normal way they're used to configuring networking services (editing /etc/inet/inetd.conf).
10-06-2004
EVALUATION This requirement has been address in tiger through the addition of the following methods :- java.lang.System.inheritedChannel() to return a Channel inherited from whatever ceated the Java virtual machine. A similiar SPI method has been added to java.nio.channels.spi.SelectorProvider to return the inherited channel. This feature has been putback for tiger b22. ###@###.### 2003-09-23
23-09-2003