db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-1456) Network Server agentError calls log only to console and are hard to diagnose
Date Wed, 02 Aug 2006 14:55:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1456?page=all ]

Bryan Pendleton resolved DERBY-1456.
------------------------------------

    Fix Version/s: 10.2.0.0
       Resolution: Fixed
       Derby Info:   (was: [Patch Available])

Using the technique suggested by Sunitha in the notes, which involves temporarily backing
out the fix to DERBY-1454 and then running the repro code from that bug, I was able to confirm
Sunitha's results and verify that the change works for me as well. The exception that is returned
to the user is vastly more useful, and proper exception information is logged to derby.log.

derbyall run was clean for me as well (modulo strange TransactionTable diff which others are
also seeing).

Committed the patch to subversion as revision 428012.

Thank you very much for fixing this problem, Sunitha. Can you please close the issue at your
convenience?


> 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.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

        

Mime
View raw message