)]}'
{"glance/db/sqlalchemy/api.py":[{"author":{"_account_id":1872,"name":"therese-mchale","email":"therese.mchale@hp.com","username":"therese-mchale"},"change_message_id":"08a91bde3a18652f9564bf479db85dc00b0f4954","unresolved":false,"context_lines":[{"line_number":93,"context_line":"    _MAX_RETRIES \u003d CONF.sql_max_retries"},{"line_number":94,"context_line":"    _RETRY_INTERVAL \u003d CONF.sql_retry_interval"},{"line_number":95,"context_line":"    _CONNECTION \u003d CONF.sql_connection"},{"line_number":96,"context_line":"    _ENGINE \u003d get_engine()"},{"line_number":97,"context_line":"    sa_logger \u003d logging.getLogger(\u0027sqlalchemy.engine\u0027)"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"AAAAM3%2F%2ByJM%3D","line":96,"updated":"2013-02-19 11:12:52.000000000","message":"no this will break stuff. i.e. all worker threads will now inherit this engine and therefore we will be back to the same bug we originally had with db sessions becoming garbled.   (by the way configure_db is still there...it calls set_db_env and gets the engine..so if you wanted to do that you would use that...)  either a) use configure db but make sure the engine you use is blown away afterwards or is at least not inherited by worker processses or b) do it within one of the worker threads but make sure somehow only one worker does it.","commit_id":"66c8e42a7fd6f5cf59030b4f388850964764c28d"}]}