If I have a server with multiple IP addresses, and I only want Derby to answer on one of them, would I do something like this:
derby.drda.host=specificIP Or is there some other way? Daniel On 9/25/06, John Embretsen <[EMAIL PROTECTED]> wrote:
Xianghan Zheng wrote: > hi, > I get a strange exception: > > Failure making connection: org.apache.derby.client.am.DisconnectException: > java.security.PrivilegedActionException : Error opening socket to server > 192.168.0.105 on port 1527 with message : null [snipped stack trace] > The problem is that i can only access the derby server in localhost, not > the remote access. Does somebody know what is the problem. How to solve > it? The Derby Network Server listens to the localhost interface only by default. If you want the server to accept remote connections, you have to set the derby.drda.host property to 0.0.0.0 before/when starting the server, or by using the -h 0.0.0.0 option if you are using a script or NetworkServerControl from the command line. See http://db.apache.org/derby/docs/dev/adminguide/radmindrdahost.html Please note that you should use other means to secure Derby once you allow remote connections. You can read more about this in the Derby Server and Administration Guide, available from http://db.apache.org/derby/manuals/. -- John
