On 4/6/2013 6:27 AM, Ralph Rauscher wrote:
RE: Empty tables returned in the second connection to the Derby
network server (Derby 10.9.1.0)
Got it :)
Problem was at some point after the creation of the Derby server and
creation of a connection to it in the server, this code was called
(also in the server program):
System.setProperty("derby.system.home", FullConfigPath);
System.setProperty("derby.drda.host", "0.0.0.0");
Looks like those settings screwed up any clients newly connecting from
the same host.
It could be that you are accidentally creating/accessing two databases
in different locations: first in the java start location because no
derby.system.home is set, and then another after setting
derby.system.home. Check your file system for multiple database
directories. If you start the server with -Dderby.infolog.append=true
then you might see the boot locations in the derby.log but if this is
the problem, there are probably two derby.log's as well.
Best
Kathey
