[ http://issues.apache.org/jira/browse/DERBY-1456?page=all ]
Sunitha Kambhampati updated DERBY-1456:
---------------------------------------
Assignee: Sunitha Kambhampati
Derby Info: [Patch Available]
> Network Server agentError calls log only to console and are hard to diagnose
> ----------------------------------------------------------------------------
>
> Key: DERBY-1456
> URL: http://issues.apache.org/jira/browse/DERBY-1456
> Project: Derby
> Issue Type: Sub-task
> Components: Network Server
> Affects Versions: 10.2.0.0
> Reporter: Bryan Pendleton
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: 1456_notes.txt, derby1456.diff.txt, derby1456.stat.txt
>
>
> 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.
--
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
