Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <27236690.1178552955568.JavaMail.jira@brutus>
Date: Mon, 7 May 2007 08:49:15 -0700 (PDT)
From: "Bryan Pendleton (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-1054) Starting Derby with the NetServlet
 inside of tomcat does not allow binding to non localhost interface.
In-Reply-To: <358850745.1140828054433.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Pendleton resolved DERBY-1054.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0
       Derby Info:   (was: [Patch Available])

Committed the code change to NetServlet and web.xml to
subversion as revision 535910, and committed the
documentation change to the Admin Guide to subversion
as revision 535912.

> Starting Derby with the NetServlet inside of tomcat does not allow binding to non localhost interface.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1054
>                 URL: https://issues.apache.org/jira/browse/DERBY-1054
>             Project: Derby
>          Issue 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
>         Assigned To: Bryan Pendleton
>             Fix For: 10.3.0.0
>
>         Attachments: cadminservlet98430.html, derby_1054_v1.diff, derby_1054_v2.diff, derby_docs_v1.diff
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.