[ http://issues.apache.org/jira/browse/DERBY-1456?page=all ]
Kathey Marsden resolved DERBY-1456.
-----------------------------------
Fix Version/s: 10.1.3.2
Resolution: Fixed
Checked into 10.1
Date: Thu Aug 10 14:20:52 2006
New Revision: 430534
URL: http://svn.apache.org/viewvc?rev=430534&view=rev
Log:
DERBY-1456 Network Server agentError calls log only to console and are hard to
diagnose
merge from trunk (svn 428012)
Contributed by Sunitha Kambhampati
I made an error on the bug number on checkin so the10.1 change does not show
up in subversion commits for this issue but rather with DERBY-353. I changed it
wtih svn propedit but that does not fix Jira apparently.
> 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
> Fix For: 10.1.3.2, 10.2.0.0
>
> 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
