db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shane Powell (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1054) Starting Derby with the NetServlet inside of tomcat does not allow binding to non localhost interface.
Date Sat, 25 Feb 2006 00:40:54 GMT
Starting Derby with the NetServlet inside of tomcat does not allow binding to non localhost
interface.
------------------------------------------------------------------------------------------------------

         Key: DERBY-1054
         URL: http://issues.apache.org/jira/browse/DERBY-1054
     Project: Derby
        Type: Bug
  Components: Network Server  
 Environment: Gentoo & RedHat Linux. 
JDK 1.5.0.  
Tomcat 5.0.28
Derby 10.1
derby.war
    Reporter: Shane Powell


I like the idea of using the NetServlet with the derby.war file inside of tomcat to allow
Tomcat to start and stop my derby database.  This makes it quite easy for some of our less
than technical users.   However, the NetServlet.java file appears to have "localhost" hard
coded as the startup host.  This forced Derby to start listening ONLY on 127.0.0.1.  I tried
passing the -Dderby.drda.host parameter through the java startup of Tomcat, but it doesn't
appear to have any affect.  Ideally, the NetServlet.java class should allow for a "host" parameter
to be passed in via the web.xml file.  That way we can easily control the listening interface.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message