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 KatheyMarsden
Date Tue, 11 Oct 2005 18:15:01 GMT
Dear Wiki user,

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

The following page has been changed by KatheyMarsden:
http://wiki.apache.org/db-derby/ProtocolDebuggingTips

------------------------------------------------------------------------------
  Execution failed because of a Distributed Protocol Error:  DRDA_Proto_SYNTAXRM;
  CODPNT arg  = 2114; Error Code Value = e
  
- This type of error is usually indicative of a bug in Derby.  All expected exceptions should
throw SQLExceptions and not protocol errors.
+ This type of error is usually indicative of a bug in Derby.  Expected exceptions, typically
are thrown as SQLExceptions and not protocol errors.
- 
  
  == Understanding DRDA ==
  
@@ -33, +32 @@

  There are three tracing options that can be set to assist with debugging protocol errors.
  
  === Client Tracing ===
- Use the [http://db.apache.org/derby/docs/10.1/adminguide/cadminappsclienttracing.html
+ Use the 
-  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.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.
  
  
  === 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.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.
  
  
  === Server SanityManager.DEBUG Output ===
- With a sane build, you can set the derby property, derby.drda.debug=true.  Thise will produce
debug output on the server console which can be helpful in debugging protocol issues.  This
property also launches a thread which will print periodic memory usage information for the
server jvm, so can be useful in debugging memory leaks as well.
+ With a sane build, you can set the derby property, derby.drda.debug=true.  This will produce
debug output on the server console which can be helpful in debugging protocol issues.  This
property also launches a thread which will print periodic memory usage information for the
server jvm, so can be useful in debugging memory leaks as well.
  
  
  == Useful Links ==
  
- Protocol Specifications - http://www.opengroup.org/dbiop/
+  * 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.1/adminguide/
  

Mime
View raw message