[DERBY-1456] Network Server agentError calls log only to console and are hard to diagnose

• Type: Sub-task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.1.3.2, 10.2.1.6
• Component/s: Network Server
• Assignee: Sunitha Kambhampati
• Reporter: Bryan Pendleton
• Created: 25/Jun/06 07:10
• Updated: 13/Dec/07 09:05
• Resolved: 10/Aug/06 22:48

Description

The Network Server code uses an assertion-check utility routine called agentError()
under certain circumstances. When these agentError() calls arise, for example as
in DERBY-1454, there is no server side logging of the error except to the console.

The user application that hit DERBY-1454 had not been capturing console output and there
was no clue in the derby.log, this made the problem hard to track down when they
suddenly hit this boundary deep within their stress tests.

See also DERBY-743 for another issue with Network Server's agentError routine.