United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-4673940 Java networking applications should be startable from inetd/xinetd
JDK-4673940 : Java networking applications should be startable from inetd/xinetd

Details
Type:
Enhancement
Submit Date:
2002-04-24
Status:
Resolved
Updated Date:
2003-09-26
Project Name:
JDK
Resolved Date:
2003-09-26
Component:
core-libs
OS:
solaris_8
Sub-Component:
java.net
CPU:
sparc,generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
1.4.0
Fixed Versions:
5.0 (tiger)

Related Reports
Duplicate:
Relates:
Relates:
Relates:
Relates:

Sub Tasks

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
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
                                     
2003-09-23
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).
                                     
2004-06-10
CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
tiger

FIXED IN:
tiger

INTEGRATED IN:
tiger
tiger-b22


                                     
2004-06-14



Hardware and Software, Engineered to Work Together