Improve DDMWriter and DDMReader traces
--------------------------------------
Key: DERBY-863
URL: http://issues.apache.org/jira/browse/DERBY-863
Project: Derby
Type: Improvement
Components: Network Server
Versions: 10.1.1.0, 10.2.0.0
Reporter: Bryan Pendleton
Priority: Minor
Improve the DDMWriter and DDMReader traces to better support DRDA protocol bug
analysis.
Among the ways that these traces could be improved:
- Show the related JDBC api calls for improved context, as is done by the
client-side tracing
- Recognize and display in a human-readable format the DSS protocol envelope,
such as the
block headers, the protocol flags, the chaining fields, the code point, etc.
This is partly done,
but the current implementation tends to emit this information only for the
first message in a
multi-message block
- Improve legibility for extremely long messages. In particular, when buffers
become very large
due to continuations and/or chaining, the buffer can exceed 64K and then the
hex offsets in
the traces wrap around, which can be quite confusing.
A close read of http://wiki.apache.org/db-derby/DssProtocolErrors will provide
lots of ideas
for ways to improve the traces. Basically, the type of analysis done in this
Wiki page should
pretty much "jump off the screen" when reading the traces.
This issue arose out of my work on DERBY-125, DERBY-170, DERBY-491 and
DERBY-492; you may want to consult those issues for additional background
information.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
