Thanks for the replies guys. Unfortunately nothing seems to work for me. :-(
My DERBY_HOME is set to c:\temp\db-derby-10.4.1.3-bin\ I copied my derby.properties file in DERBY_HOME, DERBY_HOME\bin and DERBY_HOME\lib. Here is its contents: derby.infolog.append=true derby.language.logQueryPlan=true derby.language.logStatementText=true derby.drda.logConnections=true derby.stream.error.file=c:/myderby.log And I run the server with this command: \Java\jdk1.4.2_12\bin\java.exe -Dderby.language.logQueryPlan=true -jar derbyrun.jar server start The log file gets appended to, I can see the connection numbers in the server's console and in the log file and the logs are sent to my custom file but I can't for the love of god get any statements or plans logged. I can't believe I'm the only one with such a complete lack of logs. Must be something about my setup. Any other ideas? Thanks again Donald John H. Embretsen-3 wrote: > > adam jvok wrote: >> I have a similar problem. >> I'm using 10.4.1.3 on linux and, following John's advice, yes, I can >> get the query plan logged if I use the embedded driver. But I don't >> want to use the embedded driver. >> So far I have failed to make this work with the network server. >> My derby.log remains empty running the same query with the network >> server, even with derby.properties containing: >> derby.language.logQueryPlan=true >> and DERBY_OPTS=-Dderby.language.logQueryPlan=true >> Any ideas how to get this to work with the network server? > > I just tried with the bin\startNetworkServer.bat script as well, having > derby.language.logQueryPlan=true in derby.properties, and the query plan > ended > up in derby.log. > > In this experiment, I put derby.properties in > C:\tmp\john\db-derby-10.4.1.3-bin > and ran the commands > > "set DERBY_HOME=c:\tmp\john\db-derby-10.4.1.3-bin" > > and > > "bin\startNetworkServer.bat" > > from that directory. > Then I connected to the server via IJ using the client driver: > > "java -jar lib\derbyrun.jar ij" > > > Some questions that may help folks along: > > How exactly are you starting the server, and from which directory? > > Are you sure that derby.properties is in the server's "system home"? > This is either the network server's working directory, or the directory > pointed > to by the system property derby.system.home if set. > > If you add the property > derby.drda.logConnections=true > to derby.properties, do you see connection logging in the server console > after > you restart the server and connect to it via JDBC (e.g. IJ)? > If you do, the problem is property-specific. If you don't, the server does > not > seem see your derby.properties file at all. > > Did you try the "java <properties> -jar derbyrun.jar server start" > approach? > This makes it more likely that the server sees you settings, in case there > are > "system home" issues. > > > -- > John > > > > > > -- View this message in context: http://www.nabble.com/Cannot-get-derby.language.logQueryPlan-to-work-tp17135317p17146825.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
