Noel J. Bergman wrote:
jta wrote:
...
2) Which jdbc driver is being used?
See our config file. The only entry is:
org.apache.derby.jdbc.EmbeddedDriver
I assume that answers the question, and that we are using the embedded
driver version of Derby. Should we be doing things differently?
Bernd Fondermann wrote:
...
-D properties are indeed recognized at least for opening a socket for
derby:
Added -Dderby.drda.startNetworkServer=true to the phoenix.sh command
line plus put derby[net|tools|client].jar into the lib directory
containing derby.jar.
now the embedded db could be
Noel J. Bergman wrote:
Serge,
Noel J. Bergman wrote
I am still concerned about the Derby related crash that I saw earlier.
Anyone have a clue? And is there anything that we need to do to cleanly
shut Derby down?
I'm at -0 over using Derby at this point.
Well, we aren't talking about
