db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "ProtocolDebuggingTips" by KristianWaagan
Date Tue, 16 Nov 2010 15:08:09 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The "ProtocolDebuggingTips" page has been changed by KristianWaagan.
The comment on this change is: Updated links to the manual (10.1 -> 10.6)..
http://wiki.apache.org/db-derby/ProtocolDebuggingTips?action=diff&rev1=4&rev2=5

--------------------------------------------------

  
  === Client Tracing ===
  Use the 
- [[http://db.apache.org/derby/docs/10.1/adminguide/cadminappsclienttracing.html|traceFile]]
or traceDirectory connection attributes to specify trace output files.  If you are debugging
protocol with multiple connections use traceDirectory instead of traceFile.   The client side
tracing shows  the protocol flow in the context of the jdbc calls so is probably the best
choice for tracing.
+ [[http://db.apache.org/derby/docs/10.6/adminguide/cadminappsclienttracing.html|traceFile]]
or traceDirectory connection attributes to specify trace output files.  If you are debugging
protocol with multiple connections use traceDirectory instead of traceFile.   The client side
tracing shows  the protocol flow in the context of the jdbc calls so is probably the best
choice for tracing.
  
  
  === Server Tracing ===
- There is also server side tracing available by setting the [[http://db.apache.org/derby/docs/10.1/adminguide/radminconfig.html|derby.drda.traceAll]]
and [[http://db.apache.org/derby/docs/10.1/adminguide/radminconfigdb2jdrdatracedirectory.html|derby.drda.traceDirectory]]
properties.  The server side tracing shows just the protocol and is usually only useful if
a message for some reason is getting lost between the server and client.
+ There is also server side tracing available by setting the [[http://db.apache.org/derby/docs/10.6/adminguide/radminconfig.html|derby.drda.traceAll]]
and [[http://db.apache.org/derby/docs/10.6/adminguide/radminconfigdb2jdrdatracedirectory.html|derby.drda.traceDirectory]]
properties.  The server side tracing shows just the protocol and is usually only useful if
a message for some reason is getting lost between the server and client.
  
  
  === Server SanityManager.DEBUG Output ===
@@ -52, +52 @@

  == Useful Links ==
  
   * Protocol Specifications - http://www.opengroup.org/dbiop/
-  * Server admin guide - http://db.apache.org/derby/docs/10.1/adminguide/
+  * Server admin guide - http://db.apache.org/derby/docs/10.6/adminguide/
  

Mime
View raw message