db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1054) Starting Derby with the NetServlet inside of tomcat does not allow binding to non localhost interface.
Date Sat, 28 Apr 2007 15:44:15 GMT

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

Bryan Pendleton updated DERBY-1054:
-----------------------------------

    Attachment: cadminservlet98430.html
                derby_docs_v1.diff
                derby_1054_v2.diff

Attached is a revised version of the code patch proposal, and a docs patch proposal.

derby_1054_v2.diff includes additional information in the web.xml discussing the security
considerations of setting the host paramter in the web.xml file. It also corrects the description
of the tracingDirectory parameter, which had a copy-and-paste error.

derby_docs_v1.diff contains a modification to the servlet interface doc in the admin guide
to document the new host parameter, and to describe the security considerations of that parameter.

cadminservlet98430.html shows the new doc page formatted as HTML, for easy reviewing.

Please let me know your feedback.

> 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
>         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.


Mime
View raw message