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

Keith Wall reopened QPID-5012:
------------------------------

      Assignee: Keith Wall  (was: Robbie Gemmell)

I can see that test BDBMessageStoreConfigurationTest is failing to close the 
BDB Environment.  This has the affect of leaving BDB's StatCleaner threads 
running. These get confused when their associated work directory is removed 
(they spin repeatedly logging an ISE). I also notice that yesterday's jenkins 
build 982 was *huge* as a result of this problem.

I'll commit a change to trunk to turn of the new stats collection feature (this 
is the default we'd want).

Separately, we need to fix BDBMessageStoreConfigurationTest so that the 
Environment is always closed, and a defect needs to be raised on the BDB JE 
forums.
                
> [Java Broker] update optional BDB store to use version 5.0.84 of BDB JE 
> ------------------------------------------------------------------------
>
>                 Key: QPID-5012
>                 URL: https://issues.apache.org/jira/browse/QPID-5012
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>            Assignee: Keith Wall
>             Fix For: 0.25
>
>
> A newer release of BDB JE is available, 5.0.84. We should update the 
> dependency for the optional BDB store to use this. The release contains a 
> number of defect fixes that appear to have the potential to impact users of 
> the Java Broker.  This is a drop in replacement and requires no code changes.
> http://download.oracle.com/otndocs/products/berkeleydb/html/je/je-5.0.84_changelog.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to