[DERBY-293] Correlate client connection with embedded connection

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.1.1.0
• Component/s: Network Server
• Environment: N/A
• Urgency: Low
• Assignee: Unassigned
• Reporter: David Van Couvering
• Created: 17/May/05 05:47
• Updated: 28/Jul/06 23:52

Description

There should be a way for someone to correlate a given embedded connection with its matching network client connection, if such a client connection exists.

See

http://article.gmane.org/gmane.comp.apache.db.derby.devel/3748

and

http://article.gmane.org/gmane.comp.apache.db.derby.devel/3942

for some background info on how to get useful information out of the DRDA protocol
stream to accomplish this.

This could be done either by modifying the toString() method of an embedded
connection to show its associated network client connection information or (my
preference) include this information in the proposed Connection VTI (see DERBY-292). I am worried that if we use toString() for this, the output will be overly long and complicated; also, over a period of time the same embedded connection may be associated with multiple client connections, resulting in a changing toString() value for the embedded connection. This seems problematic if we are intending toString() to uniquely identify a connection for the lifetime of the connection – this would be a good goal to have as it would enable us to do some useful debugging using the VTIs.

Issue Links

• is related to: DERBY-17 Network Server Needs to generate CRRTKN on ACCRDB if client does not send it
• is related to: DERBY-291 Debug VTIs should refer to connection string
• is related to: DERBY-292 Add a Connection VTI