You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2007/04/04 05:04:34 UTC
[jira] Updated: (DERBY-1054) Starting Derby with the NetServlet
inside of tomcat does not allow binding to non localhost interface.
[ https://issues.apache.org/jira/browse/DERBY-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Pendleton updated DERBY-1054:
-----------------------------------
Attachment: derby_1054_v1.diff
This seems like a useful idea. One straightforward way to accomplish
this would be by adding another web.xml "init-param" parameter, similar
to the already existing parameter that allows controlling the port number.
Attached is 'derby_1054_v1.diff', a patch proposal which adds a 'host'
parameter to the web.xml file and enhances NetServlet to use that
parameter, if present, to set the NetworkServer host name parameter.
> 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.