[
https://issues.apache.org/jira/browse/DERBY-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486680
]
Bryan Pendleton commented on DERBY-1054:
----------------------------------------
Correct. This parameter is only added to the web.xml, and thus requires
server-side access.
> 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: derby_1054_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.
