qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-2950) DerbyMessageStore incorrectly logs an error for an expected exception indicating successfull database shutdown
Date Sat, 03 Mar 2012 14:47:58 GMT

     [ https://issues.apache.org/jira/browse/QPID-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robbie Gemmell updated QPID-2950:
---------------------------------

    Labels: derbystore  (was: )
    
> DerbyMessageStore incorrectly logs an error for an expected exception indicating successfull
database shutdown
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-2950
>                 URL: https://issues.apache.org/jira/browse/QPID-2950
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker Derby Store
>    Affects Versions: 0.7
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>              Labels: derbystore
>             Fix For: 0.8
>
>
> The DerbyMessageStore incorrectly logs an error for an expected exception indicating
successfull database shutdown, because it is actuall checking for the wrong SQLcode for the
expected exception. The value being checked currently is that to indicate complete shutdown
of the Derby engine, and not simply the database being closed. 
> Updating SLF4J library (QPID-2947) causes this defect to make the AlertingTest fail under
the 'java' test profile, because the error message is then found in the startup logs of the
external broker (due to use of an InVM broker to load some configuration during setup before
starting the external broker) and this is then assumed to indicate the external broker failed
to start. it is not clear why upgrading SLF4J causes this change in behaviour though as it
would seem it shouldnt really impact the affected codepath; it doesnt use SLF4J and should
already be logging the same error in the same place and so fail in the same way, but doesnt
seem to do so.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message