[DERBY-1011] Improve Network Server Exception Handling

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.2.1.6
• Component/s: Network Server
• Assignee: Unassigned
• Reporter: Katherine Marsden
• Created: 19/Feb/06 15:59
• Updated: 19/Feb/06 15:59

Description

I think that there needs to be a comprehensive look at the Network Server exception handling, which is an ongoing area of concern. I am not sure how much can be done from a DRDA perspective but it would definitely be worth a look.

• Exceptions are localized with a stored procedure call which is problematic when the procedure can't be called because of a serious error and traditionally has caused other issues as well. It seems like somehow we could negotiate the client locale up front and send back the localized message
• Multiple exceptions are flattenned into one and there is limitted space to send parameter info to the client. (70 characters according to DRDA).
• Many warnings do not get returned to the client.
• I think SQLExceptions thrown by the Network Server are not getting logged to derby.log

Sub-Tasks

• Network Server agentError calls log only to console and are hard to diagnose: Closed