Raymond Kroeker wrote:
Hi Dan,
It looks like the url you're using from the client isn't quite
right. For a client/server url you want the logical database name in
the url after the port and not the path to the database.
So a single server can support multilple databases. What you'll
Hi Dan,
It looks like the url you're using from the client isn't quite right.
For a client/server url you want the logical database name in the url after
the port and not the path to the database.
So a single server can support multilple databases. What you'll want to
try is something like
host and the port. I could successfully ping the Apache Webserver
getting port 80, but not the Derby server.
You don't mention a lot about how you started the network server,
but are you using the "-h" parameter? Note that, as it says on:
http://db.apache.org/derby/docs/10.2/adminguide/tadmincb
I have a linux server running Redhat ES4 and have Derby 10.2.2.0
installed. I can access the database at the server using the ij tool.
The server is on a lan with an ip address of 192.168.1.99. I can start
the Derby server using either the ip address and port 1527 or using
0.0.0.0 and port 1527 and
