[DERBY-1054] Starting Derby with the NetServlet inside of tomcat does not allow binding to non localhost interface.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.3.1.4
• Component/s: Network Server
• Environment: Gentoo & RedHat Linux. ; JDK 1.5.0. ; Tomcat 5.0.28; Derby 10.1; derby.war
• Assignee: Bryan Pendleton
• Reporter: Shane Powell
• Created: 25/Feb/06 09:38
• Updated: 21/Jan/11 17:48
• Resolved: 07/May/07 15:48

Description

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.